Decommissioning the Landing Zone Accelerator and Control Tower, Twelve Days Later
Taking a full LZA and Control Tower deployment back out again: why the order is forced, the CloudFormation deadlock nobody documents, and what the sweep costs.
24 posts tagged "AWS".
Every published article carrying this tag.
Taking a full LZA and Control Tower deployment back out again: why the order is forced, the CloudFormation deadlock nobody documents, and what the sweep costs.
Wiring AWS Labs' lza-mcp-server into the container deployment from Part 2, then pointing its diagnosis tool at a real failure to see whether it finds the issue.
The deployment report. A Control Tower landing zone I had to build by hand because the account failed the prerequisites, fourteen failed SSM automation runs, and the guardrail that LZA created, attached to itself, and then got locked out.
Before standing up a fresh AWS Landing Zone Accelerator v1.16.2 environment on the ECS container pipeline instead of CodePipeline, I spent a morning on the release notes, the container/ folder in the repo, and the lza-universal-configuration v1.3.1 release. Here is what that research turned up.
How I moved manuel-vogel.de to vogel-johnson.com: Next.js on Amplify SSR, a CDK-built lead pipeline with DynamoDB and SES, and a 301 cutover that didn't break my SEO.
The nuke config you need so a sandbox reset does not wipe your LZA baseline
A templating CLI for LZA config files - what I discovered along the way
Which landing zone solution fits your needs? A practical comparison of two approaches
A step-by-step walkthrough of how to switch the config repository from CodeCommit to S3