Network Configuration
Basic Usage
Network Configuration Interface
Configuration Options
Maximum Availability Zones
Control how many AZs your VPC spans:NAT Gateways
Configure NAT gateway deployment for private subnet internet access:VPC Flow Logs
Enable VPC flow logs for network traffic monitoring:VPC Endpoints
Reduce NAT gateway costs by using VPC endpoints for AWS services:Advanced VPC Usage
For more control, create VPC directly:VpcFactory (Alternative)
Rarely used alternative for VPC creation:HostedZoneFactory
Import existing Route 53 hosted zones for domain configuration:Cost Optimization Strategies
Eliminate NAT Gateways
If your application only needs AWS service access:Single NAT Gateway
For non-critical workloads, use one NAT gateway instead of one per AZ:Gateway Endpoints Only
For S3 and DynamoDB workloads:Common Patterns
Development Environment
Minimal cost configuration:Production Environment
High availability with cost optimization:Serverless Optimized
No NAT gateways, VPC endpoints only:Access VPC from App
Get the default VPC for use in other constructs:Best Practices
- Start with no NAT gateways: Add them only if external internet access is needed
- Use gateway endpoints: Always enable S3 and DynamoDB gateway endpoints (free)
- Interface endpoints for AWS services: Use interface endpoints instead of NAT gateways for AWS service access
- Multi-AZ for production: Use
maxAzs: 3with multiple NAT gateways for production high availability - Flow logs for security: Enable flow logs in production for security monitoring
See Also
- Compute Factory - Deploy compute resources in VPC
- Database Factory - Deploy databases in VPC