What's the difference between public and private subnet
Public subnet has a route to the internet gateway, private doesn't. Decide per resource where it belongs.
Try this first
- 1Public: load balancer, NAT gateway, bastion (if you still use one)
- 2Private: app servers, databases, anything without direct internet need
- 3Outbound from private goes via NAT gateway in the public subnet
- 4Multi-AZ: at least 2 subnets per type, one per AZ
When to bring us in
Want to skip NAT cost, use VPC endpoints (gateway for S3/DynamoDB, interface for other services).
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.