AWS codedeploy documentation change
Summary
Updated terminology from 'Auto Scaling' to 'Amazon EC2 Auto Scaling' and 'Elastic Load Balancing' to 'ELB' for consistency. Added explicit references to EC2 Auto Scaling in problem descriptions and solutions.
Security assessment
Changes are terminology updates and clarifications about service names (EC2 Auto Scaling vs generic Auto Scaling). No security vulnerabilities or security feature enhancements are mentioned. The modifications focus on operational reliability by clarifying service interactions, but don't address security controls or vulnerabilities.
Diff
diff --git a/codedeploy/latest/userguide/troubleshooting-ecs.md b/codedeploy/latest/userguide/troubleshooting-ecs.md index 1a96b8214..83b83e4cd 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 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? +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 Amazon EC2 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? @@ -23 +23 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa - * My deployment sometimes fails when using Auto Scaling + * My deployment sometimes fails when using Amazon EC2 Auto Scaling @@ -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 Elastic Load Balancing health checks, and my application is down + * Even though my deployment succeeded, the replacement task set fails the ELB 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 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: +**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: @@ -132 +132 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -## My deployment sometimes fails when using Auto Scaling +## My deployment sometimes fails when using Amazon EC2 Auto Scaling @@ -134 +134 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -**Problem** : You are using Auto Scaling with CodeDeploy and you notice that your deployments occasionally fail. For more information about the symptoms of this problem, see the topic that reads [For services configured to use service auto scaling and the blue/green deployment type, auto scaling is not blocked during a deployment but the deployment may fail under some circumstances](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html#deployment-type-bluegreen-considerations) in the _Amazon Elastic Container Service Developer Guide_. +**Problem** : You are using Amazon EC2 Auto Scaling with CodeDeploy and you notice that your deployments occasionally fail. For more information about the symptoms of this problem, see the topic that reads [For services configured to use service auto scaling and the blue/green deployment type, auto scaling is not blocked during a deployment but the deployment may fail under some circumstances](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html#deployment-type-bluegreen-considerations) in the _Amazon Elastic Container Service Developer Guide_. @@ -136 +136 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -**Possible cause** : This problem might occur if CodeDeploy and Auto Scaling processes conflict. +**Possible cause** : This problem might occur if CodeDeploy and Amazon EC2 Auto Scaling processes conflict. @@ -138 +138 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -**Possible fix** : Suspend and resume Auto Scaling processes during the CodeDeploy deployment using the `RegisterScalableTarget` API (or the corresponding `register-scalable-target` AWS CLI command). For more information, see [Suspend and resume scaling for Application Auto Scaling](https://docs.aws.amazon.com/autoscaling/application/userguide/application-auto-scaling-suspend-resume-scaling.html) in the _Application Auto Scaling User Guide_. +**Possible fix** : Suspend and resume Amazon EC2 Auto Scaling processes during the CodeDeploy deployment using the `RegisterScalableTarget` API (or the corresponding `register-scalable-target` AWS CLI command). For more information, see [Suspend and resume scaling for Application Auto Scaling](https://docs.aws.amazon.com/autoscaling/application/userguide/application-auto-scaling-suspend-resume-scaling.html) in the _Application Auto Scaling User Guide_. @@ -142 +142 @@ A timeout occurs while waiting for replacement task setA timeout occurs while wa -CodeDeploy can't call `RegisterScaleableTarget` directly. To use this API, you must configure CodeDeploy to send a notification or event to Amazon Simple Notification Service (or Amazon CloudWatch). You must then configure Amazon SNS (or CloudWatch) to call a Lambda function, and configure the Lambda function to call the `RegisterScalableTarget` API. The `RegisterScalableTarget` API must be called with the `SuspendedState` parameter set to `true` to suspend Auto Scaling operations, and `false` to resume them. +CodeDeploy can't call `RegisterScaleableTarget` directly. To use this API, you must configure CodeDeploy to send a notification or event to Amazon Simple Notification Service (or Amazon CloudWatch). You must then configure Amazon SNS (or CloudWatch) to call a Lambda function, and configure the Lambda function to call the `RegisterScalableTarget` API. The `RegisterScalableTarget` API must be called with the `SuspendedState` parameter set to `true` to suspend Amazon EC2 Auto Scaling operations, and `false` to resume them. @@ -144 +144 @@ CodeDeploy can't call `RegisterScaleableTarget` directly. To use this API, you m -The notification or event that CodeDeploy sends out must occur when a deployment starts (to trigger Auto Scaling suspend operations), or when a deployment succeeds, fails, or stops (to trigger Auto Scaling resume operations). +The notification or event that CodeDeploy sends out must occur when a deployment starts (to trigger Amazon EC2 Auto Scaling suspend operations), or when a deployment succeeds, fails, or stops (to trigger Amazon EC2 Auto Scaling resume operations). @@ -167 +167 @@ For more information about predefined deployment configurations, see [Predefined -## Even though my deployment succeeded, the replacement task set fails the Elastic Load Balancing health checks, and my application is down +## Even though my deployment succeeded, the replacement task set fails the ELB 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 Elastic Load Balancing, and my application is down. +**Problem** : Even though CodeDeploy indicates that my deployment succeeded, the replacement task set fails the health checks from ELB, 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 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). +**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).