Prerequisites for Amazon EKS cluster support
This section includes the prerequisites for monitoring runtime behavior of your Amazon EKS resources. After these prerequisites are met, see Enabling GuardDuty Runtime Monitoring.
Validating architectural requirements
The platform that you use may impact how GuardDuty security agent supports GuardDuty in receiving the runtime events from your EKS clusters. You must validate that you're using one of the verified platforms. If you're managing the GuardDuty agent manually, ensure that the Kubernetes version supports the GuardDuty agent version that is currently in use.
Verified platforms
The OS distribution, kernel version, and CPU architecture affect the support provided by the GuardDuty security agent. The following table shows the verified configuration for deploying the GuardDuty security agent and configuring EKS Runtime Monitoring.
-
Support for various operating systems - GuardDuty has verified the support for using Runtime Monitoring on the operating systems that are listed in the preceding table. If you use a different operating system and are able to install the security agent successfully, you might get all the expected security value that GuardDuty has been verified to provide with the listed OS distribution.
-
Runtime Monitoring for Amazon EKS clusters doesn't support the first generation Graviton instance such as A1 instance types.
-
Presently, with Kernel version
6.1
, GuardDuty can't generate GuardDuty Runtime Monitoring finding types that are related to Domain Name System (DNS) events. -
Runtime Monitoring supports AL2023 with the release of the GuardDuty security agent v1.6.0 and above. For more information, see GuardDuty security agent for Amazon EKS clusters.
Kubernetes versions supported by GuardDuty security agent
The following table shows the Kubernetes versions for your EKS clusters that are supported by GuardDuty security agent.
Kubernetes version |
Amazon EKS add-on GuardDuty security agent version |
---|---|
1.28 - 1.30 |
v1.4.1 and newer |
1.27 |
v1.3.0 and newer |
1.26 |
v1.2.0 and newer |
1.21 - 1.25 |
All versions |
Some of the GuardDuty security agent versions will reach end of standard support. For information about the agent release versions, see GuardDuty security agent for Amazon EKS clusters.
CPU and memory limits
The following table shows the CPU and memory limits for the Amazon EKS add-on for GuardDuty
(aws-guardduty-agent
).
Parameter | Minimum limit | Maximum limit |
---|---|---|
CPU |
200m |
1000m |
Memory |
256 Mi |
1024 Mi |
When you use Amazon EKS add-on version 1.5.0 or above, GuardDuty provides the capability to configure the add-on schema for your CPU and memory values. For information about the configurable range, see Configurable parameters and values.
After you enable EKS Runtime Monitoring and assess the coverage status of your EKS clusters, you can set up and view the container insight metrics. For more information, see Setting up CPU and memory monitoring.