AWS codedeploy documentation change
Summary
Consistently replaced 'ELB' with 'Elastic Load Balancing' throughout troubleshooting content
Security assessment
Terminology update without substantive changes to security guidance. Troubleshooting content remains functionally identical with no new security warnings or mitigations introduced.
Diff
diff --git a/codedeploy/latest/userguide/troubleshooting-ecs.md b/codedeploy/latest/userguide/troubleshooting-ecs.md index 0121cbd4a..1a96b8214 100644 --- a//codedeploy/latest/userguide/troubleshooting-ecs.md +++ b//codedeploy/latest/userguide/troubleshooting-ecs.md @@ -5 +5 @@ -A timeout occurs while waiting for replacement task setA timeout occurs while waiting for a notification to continueThe IAM role does not have enough permissionsThe deployment timed out while waiting for a status callbackThe deployment failed because one or more of the lifecycle event validation functions failedThe ELB could not be updated due to the following error: Primary taskset target group must be behind listenerMy deployment sometimes fails when using Auto ScalingOnly ALB supports gradual traffic routing, use AllAtOnce Traffic routing instead when you create/update Deployment groupEven though my deployment succeeded, the replacement task set fails the ELB health checks, and my application is downCan I attach multiple load balancers to a deployment group?Can I perform CodeDeploy blue/green deployments without a load balancer?How can I update my Amazon ECS service with new information during a deployment? +A timeout occurs while waiting for replacement task setA timeout occurs while waiting for a notification to continueThe IAM role does not have enough permissionsThe deployment timed out while waiting for a status callbackThe deployment failed because one or more of the lifecycle event validation functions failedThe ELB could not be updated due to the following error: Primary taskset target group must be behind listenerMy deployment sometimes fails when using Auto ScalingOnly ALB supports gradual traffic routing, use AllAtOnce Traffic routing instead when you create/update Deployment groupEven though my deployment succeeded, the replacement task set fails the Elastic Load Balancing health checks, and my application is downCan I attach multiple load balancers to a deployment group?Can I perform CodeDeploy blue/green deployments without a load balancer?How can I update my Amazon ECS service with new information during a deployment? @@ -27 +27 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa - * Even though my deployment succeeded, the replacement task set fails the ELB health checks, and my application is down + * Even though my deployment succeeded, the replacement task set fails the Elastic Load Balancing health checks, and my application is down @@ -121 +121 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -**Possible fix** : Make sure that the ELB's production listener and test listener are both pointing to the target group that's currently serving your workloads. There are three places to check: +**Possible fix** : Make sure that the Elastic Load Balancing's production listener and test listener are both pointing to the target group that's currently serving your workloads. There are three places to check: @@ -167 +167 @@ For more information about predefined deployment configurations, see [Predefined -## Even though my deployment succeeded, the replacement task set fails the ELB health checks, and my application is down +## Even though my deployment succeeded, the replacement task set fails the Elastic Load Balancing health checks, and my application is down @@ -169 +169 @@ For more information about predefined deployment configurations, see [Predefined -**Problem** : Even though CodeDeploy indicates that my deployment succeeded, the replacement task set fails the health checks from ELB, and my application is down. +**Problem** : Even though CodeDeploy indicates that my deployment succeeded, the replacement task set fails the health checks from Elastic Load Balancing, and my application is down. @@ -171 +171 @@ For more information about predefined deployment configurations, see [Predefined -**Possible cause** : This issue might occur if you performed a CodeDeploy all-at-once deployment, and your replacement (green) task set contains bad code that is causing the ELB health checks to fail. With the all-at-once deployment configuration, the load balancer’s health checks start running on the replacement task set _after_ traffic has been shifted to it (that is, _after_ CodeDeploy’s `AllowTraffic` lifecycle event occurs). That’s why you will see health checks failing on the replacement task set after traffic has shifted, but not before. For information about the lifecycle events that CodeDeploy generates, see [What happens during an Amazon ECS deployment](./deployment-steps-ecs.html#deployment-steps-what-happens). +**Possible cause** : This issue might occur if you performed a CodeDeploy all-at-once deployment, and your replacement (green) task set contains bad code that is causing the Elastic Load Balancing health checks to fail. With the all-at-once deployment configuration, the load balancer’s health checks start running on the replacement task set _after_ traffic has been shifted to it (that is, _after_ CodeDeploy’s `AllowTraffic` lifecycle event occurs). That’s why you will see health checks failing on the replacement task set after traffic has shifted, but not before. For information about the lifecycle events that CodeDeploy generates, see [What happens during an Amazon ECS deployment](./deployment-steps-ecs.html#deployment-steps-what-happens).