This is some text inside of a div block.
< back to blog

Runtime security for Amazon EKS Auto Mode with Sysdig

Eric Carter
Runtime security for Amazon EKS Auto Mode with Sysdig
Published by:
Eric Carter
Product Marketing Director
Runtime security for Amazon EKS Auto Mode with Sysdig
Product Marketing Director
@
Subscribe to Threat Research
Runtime security for Amazon EKS Auto Mode with Sysdig
Published:
November 19, 2026
Table of contents
TRT in your inbox

Get security briefings from the Threat Research Team

New campaigns, attacker techniques, and detection guidance — straight to your inbox.

Subscribe
falco feeds by sysdig

Falco Feeds extends the power of Falco by giving open source-focused companies access to expert-written rules that are continuously updated as new threats are discovered.

learn more
Green background with a circular icon on the left and three bullet points listing: Automatically detect threats, Eliminate rule maintenance, Stay compliant, with three black and white cursor arrows pointing at the text.

If you use Amazon Elastic Kubernetes Service (Amazon EKS) Auto Mode, you benefit from AWS-managed infrastructure, but you still need runtime security for your workloads. Amazon EKS Auto Mode lets AWS run your Kubernetes cluster infrastructure: compute, networking, storage, load balancing, and node patching. That removes a lot of toil. Because AWS operates the nodes for you in a managed model, nodes are identical, predictable, and immutable, with read-only root filesystems and strict security controls. This post covers what that means for runtime security, and how to deploy and use Sysdig Secure with EKS Auto Mode using Universal eBPF.

What changes with Amazon EKS Auto Mode

With standard EKS, AWS manages the control plane, and you manage the worker nodes. Auto Mode extends AWS's responsibility to the nodes and the core cluster capabilities:

Nodes are AWS-managed appliances: a locked-down, container-focused OS (Bottlerocket-based) with a read-only root filesystem and SELinux enforcement. Nodes are replaced regularly, so they never drift. See the Auto Mode documentation for the full list of managed components.

Shared responsibility still applies

AWS managesYou manage

AWS's security guidance for Auto Mode and best practices cover the AWS side. This post covers the last row: what happens inside your workloads at runtime.

Why Auto Mode needs a different agent approach

Auto Mode nodes don't allow kernel module loading for security reasons. Because Bottlerocket fully supports eBPF (Extended Berkeley Packet Filter), Sysdig uses eBPF as the primary mechanism for runtime security. A Universal eBPF driver embedded in the Sysdig Host Shield (agent) enables a real-time approach to monitoring system activity safely within the kernel using system calls as a source of truth.

Learn more about kernel-level security monitoring.

How to get started

Sysdig deploys as a Kubernetes workload, so it follows Auto Mode nodes as AWS adds and replaces them. Nothing runs on the host outside Kubernetes.

How it works

Where Sysdig complements AWS-native controls

Amazon GuardDuty, AWS Security Hub, EKS control-plane logging, network policies, and Pod Security Standards are recommended in an Auto Mode design. They cover the AWS and control-plane layers. Sysdig complements these controls with in-depth cloud workload protection. With Sysdig, security teams can apply runtime policies, investigate process activity, monitor file and workload behavior, and correlate events with Kubernetes context. 

Customizable detection rules are built on the industry-leading Falco engine. It allows you to monitor system calls to identify errant or suspicious events at the Linux kernel level. You can use the default threat detection rules in Sysdig Secure or easily customize rules to work with your unique threat model.

The dynamic, short-lived nature of container workloads in a Kubernetes environment means static scanning and other traditional security measures may not detect threats that emerge at runtime. You need runtime security-the ability to monitor behavior in real time to quickly identify and address security issues for workloads running on Amazon EKS Auto Mode. For example, a compromised container might spawn an unexpected process or open a network connection that no vulnerability scanner would flag in advance. Runtime monitoring catches that behavior as it happens, with full Kubernetes context such as cluster, namespace, and workload identity.

We recommend proper posture management, including thorough container vulnerability scanning. Runtime security adds an extra layer of defense against exploits that static analysis or vulnerability scanners may miss, such as zero-days. Runtime security matters for modern organizations because it helps protect workloads and data from unauthorized access, malicious or unintentional changes, and suspicious behavior that could indicate an attack.

Try Amazon EKS Auto Mode with Sysdig

The fastest proof of value is a small EKS Auto Mode cluster with Sysdig on Universal eBPF. Check that core detections and Kubernetes context work, then test the response and investigation workflows that matter to your team. Ready to get started? You can request a demo, check out  the installation docs, or read more about Sysdig for Kubernetes here: Runtime-Driven Security for Containers & Kubernetes — A Practitioner’s Toolkit.

‍

Co-written with Merin Eralil, ISV Security Partner Solutions Architect – AWS.

About the author

featured resources

Test drive the right way to defend the cloud
with a security expert