GuardDuty security agent release versions
GuardDuty releases an updated agent version from time to time. When GuardDuty manages the agent automatically, GuardDuty is designed to update the agent on your behalf. When you manage the agent manually, you are responsible to update the agent version for your resource types – Amazon EC2 instances, Amazon ECS clusters, and Amazon EKS clusters.
The following sections provide GuardDuty security agent release versions and associated release notes for all the supported resource types.
Topics
The following table shows the release version history for the GuardDuty security agent for Amazon EC2.
The following table shows the release version history for the GuardDuty security agent for Fargate (Amazon ECS only).
GuardDuty releases an updated agent version from time to time. When GuardDuty manages the agent automatically, it is designed to manage the agent updates on your behalf. When you manage the agent manually, you are responsible to update the agent version for your Amazon EKS clusters.
Before updating the agent to a specific version, add the image registry for GuardDuty
to the allowed-container-registries in your admission controller. For more information,
see Amazon ECR repository hosting GuardDuty
agent.
The following table shows the release version history of Amazon EKS add-on GuardDuty agent.
Additional resources - next steps
For more information on the next steps, see the following topics:
-
Prerequisites to enabling Runtime Monitoring - With new agent versions, there might be an update to the prerequisites section. Verify and validate that your resources meet the latest prerequisites.
-
Managing GuardDuty security agents - When you manage the agent manually, then you're responsible for managing the updates to the agent version running on your resources. Based on your resource type (Amazon EKS or Amazon EC2-Amazon ECS), perform the steps to update the security agent. Also make sure to validate your VPC endpoint configuration.
-
Reviewing runtime coverage statistics and troubleshooting issues - After you have updated the security agent, you can assess the runtime coverage your resource. If there is any coverage issue, then use the associated troubleshooting steps.