AWS AmazonECS documentation change
Summary
Updated wording from 'below' to 'in the following sections' for better clarity and navigation in the documentation.
Security assessment
The change improves document structure but doesn't address security vulnerabilities, weaknesses, or add security features. It maintains the same internet routing options (NAT gateway or public IP) without security modifications.
Diff
diff --git a/AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate.md b/AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate.md index dbdef2123..ff5ca7737 100644 --- a//AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate.md +++ b//AmazonECS/latest/developerguide/ECS_AWSCLI_Fargate.md @@ -169 +169 @@ Output: -After you have registered a task for your account, you can create a service for the registered task in your cluster. For this example, you create a service with one instance of the `sample-fargate:1` task definition running in your cluster. The task requires a route to the internet, so there are two ways you can achieve this. One way is to use a private subnet configured with a NAT gateway with an elastic IP address in a public subnet. Another way is to use a public subnet and assign a public IP address to your task. We provide both examples below. +After you have registered a task for your account, you can create a service for the registered task in your cluster. For this example, you create a service with one instance of the `sample-fargate:1` task definition running in your cluster. The task requires a route to the internet, so there are two ways you can achieve this. One way is to use a private subnet configured with a NAT gateway with an elastic IP address in a public subnet. Another way is to use a public subnet and assign a public IP address to your task. We provide both examples in the following sections.