AWS AmazonECS documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' for clarity and consistency
Security assessment
The changes only expand ELB acronym to full product name without altering functionality or security configuration. No security implications or vulnerability fixes are mentioned.
Diff
diff --git a/AmazonECS/latest/developerguide/service_definition_parameters.md b/AmazonECS/latest/developerguide/service_definition_parameters.md index 3a174ef9f..e2e1269b7 100644 --- a//AmazonECS/latest/developerguide/service_definition_parameters.md +++ b//AmazonECS/latest/developerguide/service_definition_parameters.md @@ -503 +503 @@ Required: No -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 do not specify a health check grace period value, the default value of 0 is used. If you do not 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 do not specify a health check grace period value, the default value of 0 is used. If you do not use any of the health checks, then `healthCheckGracePeriodSeconds` is unused. @@ -520 +520 @@ When you update a service, this parameter triggers a new service deployment. -After you create a service, the load balancer configuration can't be changed from the AWS Management Console. You can use the AWS Copilot, AWS CloudFormation, AWS CLI or SDK to modify the load balancer configuration for the `ECS` rolling deployment controller only, not AWS CodeDeploy blue/green or external. When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers. We recommend that you verify this on a test environment before you update the ELB configuration. For information about how to modify the configuration, see [UpdateService](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html) in the _Amazon Elastic Container Service API Reference_. +After you create a service, the load balancer configuration can't be changed from the AWS Management Console. You can use the AWS Copilot, AWS CloudFormation, AWS CLI or SDK to modify the load balancer configuration for the `ECS` rolling deployment controller only, not AWS CodeDeploy blue/green or external. When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers. We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration. For information about how to modify the configuration, see [UpdateService](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html) in the _Amazon Elastic Container Service API Reference_. @@ -531 +531 @@ Required: No -The full Amazon Resource Name (ARN) of the ELB target group that's associated with a service. +The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group that's associated with a service.