Taking Control of Your Deployments: Pause and Continue Controls in Amazon ECS

Deploying containerized applications in production involves more than just pushing new task definitions. Teams often need manual checkpoints, such as approvals, final integration tests, or validating canary metrics, before shifting traffic. Until recently, Amazon ECS lacked native support for these controls, forcing teams to manage them externally. On May 19, 2026, AWS introduced pause-and-continue controls for ECS deployments, enabling built-in, configurable pause points so teams can pause, resume, or roll back deployments at critical stages.

What the Feature Does

This capability introduces a new PAUSE deployment lifecycle hook type in Amazon ECS. When configured, it instructs ECS to pause deployment at a specified lifecycle stage and wait for an explicit signal before continuing. The key behaviors are:

• When a deployment reaches a configured pause point, Amazon ECS pauses and emits an Amazon EventBridge event with the detail-type ECS Hook State Change and event name HOOK_AWAITING_ACTION.
• The deployment stays paused until you call the new ContinueServiceDeployment API with the hookId and an action of CONTINUE or ROLLBACK.
• You can retrieve the hookId by calling DescribeServiceDeployments, which returns a lifecycleHookDetails array showing the hook status and expiry time.
• Pause hooks work alongside existing deployment features; managed traffic shifting, bake times, CloudWatch alarm-based rollbacks, and the deployment circuit breaker all continue to function as before.

How It Works

The PAUSE hook is configured in the ECS service deployment configuration under lifecycleHooks. Each hook requires a targetType of PAUSE and one or more lifecycleStages at which to pause. Supported lifecycle stages are:

• RECONCILE_SERVICE
• PRE_SCALE_UP
• POST_SCALE_UP
• POST_TEST_TRAFFIC_SHIFT
• PRE_PRODUCTION_TRAFFIC_SHIFT
• POST_PRODUCTION_TRAFFIC_SHIFT

Note that pause hooks cannot be configured at the TEST_TRAFFIC_SHIFT or PRODUCTION_TRAFFIC_SHIFT stages.

You can also configure a timeoutConfiguration with a timeoutInMinutes value between 1 and 20,160 (equivalent to 14 days), and a timeout action of either ROLLBACK (the default) or CONTINUE. If no call to ContinueServiceDeployment is made before the timeout expires, ECS automatically takes the configured action. The default timeout when not specified is 1,440 minutes (24 hours).

For linear and canary deployments, the pause hook at PRE_PRODUCTION_TRAFFIC_SHIFT is invoked at each traffic-shift step. Each invocation generates a new hookId and requires a separate ContinueServiceDeployment call, giving teams fine-grained per-step control throughout the entire traffic migration.

Getting Started

Pause hooks can be configured across rolling, blue/green, linear, and canary deployment strategies. The tooling support is broad:

• Amazon ECS Console, AWS CLI, and AWS SDKs for configuring pause hooks and calling ContinueServiceDeployment.
• AWS CloudFormation, AWS CDK, and Terraform for infrastructure-as-code workflows.

A typical workflow looks like this:

• Add a PAUSE lifecycle hook with targetType set to PAUSE and the desired lifecycleStages to your ECS service deployment configuration.
• When the deployment reaches the pause stage, ECS emits an EventBridge event (HOOK_AWAITING_ACTION), which can trigger an approval workflow, a Slack notification, or any automation you have wired up.
• Retrieve the hookId via DescribeServiceDeployments.
• Call ContinueServiceDeployment with the hookId and action CONTINUE to proceed, or ROLLBACK to revert to the previous service revision.

If multiple hooks are configured at the same lifecycle stage, including a mix of Lambda hooks and pause hooks, the deployment stays paused until all hooks at that stage are resolved. If any hook triggers a rollback, the entire deployment rolls back, regardless of the status of the other hooks. All hooks at the same stage run in parallel.

Where This Matters Most

This feature is particularly valuable in a few common scenarios:

• Manual approval gates: Compliance-sensitive teams can pause after test traffic has shifted (POST_TEST_TRAFFIC_SHIFT) and require a human sign-off before production traffic moves.
• Integration test windows: Teams can hold a deployment open long enough to run a full test suite against the test endpoint, without needing to architect an external polling mechanism.
• Canary and linear validation: With per-step pause hooks on PRE_PRODUCTION_TRAFFIC_SHIFT, operators can inspect metrics after each traffic increment before allowing the next shift to proceed.
• External system coordination: Deployments can be paused to synchronize with external processes, change management ticketing, downstream dependency checks, or custom automation, using EventBridge as the trigger.

Things to Keep in Mind

A few constraints are worth noting before you configure pause hooks:

• A maximum of 10 lifecycle hooks of a given type can be configured per lifecycle stage.
• Pause hooks do not use hookTargetArn or roleArn; those fields are reserved for Lambda hooks.
• Pause hooks cannot be placed at the TEST_TRAFFIC_SHIFT or PRODUCTION_TRAFFIC_SHIFT stages.
• For linear and canary deployments, each traffic shift step at PRE_PRODUCTION_TRAFFIC_SHIFT produces a separate hookId. Plan your automation accordingly.
• Always monitor the expiresAt field in the DescribeServiceDeployments response to ensure your pause window stays within the configured timeout.

Smarter ECS Deployments

Pause-and-continue controls for Amazon ECS deployments fill a key gap in the native toolchain. By adding human-in-the-loop controls directly into the ECS lifecycle, with EventBridge integration, timeouts up to 14 days, and support for rolling, blue/green, linear, and canary strategies, AWS enables structured approval gates without external orchestration. The feature is free across all AWS commercial and GovCloud (US) Regions. To get started, review the ECS pause hook documentation, add a PAUSE lifecycle hook to your service, and connect EventBridge events to your approval or automation workflow.