Health-tech platform modernization
Release velocity and scale were constrained by a legacy monolith. Cloudhew migrated the platform to Amazon EKS with GitOps and CI/CD, and transferred operations to the client platform team.
Situation
A single deployable unit meant every change carried the blast radius of the entire product. Scaling was manual. Production windows had become routine. The team needed a platform that could support the product already built.
Approach
Foundations first: landing zone, observability and a security baseline. Then Amazon EKS with GitOps, CI/CD, and a cutover plan operations could rehearse.
- Landing zone before liftAccounts, IAM, logging and network paths designed for a regulated workload, not copied from a non-production account.
- Incremental extraction onto EKSServices extracted behind a delivery path the team could run daily, rather than a single rewrite that would not complete.
- GitOps and promotion gatesWhat reached production had been built, scanned and promoted. Individual intervention was removed from the path to live.
- Rehearsed cutoverDNS, data path and rollback were practiced. Maintenance windows ceased to be a standing capacity plan.
Result
The platform team could deploy twenty times a day. Cutover did not take the product offline. Cloudhew left a system the internal team operated.
Contact us
Speak with a Cloudhew architect about cost, security, migration or platform work.
Request a consultation →