CASE 109 · BIRCH · 2024
A Singapore region, opened in eight weeks.
A B2B SaaS company expanding into APAC had two enterprise customers conditioning their renewal on Singapore data residency. The team had never operated outside us-east-1 and us-west-2. We built the ap-southeast-1 deployment, retrofitted the application for region-aware routing, and certified it in time for the renewal.
B2B SaaS
SECURITY
2024
RESULTS
What changed, by the numbers.
TIME TO REGION
8w
RESIDENCY ENFORCEMENT
SCP-LOCKED
RENEWALS CLOSED
$1.8M
CODE CHANGES
< 2%
HOW IT WENT
The team had abstracted region in some places and hard-coded it in others, in proportions nobody had measured. The first audit pass surfaced 28 region-pinned references; we triaged them into "needs to be region-aware" and "always us-east-1 for org-shared services."
Singapore came up as a new account in the existing org. Control Tower managed the baseline. Aurora moved to a regional cluster; KMS used Singapore-resident keys; EKS ran a regional cluster on the same Helm charts as production. SCPs at the OU level enforced "no calls to non-APAC regions" for Singapore-tenant accounts.
Production traffic switched on in week eight. The two enterprise customers signed their renewals; $1.8M unblocked. Code changes were under 2% of the codebase. The Singapore region is now the template for future regional expansion — Sydney is next.
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.