Set up
Node SSR: pagerless/auto. Static: pagerless/browser.
Store the key with Amplify environment variables. Or run npx pagerless connect and it finds your services and places the key for you.
Fixes on AWS Amplify
| Fix | On AWS Amplify |
|---|---|
| Undo the update | Re-runs the last good build |
| Restart | Not available |
| Add capacity | Not available |
| Deploy events | Yes: errors right after a deploy are tied to it |
| Access it needs | an IAM role with an external ID |
Questions
Can Pagerless roll back AWS Amplify 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 re-runs the last good build.
Does Pagerless need admin access to AWS Amplify?
It needs an IAM role with an external ID. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.