Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Sample deliverable · Data & Databases

Sample cut-over runbook: PostgreSQL major upgrade with blue/green

A step-by-step runbook excerpt with timings, owners, checks and the rollback path.

Sample / template. Fictional systems and figures that show the format and depth of what you receive. Not a client deliverable.

System: reporting-db (fictional), Amazon RDS for PostgreSQL 14 to 16 · Method: blue/green deployment · Rehearsed: twice, switchover measured at under 1 minute in rehearsal

Roles

  • Change lead: runs the runbook and calls go/no-go
  • Application owner: runs smoke tests
  • Observer: watches dashboards and records timings

Go/no-go criteria

  • Green environment in sync, replica lag under 1 second
  • Latest snapshot under 1 hour old
  • Application owner and change lead present

Steps

TimeStepOwnerCheck
T-24hFreeze schema changes; confirm change approvalChange leadApproval recorded
T-60mTake manual snapshot of blueChange leadSnapshot available
T-30mConfirm green parameters, extensions and replica lagChange leadLag under 1s
T-10mGo/no-go callAllCriteria met
T-0Start switchoverChange leadEvent log shows switchover
T+5mRun smoke tests and data checksApp ownerAll pass
T+15mCompare latency and errors with baselineObserverWithin agreed limits
T+30mDeclare complete or roll backChange leadDecision recorded

Rollback

If checks fail before T+30m, switch traffic back to the retained blue environment using the rehearsed steps (measured in rehearsal), then restore from the T-60m snapshot only if blue is unusable. Rollback was rehearsed and timed before the change was approved.

After the change

  • Run ANALYZE on large tables and watch query plans for 48 hours
  • Keep blue for 7 days, then delete after sign-off
  • Update documentation and the upgrade calendar

Want this for your systems?

Every paid assessment ends in a document like this, with your real systems, risks and a fixed quote. The fee is credited to the project.