AWS AmazonECS documentation change
Summary
Updated terminology from 'Elastic Load Balancing' to 'ELB' and 'blue/green' to 'linear' in multiple sections. Changed test traffic routing context from blue/green to linear deployments.
Security assessment
Changes are terminology updates and context alignment with deployment types. No security vulnerabilities, mitigations, or security features are mentioned. Updates focus on naming consistency rather than security implications.
Diff
diff --git a/AmazonECS/latest/developerguide/deploy-linear-service.md b/AmazonECS/latest/developerguide/deploy-linear-service.md index 63890d764..e2cec423f 100644 --- a//AmazonECS/latest/developerguide/deploy-linear-service.md +++ b//AmazonECS/latest/developerguide/deploy-linear-service.md @@ -17 +17 @@ Perform the following operations before you start a linear deployment. - * For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). + * For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). @@ -25 +25 @@ Perform the following operations before you start a linear deployment. - 3. Create a rule to route traffic to your new service revision. For more information, see [Listener rules](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-rules.html) in the _Elastic Load Balancing Application Load Balancers_. + 3. Create a rule to route traffic to your new service revision. For more information, see [Listener rules](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-rules.html) in the _ELB Application Load Balancers_. @@ -27 +27 @@ Perform the following operations before you start a linear deployment. - 4. Create a target group for your green service revision. When you use the `awsvpc` network mode for your tasks, the target type must be `ip`. For information about target groups, see [Target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html) in the _Elastic Load Balancing Application Load Balancers_. + 4. Create a target group for your green service revision. When you use the `awsvpc` network mode for your tasks, the target type must be `ip`. For information about target groups, see [Target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html) in the _ELB Application Load Balancers_. @@ -88 +88 @@ Launch type | - 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. + 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. @@ -134 +134 @@ To have the software automatically roll back the deployment to the last complete - 4. (Optional) Configure test traffic header rules for blue/green deployments. Under **Test traffic routing** , specify the following: + 4. (Optional) Configure test traffic header rules for linear deployments. Under **Test traffic routing** , specify the following: @@ -174 +174 @@ The following describes each container log destination in more detail. - 10. (Optional) Configure **Load balancing** for blue/green deployment. + 10. (Optional) Configure **Load balancing** for linear deployment. @@ -176 +176 @@ The following describes each container log destination in more detail. -Elastic Load Balancing type | Steps +ELB type | Steps