Network segmentation and subnetting

5 minutes 5 Questions

Network segmentation and subnetting are fundamental concepts for designing secure, scalable, and well-organized AWS architectures. These techniques help partition networks into smaller, manageable segments to enhance security, improve performance, and simplify administration. In AWS, Virtual Private Clouds (VPCs) serve as the foundation for network segmentation. A VPC allows you to create an isolated virtual network where you can launch AWS resources. Within a VPC, subnetting divides the IP address space into smaller networks called subnets. Subnets in AWS are associated with specific Availability Zones and can be classified as public or private. Public subnets have routes to an Internet Gateway, enabling resources to communicate with the internet. Private subnets lack such routes, keeping resources isolated from external access while still allowing outbound connectivity through NAT Gateways when needed. For organizational complexity, consider implementing a multi-tier architecture. Web servers reside in public subnets, application servers in private subnets, and databases in separate private subnets. This separation limits the blast radius of potential security incidents and enforces the principle of least privilege. Network Access Control Lists (NACLs) and Security Groups provide additional segmentation controls. NACLs operate at the subnet level as stateless firewalls, while Security Groups act as stateful firewalls at the instance level. Combining these allows granular traffic control between segments. CIDR block planning is crucial for effective subnetting. Organizations should allocate IP ranges that accommodate future growth while avoiding overlaps with on-premises networks or other VPCs. AWS recommends using non-overlapping CIDR blocks when establishing VPC peering or Transit Gateway connections. For enterprise environments, AWS Transit Gateway centralizes connectivity between multiple VPCs and on-premises networks, simplifying network management at scale. Combined with route tables and proper subnet design, organizations can implement hub-and-spoke or mesh topologies that align with their security and operational requirements.

Network Segmentation and Subnetting for AWS Solutions Architect Professional

Why Network Segmentation and Subnetting is Important

Network segmentation and subnetting are foundational concepts for designing secure, scalable, and efficient AWS architectures. They enable organizations to:

• Enhance Security: Isolate workloads and limit the blast radius of potential security breaches
• Improve Performance: Reduce network congestion by containing broadcast traffic within smaller network segments
• Meet Compliance Requirements: Separate sensitive data and systems to satisfy regulatory requirements like PCI-DSS, HIPAA, and SOC2
• Enable Multi-Account Strategies: Support complex organizational structures with proper network isolation

What is Network Segmentation and Subnetting?

Network Segmentation is the practice of dividing a network into smaller, isolated segments to control traffic flow and improve security posture.

Subnetting is the technical process of dividing an IP address space into smaller logical subdivisions called subnets.

In AWS context, this involves:
• VPCs (Virtual Private Clouds): Logically isolated networks within AWS
• Subnets: IP address ranges within a VPC, tied to specific Availability Zones
• Public Subnets: Subnets with routes to an Internet Gateway
• Private Subnets: Subnets with no route to the Internet Gateway
• Route Tables: Control traffic routing between subnets and external networks
• NACLs: Stateless network access control at the subnet level
• Security Groups: Stateful firewalls at the instance level

How Network Segmentation Works in AWS

1. VPC Design Patterns:
• Single VPC: Simple applications with minimal isolation requirements
• Multi-VPC: Separate VPCs for different environments (dev, staging, prod)
• Hub-and-Spoke: Central shared services VPC connected to multiple spoke VPCs via Transit Gateway

2. Subnet Architecture:
• Distribute subnets across multiple Availability Zones for high availability
• Use CIDR blocks appropriately (e.g., /16 for VPC, /24 for subnets)
• Plan for growth by reserving IP address space

3. Traffic Control Mechanisms:
• Transit Gateway: Centralized hub for connecting multiple VPCs and on-premises networks
• VPC Peering: Point-to-point connections between VPCs
• PrivateLink: Private connectivity to AWS services and third-party applications
• AWS Network Firewall: Managed firewall service for VPC protection

4. Multi-Account Segmentation:
• Use AWS Organizations to manage multiple accounts
• Implement AWS RAM (Resource Access Manager) to share subnets across accounts
• Deploy centralized networking accounts for Transit Gateway and shared VPCs

Key AWS Services for Network Segmentation:
• AWS Transit Gateway
• AWS PrivateLink
• VPC Endpoints (Gateway and Interface)
• AWS Network Firewall
• AWS Firewall Manager
• Route 53 Resolver

Exam Tips: Answering Questions on Network Segmentation and Subnetting

1. Recognize Scenario Patterns:
• Questions mentioning compliance or regulatory requirements often require network isolation
• Multi-account scenarios typically involve Transit Gateway or VPC sharing
• Hybrid connectivity questions involve VPN, Direct Connect, or Transit Gateway

2. Remember Key Principles:
• Public subnets need an Internet Gateway route; private subnets use NAT Gateway for outbound internet
• NACLs are stateless (require explicit inbound AND outbound rules)
• Security Groups are stateful (return traffic is allowed by default)
• Transit Gateway enables transitive routing; VPC Peering does not

3. CIDR Block Considerations:
• VPC CIDR blocks cannot overlap when peering
• Plan for sufficient IP addresses, especially in container and serverless environments
• Secondary CIDR blocks can extend VPC address space

4. Cost and Complexity Trade-offs:
• Transit Gateway has hourly charges plus data processing fees
• VPC Peering has no hourly charge, only data transfer costs
• PrivateLink is preferred for service-to-service communication across accounts

5. Common Question Themes:
• Isolating sensitive workloads from general traffic
• Enabling communication between VPCs in different accounts or regions
• Implementing least-privilege network access
• Centralizing egress traffic inspection
• Connecting on-premises data centers to multiple VPCs

6. Best Practices to Remember:
• Use separate subnets for different tiers (web, application, database)
• Implement defense in depth with multiple layers of security controls
• Centralize VPC flow logs for monitoring and troubleshooting
• Use AWS Firewall Manager for consistent security policies across accounts

7. Watch for Distractors:
• Solutions that suggest overlapping CIDR ranges for peered VPCs are incorrect
• Answers proposing public subnets for database tiers violate security best practices
• Options that overcomplicate simple scenarios may not be optimal
Test mode:
More Network segmentation and subnetting questions
30 questions (total)

Other Design Solutions for Organizational Complexity concepts

Account structure for organizational requirementsAmazon InspectorAmazon S3 Storage LensAmazon VPC networking conceptsAutomatic failure recovery architecturesAWS Backup serviceAWS BudgetsAWS Certificate Manager (ACM)AWS CloudTrailAWS Compute OptimizerAWS container networking servicesAWS Control TowerAWS Cost ExplorerAWS Direct ConnectAWS Elastic Disaster RecoveryAWS Global InfrastructureAWS IAM Identity CenterAWS Key Management Service (KMS)AWS Network FirewallAWS OrganizationsAWS Pricing CalculatorAWS PrivateLinkAWS Region and Availability Zone selectionAWS Resource Access Manager (RAM)AWS Savings PlansAWS Security HubAWS Site-to-Site VPNAWS Transit GatewayAWS Trusted AdvisorCentralized logging strategiesCentralized security event notificationsCertificate management best practicesCo-location connectivityConnectivity among multiple VPCsCost allocation tagging strategiesCross-account access managementCross-account resource sharingData backup strategiesDesigning DR solutions for RTO/RPO requirementsEffective backup and restoration strategiesEncryption strategies for data at restEncryption strategies for data in transitEvaluating VPC connectivity optionsHybrid DNS with Route 53 ResolverIAM Access AnalyzerIAM policies and permissionsIAM users, groups, and rolesIP addressing and CIDR blocksKMS key policies and grantsLanding zone designMonitoring cost and usageMulti-account event notificationsMulti-account governance modelsMulti-site disaster recoveryNetwork ACLsNetwork latency requirementsNetwork traffic monitoringOn-premises DNS integrationOn-premises to cloud integrationPilot light disaster recoveryPurchasing options impact on cost and performanceRecovery Point Objectives (RPO)Recovery Time Objectives (RTO)Reserved InstancesRoute tables for securityScale-up vs scale-out architecturesSecurity auditing strategiesSecurity groupsService Control Policies (SCPs)Spot InstancesThird-party identity provider integrationTransitive routing in AWSTroubleshooting traffic flowsVPC endpoints for service integrationsVPC Flow LogsVPC peering connectionsWarm standby disaster recovery