AWS AmazonECS documentation change
Summary
Replaced 'Elastic Load Balancing' with 'ELB' in multiple sections and updated a reference to Classic Load Balancers
Security assessment
The changes are purely terminological updates (replacing 'Elastic Load Balancing' with 'ELB') and do not alter security guidance. The IAM permission requirements remain unchanged, and there's no evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/AmazonECS/latest/developerguide/troubleshooting-blue-green.md b/AmazonECS/latest/developerguide/troubleshooting-blue-green.md index ad02caace..354bb4a31 100644 --- a//AmazonECS/latest/developerguide/troubleshooting-blue-green.md +++ b//AmazonECS/latest/developerguide/troubleshooting-blue-green.md @@ -114 +114 @@ _Error message_ : `All loadBalancers must be strictly either ELBv1 (defining loa -Classic Load Balancers are the previous generation of load balancers from Elastic Load Balancing. We recommend that you migrate to a current generation load balancer. For more information, see [Migrate your Classic Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.html). +Classic Load Balancers are the previous generation of load balancers from ELB. We recommend that you migrate to a current generation load balancer. For more information, see [Migrate your Classic Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-classic-load-balancer.html). @@ -178 +178 @@ _Error message_ : `service myService failed to describe target health on target- -_Solution_ : The IAM role used for managing load balancer resources does not have permission to read target health information. Add the `elasticloadbalancing:DescribeTargetHealth` permission to the role's policy. For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). +_Solution_ : The IAM role used for managing load balancer resources does not have permission to read target health information. Add the `elasticloadbalancing:DescribeTargetHealth` permission to the role's policy. For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). @@ -185 +185 @@ _Error message_ : `service myService failed to register targets in target-group -_Solution_ : The IAM role used for managing load balancer resources does not have permission to register targets. Add the `elasticloadbalancing:RegisterTargets` permission to the role's policy. For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). +_Solution_ : The IAM role used for managing load balancer resources does not have permission to register targets. Add the `elasticloadbalancing:RegisterTargets` permission to the role's policy. For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). @@ -192 +192 @@ _Error message_ : `Service deployment rolled back because TEST_TRAFFIC_SHIFT lif -_Solution_ : The IAM role used for managing load balancer resources does not have permission to modify listeners. Add the `elasticloadbalancing:ModifyListener` permission to the role's policy. For information about Elastic Load Balancing permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html). +_Solution_ : The IAM role used for managing load balancer resources does not have permission to modify listeners. Add the `elasticloadbalancing:ModifyListener` permission to the role's policy. For information about ELB permissions, see [Amazon ECS infrastructure IAM role for load balancers](./AmazonECSInfrastructureRolePolicyForLoadBalancers.html).