Checklist
Define the stop signal and recovery choice
Before deployment, decide what failure will stop the rollout and what happens next. Stopping new changes and reversing completed changes are different decisions.
Before you use it
- Use when
- A change can degrade service and people may hesitate to roll back once effort has been invested.
Keep this limit in mind
- Thresholds can be noisy or incomplete; allow human escalation when evidence is serious but the predefined metric misses it.
Current editorial reading
Make the trigger observable
Name the signal, its threshold or clear failure condition, the observation period and the person or automation allowed to act. For a data migration, a broken required relationship can trigger a halt while the affected records are examined. Choose values for the actual failure mode; an example percentage is not a general safety threshold.
Choose a recovery path that fits
State when to restore the previous version and when to fix the current state. A rollback must remain compatible with changed data and dependencies. If reversing the change is unsafe or incomplete, specify containment and a tested fix-forward plan. Keep an escalation route for serious evidence that the chosen metrics miss.
Take it with you
Walk through one simulated breach: can the responder identify the trigger, stop further exposure and choose a viable recovery path without inventing a rule?
Sources and evidence (1)
What we checked
AWS calls for documented, tested recovery plans and explicit requirements for rollback.
Selected official passages read on 2026-10-04. Signal selection and the simulated breach are editorial review actions, not experimentally validated thresholds.
OPS06-BP01 Plan for unsuccessful changes · Implementation guidance; Implementation steps 1 and 5
AWS explicitly allows fix-forward circumstances and discusses changes that cannot be rolled back.
Selected official passages read on 2026-10-04. A failure signal does not establish that reversal is the safest recovery action.
OPS06-BP01 Plan for unsuccessful changes · Implementation guidance; Implementation steps 1.1 and 4
Editorial sources (1)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDefine the stop signal and recovery choice
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaTest the rollback before you need it
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
AWS recommends documenting rollback criteria and the rollback or fix-forward plan before deploying a change.
Rollback is not always safer than fixing forward, particularly for irreversible data migrations; the strategy must match the change.
OPS06-BP01 Plan for unsuccessful changes · Implementation guidance
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details