AWS AmazonECS documentation change
Summary
Replaced 'Elastic Load Balancing' with 'ELB' acronym throughout document
Security assessment
Consistent use of acronyms for ELB without modifying security-related content. References to IAM roles and permissions remain functionally equivalent.
Diff
diff --git a/AmazonECS/latest/developerguide/migrate-codedeploy-to-ecs-bluegreen.md b/AmazonECS/latest/developerguide/migrate-codedeploy-to-ecs-bluegreen.md index e42b59c45..95647d616 100644 --- a//AmazonECS/latest/developerguide/migrate-codedeploy-to-ecs-bluegreen.md +++ b//AmazonECS/latest/developerguide/migrate-codedeploy-to-ecs-bluegreen.md @@ -19 +19 @@ When creating an Amazon ECS service using CodeDeploy, you: - 3. Create a CodeDeploy deployment group (as part of a CodeDeploy application), and configure it with details of the Amazon ECS cluster, service name, load balancer listeners, two target groups (the primary target group used in the production listener rule, and a secondary target group to be used for replacement tasks), a service role (to grant CodeDeploy permissions to manipulate Amazon ECS and Elastic Load Balancing resources) and various parameters that control the deployment behavior. + 3. Create a CodeDeploy deployment group (as part of a CodeDeploy application), and configure it with details of the Amazon ECS cluster, service name, load balancer listeners, two target groups (the primary target group used in the production listener rule, and a secondary target group to be used for replacement tasks), a service role (to grant CodeDeploy permissions to manipulate Amazon ECS and ELB resources) and various parameters that control the deployment behavior. @@ -38 +38 @@ With Amazon ECS blue/green deployments, The deployment configuration is part of - * An IAM role to grant Amazon ECS permission to call the Elastic Load Balancing APIs + * An IAM role to grant Amazon ECS permission to call the ELB APIs @@ -70 +70 @@ There are three main approaches to migrating from CodeDeploy blue/green to Amazo -### Reuse the same Elastic Load Balancing resources used for CodeDeploy +### Reuse the same ELB resources used for CodeDeploy @@ -106 +106 @@ Consider the following when using this approach: - * There is minimal disruption. It occurs only during the Elastic Load Balancing port swap. + * There is minimal disruption. It occurs only during the ELB port swap. @@ -108 +108 @@ Consider the following when using this approach: - * A rollback requires that you revert the Elastic Load Balancing port swap. + * A rollback requires that you revert the ELB port swap. @@ -138 +138 @@ Consider the following when using this approach: - * There is minimal disruption. It occurs only during the Elastic Load Balancing port swap. + * There is minimal disruption. It occurs only during the ELB port swap.