AWS AmazonECS documentation change
Summary
Clarified role selection wording and removed redundant 'here' in VPC description
Security assessment
Minor editorial changes to improve clarity without introducing or modifying security-related content. Infrastructure role references maintain existing security practices.
Diff
diff --git a/AmazonECS/latest/developerguide/ecs-vpc-lattice-create-service.md b/AmazonECS/latest/developerguide/ecs-vpc-lattice-create-service.md index 02de65ec9..30bbd0159 100644 --- a/AmazonECS/latest/developerguide/ecs-vpc-lattice-create-service.md +++ b/AmazonECS/latest/developerguide/ecs-vpc-lattice-create-service.md @@ -40 +40 @@ If you've never created a service before, follow the steps found in [Creating an - 6. Choose an **ECS infrastructure role for Amazon ECS** that you've already created to use when creating the VPC Lattice target group or choose to **Create ECS infrastructure role**. + 6. To use an existing role, for **ECS infrastructure role for Amazon ECS** , choose one that you've already created to use when creating the VPC Lattice target group. To create a new role, **Create ECS infrastructure role**. @@ -44 +44 @@ If you've never created a service before, follow the steps found in [Creating an -The **VPC** depends on the networking mode you selected when you registered your task definition. If you use the `host` or `network` mode with the EC2 launch type, choose your VPC here. +The **VPC** depends on the networking mode you selected when you registered your task definition. If you use the `host` or `network` mode with the EC2 launch type, choose your VPC.