AWS AmazonECS documentation change
Summary
Updated terminology from 'Elastic Load Balancing' to 'ELB' in three instances for consistency and brevity.
Security assessment
Changes are purely terminological (replacing 'Elastic Load Balancing' with 'ELB') without altering security configurations, permissions, or best practices. No evidence of security vulnerability remediation.
Diff
diff --git a/AmazonECS/latest/developerguide/update-rolling-to-bluegreen.md b/AmazonECS/latest/developerguide/update-rolling-to-bluegreen.md index 93727a839..01870fb9e 100644 --- a//AmazonECS/latest/developerguide/update-rolling-to-bluegreen.md +++ b//AmazonECS/latest/developerguide/update-rolling-to-bluegreen.md @@ -23 +23 @@ Before migrating your service from rolling to blue/green deployments, ensure you - * For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). + * For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). @@ -29 +29 @@ Before migrating your service from rolling to blue/green deployments, ensure you - * If your service uses Elastic Load Balancing, update your service with the new `advancedConfiguration` and start a rolling deployment. + * If your service uses ELB, update your service with the new `advancedConfiguration` and start a rolling deployment. @@ -33 +33 @@ Before migrating your service from rolling to blue/green deployments, ensure you - * If your service uses both Elastic Load Balancing and Service Connect, perform both steps above (you can use a single UpdateService request). + * If your service uses both ELB and Service Connect, perform both steps above (you can use a single UpdateService request).