Setting up a new VPC, which CIDR
Today's CIDR choice hits you years later when peering or VPNs come in. Plan address space.
Try this first
- 1Avoid 10.0.0.0/16 as default, it collides with everything
- 2Pick a unique 10.x.x.x/16 block per VPC
- 3Leave room to grow, /16 is plenty, /20 can pinch
- 4Document which subnet does what (public, private, db)
When to bring us in
For multi-cloud or on-prem links, plan IP allocation centrally in a sheet or IPAM.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.