AWS codedeploy documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' throughout the document and corrected references to the user guide name
Security assessment
The changes only involve branding/terminology updates (ELB → Elastic Load Balancing) and documentation reference corrections. No security vulnerabilities, configurations, or features are mentioned or modified in the diff.
Diff
diff --git a/codedeploy/latest/userguide/deployment-steps-ecs.md b/codedeploy/latest/userguide/deployment-steps-ecs.md index 30ba073ef..a28a326e8 100644 --- a//codedeploy/latest/userguide/deployment-steps-ecs.md +++ b//codedeploy/latest/userguide/deployment-steps-ecs.md @@ -71 +71 @@ Application Load Balancer or Network Load Balancer** -You must use ELB with the Amazon ECS service you want to update with an Amazon ECS deployment. You can use an Application Load Balancer or a Network Load Balancer. We recommend an Application Load Balancer so you can take advantage of features such as dynamic port mapping and path-based routing and priority rules. You specify the load balancer when you create your CodeDeploy application's deployment group. For more information, see [Set up a load balancer, target groups, and listeners for CodeDeploy Amazon ECS deployments](./deployment-groups-create-load-balancer-for-ecs.html) and [Creating a load balancer](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-load-balancer.html) in the _Amazon Elastic Container Service User Guide_. +You must use Elastic Load Balancing with the Amazon ECS service you want to update with an Amazon ECS deployment. You can use an Application Load Balancer or a Network Load Balancer. We recommend an Application Load Balancer so you can take advantage of features such as dynamic port mapping and path-based routing and priority rules. You specify the load balancer when you create your CodeDeploy application's deployment group. For more information, see [Set up a load balancer, target groups, and listeners for CodeDeploy Amazon ECS deployments](./deployment-groups-create-load-balancer-for-ecs.html) and [Creating a load balancer](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-load-balancer.html) in the _Amazon Elastic Container Service User Guide_. @@ -78 +78 @@ One or two listeners** -A _listener_ is used by your load balancer to direct traffic to your target groups. One production listener is required. You can specify an optional second test listener that directs traffic to your replacement task set while you run validation tests. You specify one or both listeners when you create your deployment group. If you use the Amazon ECS console to create your Amazon ECS service, your listeners are created for you. For more information, see [Listeners for your application load balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listener.html) in the _ELB User Guide_ and [Creating a service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service.html) in the _Amazon Elastic Container Service User Guide_. +A _listener_ is used by your load balancer to direct traffic to your target groups. One production listener is required. You can specify an optional second test listener that directs traffic to your replacement task set while you run validation tests. You specify one or both listeners when you create your deployment group. If you use the Amazon ECS console to create your Amazon ECS service, your listeners are created for you. For more information, see [Listeners for your application load balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listener.html) in the _Elastic Load Balancing User Guide_ and [Creating a service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service.html) in the _Amazon Elastic Container Service User Guide_. @@ -87 +87 @@ A _target group_ is used to route traffic to a registered target. An Amazon ECS -During a deployment, CodeDeploy determines which target group is associated with the task set in your Amazon ECS service that has the status `PRIMARY` (this is the original task set) and associates one target group with it, and then associates the other target group with the replacement task set. If you do another deployment, the target group associated with the current deployment's original task set is associated with the next deployment's replacement task set. For more information, see [Target groups for your application load balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html) in the _ELB User Guide_. +During a deployment, CodeDeploy determines which target group is associated with the task set in your Amazon ECS service that has the status `PRIMARY` (this is the original task set) and associates one target group with it, and then associates the other target group with the replacement task set. If you do another deployment, the target group associated with the current deployment's original task set is associated with the next deployment's replacement task set. For more information, see [Target groups for your application load balancers](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html) in the _Elastic Load Balancing User Guide_.