AWS guardduty documentation change
Summary
Updated EKS add-on version from v1.9.0 to v1.10.0, restructured VPC endpoint documentation, and changed section title
Security assessment
Version update and documentation restructuring do not explicitly address security vulnerabilities. No mention of security fixes in changelog.
Diff
diff --git a/guardduty/latest/ug/eksrunmon-deploy-security-agent.md b/guardduty/latest/ug/eksrunmon-deploy-security-agent.md index 393524ab6..eb1ea3ba9 100644 --- a//guardduty/latest/ug/eksrunmon-deploy-security-agent.md +++ b//guardduty/latest/ug/eksrunmon-deploy-security-agent.md @@ -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.9.0-eksbuild.2 --configuration-values 'file://example.json' + aws eks create-addon --region us-east-1 --cluster-name myClusterName --addon-name aws-guardduty-agent --addon-version v1.10.0-eksbuild.2 --configuration-values 'file://example.json' @@ -99,7 +99 @@ You can use the following AWS CLI example when using configurable values support -By default, the security agent resolves and connects to the private DNS name of the VPC endpoint. The following list provides the private DNS names for your endpoints: - - * Non-FIPS endpoint – `guardduty-data.`us-east-1`.amazonaws.com` - - * FIPS endpoint – `guardduty-data-fips.`us-east-1`.amazonaws.com` - - +By default, the security agent resolves and connects to the private DNS name of the VPC endpoint. For a non-FIPS endpoint, your private DNS will appear in the following format: @@ -106,0 +101 @@ By default, the security agent resolves and connects to the private DNS name of +Non-FIPS endpoint – `guardduty-data.`us-east-1`.amazonaws.com` @@ -116 +111 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Configure EKS add-on parameters +Prerequisite – Creating an Amazon VPC endpoint