CASE 18 · AURUM · 2025
Azure to AWS, twenty-two services, no rewrite.
A healthcare ISV with twenty-two production services on Azure (AKS, Azure SQL, App Configuration, Service Bus) needed to leave Azure inside seven months — driven by their largest customer’s "AWS-only" mandate. We migrated everything to equivalent AWS services without rewriting application code.
Healthcare ISV
MIGRATION
2025
RESULTS
What changed, by the numbers.
TIMELINE
6m
CODE REWRITES
0
RUN-RATE COST
−22%
CUTOVER DOWNTIME
< 45m
HOW IT WENT
The team had built thin SDK wrappers around every Azure dependency three years earlier, "because we might switch clouds someday." Someday arrived. The wrappers paid off — most services needed only a configuration swap and a new credential.
AKS workloads moved to EKS with the same Helm charts. Azure SQL went to Aurora Postgres via DMS with a five-week shadow run. Service Bus mapped to SQS plus EventBridge for the topic-style flows. Azure App Configuration mapped to AWS AppConfig.
The largest customer’s deadline was hit with two weeks of slack. Run-rate cost on AWS came in 22% lower after right-sizing, partly because Reserved Instance equivalents (Savings Plans) priced better than the original Azure Hybrid Benefit. The team kept the abstraction layer.
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.