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
Multi-Cloud and Hybrid Infrastructure
Most multi-cloud is accidental: an acquisition, a credits deal, or one team that chose differently. Running it deliberately means deciding what genuinely needs to be portable and accepting managed services everywhere else.
No sales layer, no juniors. You meet the engineer before anything begins.
// What is included
What you get
- An honest assessment of what portability is actually costing you
- One Terraform codebase and one deployment path across providers
- Identity, secrets and networking handled consistently rather than per cloud
- A single view of cost across accounts and providers
// How it runs
The sequence
- 01
Map
What runs where, why, and what it would take to consolidate.
- 02
Unify
One pipeline, one IaC layout, one set of conventions.
- 03
Decide
Keep, consolidate or migrate, argued on cost and staffing.
// Stack
- AWS
- GCP
- Azure
- DigitalOcean
- Hetzner
- Terraform
// Related work
Where this has been done before
Client names under NDA. The numbers are not.
// 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.