Zhivko Todorov
ALL CASE STUDIES

CASE 01 · ACME · 2026

CONTROL TOWERSOC 2MULTI-REGIONAURORA

Cut the AWS bill in half, kept the SLA.

A Series-B fintech on a single AWS account, growing 30% MoM, with auditors three weeks out. We rebuilt the landing zone on Control Tower and shipped the SOC 2 Type II remediation work in nine weeks — without a single migration weekend.

INDUSTRY

Series-B fintech

DOMAIN

LANDING ZONE

DELIVERED

2026

STACK

CONTROL TOWER·AURORA POSTGRES·ECS FARGATE·EVENTBRIDGE·CLOUDFRONT·KMS·CLOUDTRAIL·CONFIG·GUARDDUTY

RESULTS

What changed, by the numbers.

AWS BILL

−44%

$61K → $34K / MONTH

RTO

18m

FROM 4 HOURS

p99 LATENCY

80ms

API-EDGE, US-EAST-1

AUDIT FINDINGS

0

DOWN FROM 23

HOW IT WENT

The original account had eight production workloads, three dev environments, a shared services VPC, and a single root user nobody wanted to touch. We started with a written portfolio assessment: every workload mapped to a 6R disposition, every IAM principal inventoried, every NAT gateway costed out.

Week three we provisioned Control Tower with six accounts — prod, non-prod, security, audit, log archive, shared services — and stood up SSO with permission sets that mirrored the existing engineering team structure. Foundation services (DNS, IAM, CloudTrail, Config, GuardDuty) landed before any workload moved.

Then we migrated in three waves, four workloads each. Pilot-light for the data plane, blue/green for the stateless services, dual-write for the queue. The bill dropped 44% on right-sizing alone; Savings Plans took us the rest of the way. Auditors got their evidence in week eight.

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 →