Modern Enterprise Network Architecture in AWS Cloud
summary
Describes migrating a large AWS estate (40+ accounts and many VPC peering links) into a central AWS Transit Gateway and a separate networking account to eliminate peering sprawl and simplify routing. Implements network and host configuration as code with Terraform in a dedicated git repo (AMIs, bastions, network config), enforces AMI/image baselines and IAM roles, adds logging and scanning for audits, and preserves S3/Direct Connect and VPN flows to reduce manual changes and ease debugging, compliance, and deployments.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:26Excess accounts issues
- 5:18Multi-account challenges
- 8:15Compliance isolation
- 10:17Account structuring
- 12:04Networking benefits
- 14:55Network control
- 17:24Account requirements
- 20:19Security groups vs ACLs
- 23:52Bastion hosts
- 25:58VPC peering fixes
- 27:24Transit networks
- 29:33Migration success
- 31:47Environment separation
- 33:38Office connectivity
- 36:25Troubleshooting logs
- 37:55Docs and config management
- 39:19Automation errors
- 40:47DevOps infrastructure
- 41:34Q&A
related talks
32mCreate a cloud-ready environment
29mLeading an Enterprise to the Public Cloud
51mBuilding a multi-account, multi-runtime service-oriented architecture
47mNetwork operations management and governance
01h 03mContinuous Security in the Cloud
55mBest practices
25mNetDevOps: Applying lessons of DevOps to networking
17mAdvance securely: Safely migrating to