AWS AmazonECS documentation change
Summary
Updated reference from 'Elastic Load Balancing' to 'ELB' in CodeDeploy permissions description.
Security assessment
Change only updates abbreviation usage without altering security context. Permission requirements for load balancer modifications remain unchanged and are part of standard deployment procedures, not a security fix or vulnerability disclosure.
Diff
diff --git a/AmazonECS/latest/developerguide/deployment-type-bluegreen.md b/AmazonECS/latest/developerguide/deployment-type-bluegreen.md index c0ae13fb9..9501f5170 100644 --- a//AmazonECS/latest/developerguide/deployment-type-bluegreen.md +++ b//AmazonECS/latest/developerguide/deployment-type-bluegreen.md @@ -178 +178 @@ In addition to the standard Amazon ECS permissions required to run tasks and ser -CodeDeploy needs permissions to call Amazon ECS APIs, modify your Elastic Load Balancing, invoke Lambda functions, and describe CloudWatch alarms, as well as permissions to modify your service's desired count on your behalf. Before creating an Amazon ECS service that uses the blue/green deployment type, you must create an IAM role (`ecsCodeDeployRole`). For more information, see [Amazon ECS CodeDeploy IAM Role](./codedeploy_IAM_role.html). +CodeDeploy needs permissions to call Amazon ECS APIs, modify your ELB, invoke Lambda functions, and describe CloudWatch alarms, as well as permissions to modify your service's desired count on your behalf. Before creating an Amazon ECS service that uses the blue/green deployment type, you must create an IAM role (`ecsCodeDeployRole`). For more information, see [Amazon ECS CodeDeploy IAM Role](./codedeploy_IAM_role.html).