AWS AmazonECS documentation change
Summary
Updated documentation for managed daemon deployments, adding a new STOPPED state, clarifying deployment circuit breaker behavior, updating parameter descriptions for drainPercent and bakeTimeInMinutes, and reordering alarm configuration details.
Security assessment
The changes are documentation improvements and clarifications about deployment states and configuration parameters. There is no evidence of addressing a specific security vulnerability or weakness. The changes mention CloudWatch alarms and automatic rollback features, but these are existing deployment safety mechanisms rather than new security features or fixes for security issues.
Diff
diff --git a/AmazonECS/latest/developerguide/managed-daemons-deployments.md b/AmazonECS/latest/developerguide/managed-daemons-deployments.md index 10ba6bc19..4821dd638 100644 --- a//AmazonECS/latest/developerguide/managed-daemons-deployments.md +++ b//AmazonECS/latest/developerguide/managed-daemons-deployments.md @@ -17 +17 @@ The deployment lifecycle transitions through the following states: - 1. `PENDING` \- ECS has created the deployment and is preparing to begin. + 1. `PENDING` \- Amazon ECS has created the deployment and is preparing to begin. @@ -19 +19 @@ The deployment lifecycle transitions through the following states: - 2. `IN_PROGRESS` \- ECS is actively draining instances and provisioning replacements. + 2. `IN_PROGRESS` \- Amazon ECS is actively draining instances and provisioning replacements. @@ -22,0 +23 @@ The deployment lifecycle transitions through the following states: + 4. `STOPPED` \- Amazon ECS has stopped the deployment because it failed or was replaced by a new deployment. The daemon may be in a mixed state where some instances run the old revision and others run the new revision. @@ -26 +27,2 @@ The deployment lifecycle transitions through the following states: -If a deployment fails or a CloudWatch alarm triggers, Amazon ECS can automatically roll back to the previous daemon revision by using circuit breaker protection. + +Amazon ECS automatically rolls back to the previous daemon revision if the deployment circuit breaker detects failures or if a CloudWatch alarm triggers during the deployment. @@ -32 +34 @@ You can customize deployment behavior by using the `deploymentConfiguration` par - * `drainPercent` (0.0 to 100.0) - The percentage of instances to drain simultaneously during the deployment. Higher values speed up deployments but may temporarily reduce available capacity. For example, a value of `20.0` drains 20% of instances at a time. + * `drainPercent` (1.0–100.0) - The percentage of instances to drain simultaneously during the deployment. Higher values speed up deployments but may temporarily reduce available capacity. For example, a value of `20.0` drains 20% of instances at a time. If not specified, the default is `25.0`. @@ -34 +36 @@ You can customize deployment behavior by using the `deploymentConfiguration` par - * `bakeTimeInMinutes` (integer) - The number of minutes to wait after deploying the daemon to an instance before moving to the next batch. This gives you time to verify the new daemon is healthy before continuing the rollout. + * `alarms` (`DaemonAlarmConfiguration`) - CloudWatch alarms to monitor during the deployment. Amazon ECS evaluates the specified alarms during the deployment and automatically rolls back if any alarm enters the `ALARM` state. Amazon ECS ignores alarms that are already in the `ALARM` state when the deployment begins. @@ -36 +38 @@ You can customize deployment behavior by using the `deploymentConfiguration` par - * `alarms` (`DaemonAlarmConfiguration`) - CloudWatch alarms to monitor during the deployment. If any specified alarm enters the `ALARM` state, Amazon ECS can automatically roll back the deployment. + * `bakeTimeInMinutes` (0–1440) - The number of minutes that Amazon ECS waits after it updates all instances to the new daemon revision before it completes the deployment. During this period, Amazon ECS monitors CloudWatch alarms and automatically rolls back the deployment if any alarm triggers. If not specified, the default is `0`.