Zhivko Todorov
ALL CASE STUDIES

CASE 112 · VINTAGE · 2025

AMAZON LINUX 2023GRAVITONEC2COMPUTE

Compute that runs the same workload for thirty percent less.

A consumer publishing platform ran their entire fleet on Amazon Linux 2 with x86 instances, despite roughly two-thirds of the workloads being ARM-compatible. We migrated to Amazon Linux 2023 on Graviton-based instances, one workload class at a time.

INDUSTRY

Consumer publishing

DOMAIN

COST

DELIVERED

2025

STACK

AMAZON LINUX 2023·GRAVITON (m7g, c7g, r7g)·ECS FARGATE·EC2·TERRAFORM·BENCHMARK SUITE

RESULTS

What changed, by the numbers.

COMPUTE BILL

−31%

ON MIGRATED FLEET

WORKLOADS MIGRATED

64%

OF FLEET

PERFORMANCE DELTA

+3%

MEDIAN, ON GRAVITON

AL2 EOL EXPOSURE

ELIMINATED

PROACTIVE

HOW IT WENT

AL2 was sliding toward end-of-life and the team had been deferring the migration because "ARM is a separate problem." We rolled them together. AL2023 itself is a relatively clean migration; the ARM transition needed careful workload classification.

Each workload class got benchmarked on Graviton in a staging environment with production-shape traffic. About two-thirds passed cleanly — same or better performance, same or better latency, sometimes a configuration tweak. The third that didn’t (older Java workloads with native bindings, some Rust workloads with x86-specific intrinsics) stayed on x86 with AL2023.

On the migrated 64% of the fleet the compute bill dropped 31%. Performance came out slightly ahead at the median. The AL2 end-of-life exposure is gone proactively rather than reactively. The team plans to revisit the held-back workloads in six months as ARM ports of their dependencies mature.

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.

Or email directly →