AWS guardduty documentation change
Summary
Updated add-on name references to 'GuardDuty EKS Runtime Monitoring', recommended latest agent version (v1.9.0), and CLI example version update
Security assessment
Updates deployment instructions for security agent but no mention of patching vulnerabilities or security incidents.
Diff
diff --git a/guardduty/latest/ug/eksrunmon-deploy-security-agent.md index 6c8ac49af..393524ab6 100644 --- a/guardduty/latest/ug/eksrunmon-deploy-security-agent.md +++ b/guardduty/latest/ug/eksrunmon-deploy-security-agent.md @@ -22 +22 @@ Console - 5. On the **Select add-ons** page, choose **Amazon GuardDuty Runtime Monitoring**. + 5. On the **Select add-ons** page, choose **Amazon GuardDuty EKS Runtime Monitoring**. @@ -24 +24 @@ Console - 6. Choose the agent that shows up as the latest and default version. + 6. GuardDuty recommends choosing the latest and default agent **Version**. @@ -68 +68 @@ Use the following values for the request parameters: -You can use the following AWS CLI example when using configurable values supported for addon versions v1.5.0 or above. Make sure to replace the placeholder values highlighted in red and the associated `Example.json` with the configured values. +You can use the following AWS CLI example when using configurable values supported for add-on versions `v1.5.0` or above. Make sure to replace the placeholder values highlighted in red and the associated `Example.json` with the configured values. @@ -70 +70 @@ You can use the following AWS CLI example when using configurable values support - aws eks create-addon --region us-east-1 --cluster-name myClusterName --addon-name aws-guardduty-agent --addon-version v1.5.0-eksbuild.1 --configuration-values 'file://example.json' + aws eks create-addon --region us-east-1 --cluster-name myClusterName --addon-name aws-guardduty-agent --addon-version v1.9.0-eksbuild.2 --configuration-values 'file://example.json'