AWS AmazonECS documentation change
Summary
Expanded lifecycle hooks to include pause functionality alongside Lambda functions. Added timeout configuration for pause hooks (up to 14 days) and clarified lifecycle stage behaviors.
Security assessment
Changes enhance deployment flexibility by introducing manual pause points but contain no references to vulnerabilities, security incidents, or protective measures. Updates are operational improvements without security implications.
Diff
diff --git a/AmazonECS/latest/developerguide/canary-deployment.md b/AmazonECS/latest/developerguide/canary-deployment.md index fa8cf0c43..e0255e809 100644 --- a//AmazonECS/latest/developerguide/canary-deployment.md +++ b//AmazonECS/latest/developerguide/canary-deployment.md @@ -27 +27 @@ The following are resources involved in Amazon ECS canary deployments: - * Lifecycle hook - A Lambda function that runs at a specific lifecycle stage. You can create a function that verifies the deployment. + * Lifecycle hook - A Lambda function or pause point at a specific lifecycle stage. Lambda hooks invoke Lambda functions that you have defined to run custom code. Pause hooks pause the deployment and wait for you to call `ContinueServiceDeployment` to proceed. @@ -88 +88 @@ The canary traffic shift phase follows these steps: - * Lifecycle hooks - Optional Lambda functions can be executed at various lifecycle stages during the deployment to perform automated validation, monitoring, or custom logic. Lambda functions or lifecycle hooks configured for PRODUCTION_TRAFFIC_SHIFT will be invoked at every production traffic shift step. + * Lifecycle hooks - Optional Lambda functions or pause hooks can be configured at various lifecycle stages during the deployment to perform automated validation, monitoring, or custom logic. Hooks configured for `PRODUCTION_TRAFFIC_SHIFT` or `PRE_PRODUCTION_TRAFFIC_SHIFT` are invoked at every production traffic shift step. @@ -100,0 +101,2 @@ CloudFormation deployments have additional timeout restrictions. While the 24-ho +For pause hooks, the timeout can be configured up to 20,160 minutes (14 days). The overall deployment timeout is 30 days. + @@ -107 +109 @@ POST_SCALE_UP | The green service revision has started. The blue service revisio -TEST_TRAFFIC_SHIFT | The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic. | Yes +TEST_TRAFFIC_SHIFT | The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic. | Yes (Lambda only) @@ -109 +111,2 @@ POST_TEST_TRAFFIC_SHIFT | The test traffic shift is complete. The green service -PRODUCTION_TRAFFIC_SHIFT | Canary production traffic is routed to green revision and lifecycle hook is invoked with 24 hours timeout. The second step shifts remaining production traffic to green revision. | Yes +PRE_PRODUCTION_TRAFFIC_SHIFT | Occurs before each production traffic shift step. For canary, this occurs before the canary traffic shift and before the remaining traffic shift. | Yes +PRODUCTION_TRAFFIC_SHIFT | Canary production traffic is routed to green revision and lifecycle hook is invoked with 24 hours timeout. The second step shifts remaining production traffic to green revision. | Yes (Lambda only)