AWS AmazonECS documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' throughout the documentation for consistency and clarity
Security assessment
Changes are purely terminological updates (ELB → Elastic Load Balancing) with no security implications. No vulnerabilities, security fixes, or security features are mentioned or modified.
Diff
diff --git a/AmazonECS/latest/developerguide/update-service-parameters.md b/AmazonECS/latest/developerguide/update-service-parameters.md index 5e00245dd..4ed4dd37e 100644 --- a//AmazonECS/latest/developerguide/update-service-parameters.md +++ b//AmazonECS/latest/developerguide/update-service-parameters.md @@ -196 +196 @@ You can change this parameter for rolling deployments. -The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy ELB, VPC Lattice, and container health checks after a task has first started. If you don't specify a health check grace period value, the default value of `0` is used. If you don't use any of the health checks, then `healthCheckGracePeriodSeconds` is unused. +The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing, VPC Lattice, and container health checks after a task has first started. If you don't specify a health check grace period value, the default value of `0` is used. If you don't use any of the health checks, then `healthCheckGracePeriodSeconds` is unused. @@ -207 +207 @@ You must use a service-linked role when you update a load balancer. -A list of ELB load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition. +A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition. @@ -209 +209 @@ A list of ELB load balancer objects. It contains the load balancer name, the con -Amazon ECS does not automatically update the security groups associated with ELB load balancers or Amazon ECS container instances. +Amazon ECS does not automatically update the security groups associated with Elastic Load Balancing load balancers or Amazon ECS container instances. @@ -211 +211 @@ Amazon ECS does not automatically update the security groups associated with ELB -When you add, update, or remove a load balancer configuration, Amazon ECS starts new tasks with the updated ELB configuration, and then stops the old tasks when the new tasks are running. +When you add, update, or remove a load balancer configuration, Amazon ECS starts new tasks with the updated Elastic Load Balancing configuration, and then stops the old tasks when the new tasks are running. @@ -213 +213 @@ When you add, update, or remove a load balancer configuration, Amazon ECS starts -For services that use rolling updates, you can add, update, or remove ELB target groups. You can update from a single target group to multiple target groups and from multiple target groups to a single target group. +For services that use rolling updates, you can add, update, or remove Elastic Load Balancing target groups. You can update from a single target group to multiple target groups and from multiple target groups to a single target group. @@ -215 +215 @@ For services that use rolling updates, you can add, update, or remove ELB target -For services that use blue/green deployments, you can update ELB target groups by using `[CreateDeployment](https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html)` through CodeDeploy. Note that multiple target groups are not supported for blue/green deployments. For more information see [Register multiple target groups with a service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html). +For services that use blue/green deployments, you can update Elastic Load Balancing target groups by using `[CreateDeployment](https://docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html)` through CodeDeploy. Note that multiple target groups are not supported for blue/green deployments. For more information see [Register multiple target groups with a service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html).