AWS govcloud-us documentation change
Summary
Corrected service name syntax for VPC endpoints, fixed region placeholder formatting, renumbered list items, and updated apostrophe usage
Security assessment
Changes improve documentation clarity for GuardDuty configuration but do not address specific vulnerabilities or add new security features. The service name syntax correction helps prevent misconfiguration but isn't tied to a disclosed security issue.
Diff
diff --git a/govcloud-us/latest/UserGuide/govcloud-guardduty.md b/govcloud-us/latest/UserGuide/govcloud-guardduty.md index c870ad430..87dae08d7 100644 --- a//govcloud-us/latest/UserGuide/govcloud-guardduty.md +++ b//govcloud-us/latest/UserGuide/govcloud-guardduty.md @@ -17 +17 @@ The following list indicates the differences in the feature availability in AWS - 1. **For both Amazon EC2 and Amazon EKS** – In the prerequisite step for creating an Amazon VPC endpoint manually, the **Service name** in the AWS GovCloud (US) Region should be `com.amazonaws.`us-gov-east-1`.guardduty-data-fips`. + 1. **For both Amazon EC2 and Amazon EKS** – In the prerequisite step for creating an Amazon VPC endpoint manually, the **Service name** in the AWS GovCloud (US) Region should be `com.amazonaws.<us-gov-east-1>.guardduty-data-fips`. @@ -19 +19 @@ The following list indicates the differences in the feature availability in AWS -Replace `us-gov-east-1` with your Region. This must be the same Region as your Amazon EC2 instance (or Amazon EKS cluster) that belongs to your AWS account ID. +Replace <us-gov-east-1> with your Region. This must be the same Region as your Amazon EC2 instance (or Amazon EKS cluster) that belongs to your AWS account ID. @@ -31 +31 @@ For more information, see [GuardDuty security agent release versions](https://do - 3. **For Amazon EC2** – When managing the security agent manually using [Method 2 - Using Linux Package Managers](https://docs.aws.amazon.com/guardduty/latest/ug/installing-gdu-security-agent-ec2-manually.html), use the following AWS account IDs and Regions for both RPM installation and Debian installation: + 1. **For Amazon EC2** – When managing the security agent manually using [Method 2 - Using Linux Package Managers](https://docs.aws.amazon.com/guardduty/latest/ug/installing-gdu-security-agent-ec2-manually.html), use the following AWS account IDs and Regions for both RPM installation and Debian installation: @@ -37 +37 @@ For more information, see [GuardDuty security agent release versions](https://do - 4. **For Amazon EKS and Fargate-Amazon ECS resources** – For [Amazon ECR repository hosting GuardDuty agent](https://docs.aws.amazon.com/guardduty/latest/ug/runtime-monitoring-ecr-repository-gdu-agent.html), use the following ECR repository for your Amazon EKS and Fargate-Amazon ECS resources: + 2. **For Amazon EKS and Fargate-Amazon ECS resources** – For [Amazon ECR repository hosting GuardDuty agent](https://docs.aws.amazon.com/guardduty/latest/ug/runtime-monitoring-ecr-repository-gdu-agent.html), use the following ECR repository for your Amazon EKS and Fargate-Amazon ECS resources: @@ -81 +81 @@ AWS GovCloud (US-West) - `383110348953.dkr.ecr.us-gov-west-1.amazonaws.com/aws-g - * In AWS GovCloud (US) Regions, AWS doesn't use or store Customer Content processed by Amazon GuardDuty to develop and improve the service or technologies of AWS or its affiliates. Opt-out policies are currently not applicable to these Regions. + * In AWS GovCloud (US) Regions, AWS doesn’t use or store Customer Content processed by Amazon GuardDuty to develop and improve the service or technologies of AWS or its affiliates. Opt-out policies are currently not applicable to these Regions.