Zhivko Todorov
ALL CASE STUDIES

CASE 34 · YARROW · 2025

MULTI-REGIONTERRAFORMPLAYBOOKGLOBAL ACCELERATOR

A region-expansion playbook that runs in four weeks, not four months.

A consumer marketplace expanded from US-East to four additional regions over eighteen months. The first expansion took four months. We worked on the second and wrote a playbook; the third and fourth took four weeks each, with the same engineering team.

INDUSTRY

Consumer marketplace

DOMAIN

LANDING ZONE

DELIVERED

2025

STACK

TERRAFORM·GLOBAL ACCELERATOR·AURORA GLOBAL·CLOUDFRONT·ROUTE 53 GEO-DNS·CODEPIPELINE

RESULTS

What changed, by the numbers.

TIME PER REGION

4w

WAS 4 MONTHS

MANUAL STEPS

11

WAS 87

POST-LAUNCH BUGS

−81%

PER REGION

PLAYBOOK PAGES

14

INCL. CHECKLIST

HOW IT WENT

The first regional expansion had been mostly artisanal — every Terraform module touched, every IAM policy duplicated, every DNS record manually added. The team that did it remembered it as a hard four months. Nothing had been written down.

We worked the second expansion as a paired engagement: their senior engineer ran it, we sat alongside writing down every decision and every gotcha. Modules were generalised, conditional regional features documented, Aurora Global cutover scripted, Route 53 geo-DNS policies templated.

The third region was run from the playbook by a different engineer entirely. Four weeks, eleven manual steps (down from 87), three post-launch bugs (down from a typical sixteen). The fourth was even smoother. The team now considers a fifth a low-risk project.

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 →