go-to-k/cdk-multi-region-stack — explained in plain English
Analysis updated 2026-05-18
Put an ACM certificate for CloudFront in us-east-1 while your main app lives in another region, without splitting stacks by hand.
Add a CloudWatch alarm on CloudFront metrics that references resources back in your main stack.
Migrate existing hand-split multi-region CDK stacks into a single logical stack without recreating deployed resources.
| go-to-k/cdk-multi-region-stack | andersondanieln/hexllama | antonlobanovskiy/agent-tmux-web | |
|---|---|---|---|
| Stars | 13 | 13 | 13 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | easy | moderate |
| Complexity | — | 2/5 | 3/5 |
| Audience | ops devops | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing AWS CDK app and account access across multiple regions.
cdk-multi-region-stack is a small helper library for AWS CDK, the toolkit developers use to define cloud infrastructure as code. It solves a specific annoyance: some AWS setups need resources spread across two regions, but CDK normally forces you to write those as separate stacks and stitch them together by hand. The classic example is a CloudFront distribution. If you want a website served through CloudFront with a custom domain, the SSL certificate for that domain must live in the us-east-1 region no matter where your main application lives. Developers often deal with this by splitting their code into multiple stacks and manually wiring references between them. This library lets you write it as one logical stack instead. With MultiRegionStack, you call stack.regionScope('us-east-1') to get a scope for resources that need to live in that other region, while everything else stays in your main stack's region. Behind the scenes, CDK still creates one CloudFormation stack per region when it builds your infrastructure, but they share the same stack name and CDK automatically figures out the deploy order and handles passing values between them. The library also supports a case called groups, for resources that need to live in another region but also reference something back in your main stack, such as a CloudWatch alarm that watches a CloudFront metric. Putting these in the same twin stack as the certificate would create a circular reference, so the library lets you place them in a separate group stack instead, and figures out the correct deploy order automatically. There is also a migration path for teams that already run hand split stacks across regions, letting them adopt this library without recreating already deployed resources. This is a focused infrastructure tool for AWS CDK users managing multi region deployments, not a general purpose framework.
A small AWS CDK library that lets you place some resources in a different AWS region while writing them as one logical stack, instead of manually splitting your infrastructure code into separate stacks.
Mainly TypeScript. The stack also includes TypeScript, AWS CDK, AWS CloudFormation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.