During VPC design for a growing municipality, the network team prop…

Question

During VPC design for a growing municipality, the network team proposes /28 subnets for every application tier to “save” addresses. What IP planning guidance should the solutions architect give for future scale?

Accepted Answer

Choose CIDR blocks large enough for projected growth of instances, load balancers, and managed ENIs—avoid tiny subnets that exhaust addresses and block scale — Tiny /28 pockets fill up the week before go-live when load balancers and managed ENIs each take a bite. Plan room to grow—re-IP mid-project is the expensive kind of civic construction.

Answer

Always use /28 everywhere because AWS cannot support larger subnets

Answer

Ignore IP planning because Elastic IPs remove all private address constraints

Answer

Overlap the same 10.0.0.0/16 in every VPC so peering never needs thought

During VPC design for a growing municipality, the network team proposes /28 subnets for every application tier to “save” addresses. What IP planning guidance should the solutions architect give for future scale?

Short Explanation

Full Explanation