medium riskcluster affecting~20 min
Runbook: Rollback to a Previous State Version
1 · Prerequisites
Confirm every item is in place before any state change.
- The state has multiple versions (S3 versioning)
- A previous version is known-good
2 · Pre-checks
Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.
- · The state backend has versioning enabled
- · The previous version is verified
3 · Procedure
Execute each step in order. Verify the expected output of a step before moving to the next.
- 1Identify the version to roll back to
- 2Stop all apply operations
- 3Roll back the state to the previous version
- 4Verify the state is consistent
- 5Document the rollback
4 · Verification
Confirm the procedure actually fixed the problem.
- ✓State is at the previous version
- ✓Plan is empty
- ✓Rollback is documented
5 · Rollback
If verification fails, undo the procedure in reverse order.
- ↶If the rollback is wrong, re-apply from a different version
6 · Escalation
When the runbook isn't enough, contact:
- · If the rollback breaks production, escalate to incident response