✅ Policy Check: All VPCs in the 10 CIDR block #66
Description
All VPCs in the 10 CIDR block
Status: ✅ PASS
Policy File: vpc-cidr.md
Workspace: View in System Initiative
Date: 2025-10-21T16:47:07.764Z
Full Report: 📄 View in Artifacts
All VPCs in the 10 CIDR block
Date: 2025-10-21T16:47:06Z
Policy
All the VPCs must be in the 10 CIDR block, and not have overlapping addresses.
Exceptions
The default VPC (sandbox) is allowed to be the 172.31 CIDR block.
Tags
- networking
Test Results
Result: Pass
All VPCs comply with the policy requirements. The sandbox-default-vpc uses the 172.31.0.0/16 CIDR block which is allowed under the policy exception for the default VPC. The tonys-chips-sandbox-vpc-vpc uses 10.1.0.0/16 which is within the required 10.0.0.0/8 CIDR block. No overlapping addresses were detected between the VPCs.
Source Data
System Initiative
all-vpc
| component | CIDR Block | Actual CIDR Block | VPC Name | VPC ID |
|---|---|---|---|---|
| AWS::EC2::VPC sandbox-default-vpc | 172.31.0.0/16 | sandbox-default-vpc | vpc-03d8021c04dbaedb3 | |
| AWS::EC2::VPC tonys-chips-sandbox-vpc-vpc | tonys-chips-sandbox-vpc-vpc | vpc-0bc7327e9bc2204c2 |
Column Selection Reasoning: The CIDR block attributes are essential for evaluating whether VPCs are in the correct IP range (10.x.x.x) and for detecting overlapping addresses. The VPC name is needed to identify whether a VPC qualifies for the default VPC exception (sandbox). The resource ID provides AWS-level identification for the VPC. Both domain and resource payload CIDR blocks are included since they represent the configured and actual CIDR values respectively.
About this issue
This issue was automatically generated by the policy checker workflow. When the workflow runs again for this policy, this issue will be closed and a new one will be created with updated results.