AWS AmazonECS documentation change
Summary
Replaced 'ELB' with 'Elastic Load Balancing' in three locations for terminology consistency
Security assessment
Changes are purely terminological updates from abbreviations to full product names. No security-related content was added or modified.
Diff
diff --git a/AmazonECS/latest/developerguide/deploy-blue-green-service.md b/AmazonECS/latest/developerguide/deploy-blue-green-service.md index 795c3d1dd..c4b5b1932 100644 --- a//AmazonECS/latest/developerguide/deploy-blue-green-service.md +++ b//AmazonECS/latest/developerguide/deploy-blue-green-service.md @@ -17 +17 @@ Perform the following operations before you start a blue/green deployment. - * For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). + * For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). @@ -108 +108 @@ Launch type | - 4. For **Health check grace period** , enter the amount of time (in seconds) that the 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. + 4. For **Health check grace period** , enter the amount of time (in seconds) that the 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. @@ -188 +188 @@ The following describes each container log destination in more detail. -ELB type | Steps +Elastic Load Balancing type | Steps