An architecture review of a multi-account municipal landing zone fi…

Question

An architecture review of a multi-account municipal landing zone finds possible hidden single points of failure: one NAT Gateway in a shared services VPC, one bastion, and a single-Region authoritative DNS pattern for critical apps. Which action best improves reliability evaluation?

Accepted Answer

Systematically inventory and remediate hidden SPOFs—multi-AZ NAT, redundant admin access paths, and DNS/DR patterns aligned to app RTO—rather than assuming landing-zone defaults are enough — Landing zones can still hide one lonely NAT or bastion acting like a drawbridge. Hunt those SPOFs on purpose and fix them—Control Tower paperwork is not a spare NAT Gateway.

Answer

Document the SPOFs as acceptable because Control Tower was used at account vending time

Answer

Consolidate all workloads into one AZ to make failure domains easier to reason about

Answer

Replace Route 53 with a hosts file distributed by email during incidents

An architecture review of a multi-account municipal landing zone finds possible hidden single points of failure: one NAT Gateway in a shared services VPC, one bastion, and a single-Region authoritative DNS pattern for critical apps. Which action best improves reliability evaluation?

Short Explanation

Full Explanation