Project · Multi-Cloud CIDR Allocation Plan

Plan a non-overlapping CIDR range for 4 clouds (AWS, GCP, Azure, DigitalOcean) across 3 environments (dev, staging, prod). Document the allocation in a CIDR table that survives 10x growth and supports cross-cloud peering.

• A markdown table with 12 rows (4 clouds × 3 envs), each row showing cloud, env, parent CIDR, and per-AZ subnet carve-outs.
• A short README section explaining the /N choice for parent ranges and why it leaves headroom for 10x scale.
• A second table listing the reserved ranges per cloud (e.g. AWS 169.254.169.254 metadata, GCP 169.254.169.254, Azure 168.63.129.16) that your plan must not collide with.
• A peering compatibility check: prove no two parent CIDRs overlap by showing the network and broadcast addresses of each.
• One IaC snippet (Terraform or cloud CLI) that creates one VPC/VNet from your plan as a sanity check.

• Zero CIDR overlaps across all 12 rows — verifiable by sorting on network address.
• Each parent range has at least 4x current address need and supports at least 3 AZs of /24 subnets.
• Reserved cloud-internal IPs are documented and avoided.
• Plan accommodates one VPC peering and one Transit Gateway / Cloud Interconnect attachment without renumbering.
• IaC snippet is runnable (passes `terraform plan` or equivalent CLI dry-run) against one cloud.