Define the support boundary
- Name the AWS accounts, environments and applications included.
- Separate application-vendor support from infrastructure operations.
- Agree support hours, incident severity and escalation contacts.
Transfer usable runbooks
- Document a safe restart and a failed-release rollback.
- Record backup locations, retention and the latest restore test.
- Confirm who approves maintenance and emergency changes.
Prove the handover works
- Send a test alarm through the agreed notification path.
- Walk through an incident with the application owner.
- Review open issues and give each one a responsible owner.
Bring this to your next discussion
Bring the completed list to the service onboarding discussion. Coverage and response objectives belong in the agreed service schedule.
Explore the related service