# Pagerless for AWS ECS

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless deploys the previous task definition.

URL: https://pagerless.dev/integrations/aws-ecs
Updated: 2026-10-22

## Set up

Node, Go or Python SDK in the container.

Store the key with SSM Parameter Store: connect writes `pagerless.tf` so ECS reads `/pagerless/<app>/key`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on AWS ECS

| Fix | On AWS ECS |
| --- | --- |
| Undo the update | Deploys the previous task definition |
| Restart | Forces a new deployment |
| Add capacity | Changes desired count |
| Deploy events | Yes: errors right after a deploy are tied to it |
| Access it needs | an IAM role you create with a CloudFormation link, with an external ID |

## Questions

### Can Pagerless roll back AWS ECS automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then deploys the previous task definition.

### Does Pagerless need admin access to AWS ECS?

It needs an IAM role you create with a CloudFormation link, with an external ID. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.