AWS VPC and subnet configuration is confusing and restrictive

5/10 Medium

AWS VPC networking topology is confusing, with non-intuitive constraints like subnets being restricted to single availability zones ('one subnet equals one availability zone'). This creates gotchas when designing multi-AZ deployments.

AWS VPCAWS
Category
config
Workaround
partial
Stage
build
Freshness
persistent
Scope
single_lib
Upstream
open
Recurring
Yes
Buyer Type
team
Maintainer
slow

Sources

Collection History

Query: “What are the most common pain points with Azure for developers in 2025?”4/7/2026

subnets within your Vnet are restricted to one availability zone rather than spanning multiple availability zones. As such, you'll have to configure your systems in such a way to ensure you don't run into a scenario where one subnet needs to be talking to another in a different availability zone.

Query: “What are the most common pain points with AWS for developers in 2025?”3/29/2026

You can't have one subnet across multiple availability zones. You'll probably hear something along the lines of 'one subnet equals one availability zone.'

Created: 3/29/2026Updated: 4/7/2026