Self-hosted infrastructure retired onto managed services (NDA)
- Self-managed Kubernetes to ECS and Fargate
- Configuration store to Parameter Store and Secrets Manager
- Artifact repository to ECR and CodeArtifact
Four self-maintained components retired
Cloud
Backup and Disaster Recovery
Almost everyone has backups. Far fewer have ever restored from them, and that is the only test that counts. Disaster recovery work is mostly about turning an assumption into a rehearsed procedure.
No sales layer, no juniors. You meet the engineer before anything begins.
// What is included
What you get
- Recovery objectives agreed in numbers, then designed against
- Backups verified by performing a real restore, not by checking a green tick
- Infrastructure recreatable from code, so recovery is not manual archaeology
- A written runbook for the scenarios that would actually happen
// How it runs
The sequence
- 01
Define
How much data loss and how much downtime you can genuinely accept.
- 02
Close
Fix the gap between that number and what is currently possible.
- 03
Rehearse
Run the restore, time it, and write down what went wrong.
// Stack
- AWS
- Amazon S3
- Amazon RDS
- Terraform
- AWS Backup
// Related work
Where this has been done before
Client names under NDA. The numbers are not.
Zero-downtime Redis to ElastiCache migration (martech SaaS, NDA)
- Replication-based sync kept both caches current
- Circuit breaker in the application path to fail safe
- Traffic cut over in stages, verified at each step
0 minutes of user-facing downtime
// Questions
Before you ask
// Also in Cloud
Related services
Talk to the engineer who would do the work
A 20 minute call. You describe your setup, you get an honest read on whether this helps, and the top risks worth looking at first.