Engineer the Cloud.
Understand Every Network Path.
Explore enterprise AWS networking through interactive architecture, routing decisions, hybrid connectivity, cloud security and production troubleshooting.
Investigate VPCs, subnets, route tables, Transit Gateway, Cloud WAN, Direct Connect, PrivateLink, Network Firewall, load balancing and multi-account security.
Understand the Architecture Behind AWS Connectivity
AWS networking is more than deploying a VPC. Enterprise architectures combine routing domains, connectivity services, security controls, private service access and operational telemetry.
Network Reachability
VPC CIDRs, subnet routing, gateways, attachments and network paths determine which destinations are reachable.
Enterprise Transit
Transit Gateway and Cloud WAN connect distributed environments through managed routing constructs.
Policy Enforcement
Security groups, network ACLs, firewalls and identity controls restrict permitted communication.
Network Evidence
Flow Logs, route inspection, Reachability Analyzer and telemetry support troubleshooting.
Inside an AWS Enterprise Network
Explore six architecture layers and select individual network components to inspect their responsibilities, dependencies and engineering considerations.
Trace Traffic Through the AWS Network
Select an enterprise traffic scenario, change the relevant conditions and investigate how routing and security decisions affect the conceptual path.
Engineering Scenario Controls
Traffic Investigation Result
PATH AVAILABLEFive Stages of Enterprise AWS Networking
Progress from foundational VPC architecture to enterprise connectivity, cloud security, advanced networking and production operations.
Network Foundations
- VPC architecture
- Subnets and route tables
- Security groups and NACLs
Enterprise Connectivity
- VPC peering
- Transit Gateway
- Direct Connect
Cloud Security
- Network Firewall
- PrivateLink
- Multi-account security
Advanced Networking
- Cloud WAN
- Route 53
- Load balancing
Production Engineering
- Network observability
- Failure investigation
- Enterprise capstone
Your Enterprise AWS Engineering Journey
Each lab will provide a dedicated interactive engineering environment with architecture exploration, configurable scenarios, technical explanations and investigations.
From Cloud Architecture to Engineering Mastery
Explore the architecture above, investigate traffic paths and prepare for the 15-lab AWS networking curriculum.
AWS Cloud Networking & Security Engineering
Your complete interactive AWS engineering learning environment. Explore 15 hands-on labs across five progressive stages, from VPC fundamentals to enterprise networking, security, observability and production troubleshooting.
Progress Through the AWS Engineering Curriculum
Each stage contains three engineering labs. Stage completion is calculated automatically from the completion status of its three labs.
All 15 AWS Engineering Labs
Search, filter, open and manage completion for every lab. Progress is shared with the individual lab widgets and all five stage completion trackers.
No labs match the current filters.
Your 15-Lab Completion Overview
Each numbered tile represents a lab. Select a tile to navigate directly to that activity. Green indicates self-reported completion.
Enterprise AWS Networking & Security Capstone
Bring together all five learning stages in the final enterprise architecture challenge. Validate routing, global connectivity, hybrid integration, security inspection, private services and application delivery.
AWS VPC Architecture Explorer
Design a foundational AWS Virtual Private Cloud, examine subnet placement across Availability Zones, inspect route tables, investigate connectivity and diagnose common VPC configuration failures.
Inside a Multi-AZ Virtual Private Cloud
Select a network component to examine its role in an AWS VPC. This topology is a simplified teaching model; real deployments use subnet-specific routing, gateway placement and security controls.
Plan the AWS Network Address Space
VPC CIDR Planner
Choose a VPC address block and a subnet prefix. The planner calculates the maximum number of equal-size subnets and AWS-usable IPv4 addresses per subnet.
Route Table Inspector
Compare simplified public and private subnet route tables. The public subnet uses an Internet Gateway; the private subnet uses a NAT Gateway for outbound IPv4 internet access.
| Destination | Target | Purpose |
|---|
Trace the Packet. Diagnose the Failure.
Select a traffic flow and change the network conditions. The lab models the relevant routing and security dependencies, then produces a diagnostic trace.
Connectivity Test Controls
Engineering Diagnostic Trace
PATH AVAILABLEValidate Your VPC Architecture Understanding
Answer five technical questions covering AWS networking fundamentals. Your score is calculated locally and does not control lab completion.
Complete the AWS VPC Architecture Lab
When you have finished exploring the topology, CIDR planner, route tables and diagnostic scenarios, mark the lab complete. Completion is self-reported and synchronizes with the AWS Learning Dashboard in this browser.
Subnets, Route Tables & Internet Gateways
Build and investigate AWS subnet routing. Configure public and private subnet route tables, test longest-prefix-match decisions, explore Internet Gateway and NAT Gateway dependencies, and diagnose production-style connectivity failures.
Two Availability Zones. Multiple Routing Domains.
Inspect the Internet Gateway, public subnets, NAT Gateways, private application subnets and VPC route tables. Select any component to examine its role in the network.
Engineer the Route Tables
Edit a simplified route table for each subnet type. The mandatory VPC local route is preserved. Add static routes, change targets, remove custom entries and observe how the subnet classification changes.
Route Table Editor
| Destination | Target | Action |
|---|
Subnet Classification & Routing Analysis
Longest Prefix Match Explorer
Choose a source subnet and enter a destination IPv4 address. The engine checks the configured routes and selects the most-specific matching prefix, including the immutable VPC local route.
Route Lookup Controls
Matching Route Candidates
Inject Failures. Investigate Connectivity.
Test three traffic scenarios against the editable route tables. Change gateway health and security conditions to identify the first failing dependency in the simplified traffic path.
Traffic Scenario Controls
Connectivity Diagnostic Output
PATH AVAILABLETest Your AWS Routing Knowledge
Five questions covering subnet classification, longest prefix match, NAT Gateway design, route-table associations and AWS networking fundamentals.
Complete the AWS Routing Architecture Lab
When you have investigated the route tables, subnet classification, longest-prefix-match decisions and gateway failures, mark Lab 2 complete. This is self-reported and synchronizes with the existing AWS Learning Dashboard.
Security Groups vs Network ACLs
Understand how AWS evaluates security group and network ACL rules. Trace inbound and outbound packets, investigate stateful connection tracking, test stateless return-path rules, and diagnose security policy failures in a multi-tier VPC.
Two Security Layers. Different Evaluation Models.
Select a security component in the topology to examine how AWS security groups and network ACLs protect traffic between an internet client, a web workload and a private database.
Configure the Security Controls
Add and remove simplified IPv4 rules. Security groups use allow-only rules; network ACLs support ordered allow and deny rules. Both editors feed the packet-flow simulator.
Web Server Security Group
| Protocol | Port | Peer CIDR | Action |
|---|
Public Subnet Network ACL
| # | Port | CIDR | Effect |
|---|
Trace the Request and Return Path
Select an inbound HTTPS connection or outbound web request. The simulator evaluates the configured security rules, including the return packet's ephemeral destination port.
Traffic Test Configuration
Packet Evaluation Trace
CONNECTION ALLOWEDWhy Ephemeral Ports Matter
Security groups are stateful for tracked connections, but network ACLs independently evaluate request and response packets. Explore the packet tuples for the selected traffic scenario.
TCP Connection Tuple
Operational Design Notes
For an inbound HTTPS connection, the request reaches TCP destination port 443. The server response returns to the client's ephemeral port, which must be allowed by the outbound NACL.
For an outbound HTTPS connection, the request uses the server's ephemeral source port and remote destination port 443. The inbound NACL must allow the return traffic to that ephemeral port.
Validate Your AWS Security Knowledge
Five questions covering security group connection tracking, NACL rule ordering, default-deny behavior, subnet security and ephemeral TCP ports.
Complete the AWS Security Controls Lab
When you have explored the architecture, edited security policies, tested packet flows and investigated ephemeral-port failures, mark Lab 3 complete. Your progress synchronizes with the AWS Learning Dashboard.
Architecture & Foundations Completion Tracker
Track your progress through the first three AWS networking labs. Review the VPC architecture, investigate subnet routing, and validate your understanding of security groups and network ACLs.
AWS VPC Architecture Explorer
Explore VPC CIDRs, Availability Zones, subnets, routing domains and enterprise network architecture.
Subnets, Route Tables & Internet Gateways
Engineer subnet routes, inspect Internet Gateway and NAT dependencies, and investigate connectivity failures.
Security Groups vs Network ACLs
Compare stateful and stateless controls, configure security policies, and trace TCP return traffic.
AWS VPC Peering & Routing
Connect isolated AWS VPCs using VPC peering. Configure peering relationships, validate non-overlapping CIDR blocks, build bidirectional route tables, investigate connectivity failures and understand why VPC peering does not provide transitive routing.
Three VPCs. Three Routing Domains.
Inspect the application, shared-services and analytics VPCs. Select a component to understand its routing domain and how peering enables private IP connectivity between directly connected VPCs.
Create and Manage Peering Connections
Configure the three possible peering relationships. CIDR overlap validation is performed before a connection can become active. Peering activation does not automatically create the routes required for traffic forwarding.
Peering Connection Manager
VPC CIDR Configuration
Build the Peering Routes
Each VPC has its own route table. Add or remove peering routes and examine the impact on traffic. A successful connection requires a matching route in both directions and an active direct peering relationship.
VPC Route Table Editor
| Destination | Target | Action |
|---|
Routing Domain Analysis
Even when A peers with B and B peers with C, A cannot reach C through B using VPC peering. A direct A–C peering connection or another supported routing architecture is required.
This lab models one workload route table per VPC. Real VPCs may contain multiple subnets associated with different route tables.
Trace Inter-VPC Traffic
Choose a source and destination VPC. The diagnostic engine evaluates CIDR validity, direct peering, forward and return routes, and security permissions. Test the A → B → C transitive-routing misconception.
Traffic Investigation Controls
Routing and Connectivity Trace
PATH AVAILABLEValidate Your VPC Peering Knowledge
Five questions covering peering CIDR constraints, routing requirements, transitive routing, security controls and production network design.
Complete the AWS VPC Peering Lab
When you have explored the multi-VPC topology, configured peering connections, built bidirectional routes and investigated routing failures, mark Lab 4 complete. Progress is self-reported and shared with the AWS dashboard.
AWS Transit Gateway Architecture
Engineer a scalable hub-and-spoke AWS network using Transit Gateway attachments, route-table associations, propagation and segmentation. Investigate how the source attachment's associated route table determines forwarding, and why missing routes or blackhole entries disrupt connectivity.
One Transit Hub. Multiple Routing Domains.
Select the Transit Gateway or any VPC attachment to inspect its CIDR, association and role. The topology reflects attachment availability and highlights the difference between physical connectivity and routing permissions.
Configure VPC Attachments & Associations
Each attachment associates with exactly one Transit Gateway route table in this lab. The associated table is used to look up traffic entering the Transit Gateway from that attachment.
Attachment Manager
Propagation Manager
Inspect Static, Propagated & Blackhole Routes
Choose a TGW route table to inspect effective routes. Add static routes or blackholes to explore route selection and segmentation. A blackhole route discards matching traffic.
Transit Gateway Route Table
| Destination | Target | Type |
|---|
Routing Domain Segmentation
Application, Shared Services and Security VPCs can exchange traffic through their production-associated Transit Gateway route table, subject to effective routes and return-path configuration.
The Analytics VPC is associated with a separate TGW route table. Segmentation is controlled by the routes installed in each table, not simply by the names of the tables.
Configure the VPC-Side Routes
Transit Gateway routes alone are insufficient. The source and destination VPC subnet route tables must also direct traffic for remote networks toward the Transit Gateway. Toggle these modeled route dependencies to simulate asymmetric connectivity.
VPC Routing Controls
VPC Routing Matrix
| Source | Remote VPCs Routed via TGW |
|---|
Trace Traffic Through Transit Gateway
Run a bidirectional connectivity test. The diagnostic engine checks attachment availability, VPC-side routing, source route-table association, effective TGW forwarding, blackhole routes, destination attachment state and return-path symmetry.
Connectivity Test Controls
End-to-End Routing Trace
PATH AVAILABLEValidate Your Transit Gateway Knowledge
Five questions covering attachment associations, propagation, route selection, blackholes and VPC-side routing dependencies.
Complete the AWS Transit Gateway Lab
When you have inspected the hub-and-spoke topology, configured attachments, modified route-table associations and propagations, tested segmentation and investigated traffic failures, mark Lab 5 complete. Progress is self-reported and shared with the AWS dashboard.
AWS Direct Connect & Hybrid Networking
Build a resilient hybrid cloud architecture connecting enterprise data centres to AWS. Explore Direct Connect, Direct Connect Gateway, Transit Gateway, private and transit virtual interfaces, BGP route exchange, VPN backup, and production failure investigation.
From Enterprise Data Centre to AWS
Inspect each architecture component and the two transport paths. The Direct Connect path is modeled through a transit VIF and Direct Connect Gateway to a Transit Gateway. A separate private VIF model illustrates direct private connectivity to a VPC through a Virtual Private Gateway.
Configure Direct Connect & VPN Resilience
Enable or disable connectivity dependencies to investigate path selection and failover. The simulator treats BGP sessions, physical connectivity, VIF configuration and VPN tunnels as separate operational states.
Direct Connect Transport
Site-to-Site VPN Backup
Inspect Hybrid Route Selection
Compare candidate paths to an AWS workload prefix. In this educational model, a configurable policy preference selects Direct Connect or VPN when both routes are available. Actual AWS path selection also depends on gateway type, route specificity, BGP attributes and AWS-specific routing rules.
Hybrid Routing Policy
Candidate Route Table
| Transport | Next Hop | Preference | State |
|---|
Private VIF vs Transit VIF
Private VIF Architecture
A private VIF provides private connectivity to a VPC through a Virtual Private Gateway, either directly or through a Direct Connect Gateway where supported. It is not the same as a Transit Gateway attachment.
Transit VIF Architecture
A transit VIF connects through a Direct Connect Gateway to a Transit Gateway, enabling connectivity to supported networks attached to that TGW, subject to routing and association constraints.
Run a Hybrid Connectivity Trace
Investigate end-to-end traffic between the enterprise data centre and AWS. Inject faults, observe BGP path availability and identify the first failed forwarding dependency.
Investigation Controls
Connectivity Investigation Results
PATH AVAILABLEValidate Your Hybrid Networking Knowledge
Five questions covering Direct Connect, BGP, transit VIFs, hybrid resilience and security.
Complete the AWS Hybrid Networking Lab
When you have explored the Direct Connect architecture, compared virtual interfaces, inspected BGP route selection, tested VPN backup and investigated hybrid failures, mark Lab 6 complete. Progress is self-reported and shared with the AWS dashboard.
Enterprise Connectivity
Completion Tracker
You've explored AWS VPC peering, Transit Gateway architecture and hybrid cloud networking with Direct Connect. Track your engineering progress across all three Stage 2 labs before advancing to Cloud Security Architecture.
completed in Stage 2
Stage 2 Engineering Activities
Self-reported completion · No quiz gatingAWS VPC Peering & Routing
Explore VPC peering connections, route-table dependencies, non-transitive routing, overlapping CIDR restrictions and connectivity troubleshooting.
AWS Transit Gateway Architecture
Engineer a scalable hub-and-spoke architecture using VPC attachments, Transit Gateway route-table associations, propagation, segmentation and blackhole routes.
AWS Direct Connect & Hybrid Networking
Investigate enterprise hybrid connectivity using Direct Connect, virtual interfaces, Direct Connect Gateway, BGP route exchange, VPN backup and failure analysis.
Continue Your Enterprise Connectivity Journey
Complete Labs 4, 5 and 6 to finish Stage 2. Your progress updates automatically as you mark each lab complete.
NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 02
Return to Learning Dashboard ↑AWS Network Firewall & Centralized Inspection
Design, configure and troubleshoot centralized network inspection using AWS Network Firewall, Transit Gateway, dedicated inspection VPCs, stateful and stateless rules, firewall endpoints and symmetric traffic routing.
Centralized Inspection Through a Security VPC
Select a network component to inspect its function. The diagram represents east-west traffic between two application VPCs routed through a centralized inspection VPC containing AWS Network Firewall endpoints.
Control Inspection & Traffic Symmetry
Toggle key architectural dependencies. The model uses a simplified single-AZ inspection path; production designs should consider firewall endpoints per Availability Zone, route-table configuration, Transit Gateway appliance mode and AZ affinity.
Inspection Path Configuration
Firewall Policy Processing
Configure Stateless & Stateful Rules
Experiment with simplified firewall policy processing. Stateless rules use priority-based evaluation. Stateful rules model connection-aware allow, drop and alert actions for selected protocols and destination ports.
Stateless Rule Group
| Priority | Port | Action |
|---|
Stateful Rule Group
| Protocol | Port | Action |
|---|
Trace Traffic Through Centralized Inspection
Choose a traffic flow and run a packet inspection trace. The engine evaluates routing, firewall endpoint availability, stateless policy, stateful policy, application security and return-path symmetry.
Traffic Simulation Controls
Firewall Inspection Results
READY TO INSPECTValidate Your AWS Network Firewall Knowledge
Five questions covering centralized inspection, stateless rules, stateful policies, routing symmetry and firewall endpoints.
Complete the AWS Network Firewall Lab
When you have inspected the centralized security architecture, modified firewall rules, tested traffic flows and investigated routing failures, mark Lab 7 complete. Completion is self-reported and synchronized with the AWS learning dashboard.
AWS PrivateLink & VPC Endpoints
Engineer private connectivity to AWS services and privately published applications. Compare interface and gateway endpoints, explore PrivateLink endpoint services, inspect private DNS resolution and troubleshoot endpoint policies, security groups and network routing.
Private Service Access Without Public IP Exposure
Inspect the consumer VPC, interface endpoint, endpoint service, provider load balancer, gateway endpoint and AWS service. Select each node to learn how the connectivity components fit together.
Choose the Correct Endpoint Architecture
PrivateLink Interface Endpoint
Creates endpoint network interfaces with private IP addresses in selected subnets. Connects to supported AWS services or privately published endpoint services.
DNS + ENI + SECURITY GROUPSS3 / DynamoDB Gateway Endpoint
Uses VPC route-table entries targeting a gateway endpoint. Does not create endpoint ENIs or use security groups on the gateway endpoint.
ROUTE TABLE + ENDPOINT POLICYPrivate Service Publishing
A service provider publishes an endpoint service, commonly backed by a Network Load Balancer. Consumers establish interface endpoints after the required permissions and acceptance checks.
PROVIDER NLB + CONSUMER ENDPOINTConfigure Endpoint & DNS Dependencies
Toggle the components that determine private connectivity. The interface endpoint path, gateway endpoint path and privately published service path have different requirements.
Interface Endpoint & PrivateLink
Gateway Endpoint & Policies
Run a Private Endpoint Connectivity Trace
Choose an AWS service access scenario and inject a failure. The engine follows the relevant private connectivity model rather than treating every endpoint type as identical.
Traffic Simulation Controls
Private Connectivity Results
READY TO TRACEValidate Your AWS PrivateLink Knowledge
Five questions covering interface endpoints, gateway endpoints, DNS, endpoint services and authorization.
Complete the AWS PrivateLink & VPC Endpoints Lab
When you have compared endpoint types, explored the architecture, tested private DNS and investigated endpoint policy and routing failures, mark Lab 8 complete. Progress is self-reported and synchronized with the AWS dashboard.
AWS Zero Trust & Multi-Account Segmentation
Design enterprise security boundaries using AWS Organizations, separate AWS accounts, Transit Gateway route-table segmentation, workload security groups, identity-based authorization and least-privilege access. Investigate how network reachability and application authorization combine to protect sensitive AWS environments.
Multi-Account Isolation & Trust Boundaries
Select a component to inspect its role. This simplified architecture uses Production, Development, Shared Services and Security accounts connected through a central Transit Gateway.
Three Independent Security Decisions
Transit Gateway Segmentation
Transit Gateway route-table associations and propagations control which VPC attachments can route to other network domains.
ROUTING REACHABILITYSecurity Groups & Network ACLs
Workload-level security groups and subnet network ACLs enforce permitted traffic independently of the routing architecture.
PACKET FILTERINGIdentity & Application Authorization
IAM, resource policies and application-level authentication determine whether an identity can perform a protected operation.
LEAST-PRIVILEGE AUTHORIZATIONConfigure Network & Identity Controls
Toggle the independent dependencies that govern access to sensitive environments. The model illustrates how route-table segmentation, security groups and authorization combine.
Network Segmentation Controls
Workload & Identity Security Controls
Investigate an Enterprise Access Request
Choose a cross-account flow and inject a fault. The model evaluates forward and return routing, destination security controls, identity authorization and organization policy.
Security Investigation Controls
Security Decision Trace
READY TO EVALUATEValidate Your AWS Zero Trust Knowledge
Five questions covering multi-account boundaries, TGW segmentation, security groups, identity authorization and least privilege.
Complete the AWS Zero Trust & Multi-Account Lab
After exploring account trust boundaries, changing routing and security controls, and investigating access decisions, mark Lab 9 complete. Progress is self-reported and synchronized with the AWS dashboard.
Cloud Security Architecture Completion Tracker
Track your progress across three enterprise AWS security engineering labs. Explore centralized inspection, private service connectivity and Zero Trust segmentation, then mark each activity complete as you finish it.
AWS Network Firewall & Centralized Inspection
Inspect firewall endpoints, stateless and stateful rules, centralized security routing and symmetric inspection paths.
AWS PrivateLink & VPC Endpoints
Explore interface endpoints, gateway endpoints, private DNS, endpoint policies and private connectivity troubleshooting.
AWS Zero Trust & Multi-Account Segmentation
Investigate cross-account trust boundaries, Transit Gateway segmentation, workload security and identity authorization.
AWS Cloud WAN & Global Networks
Design and troubleshoot enterprise multi-region connectivity using AWS Cloud WAN core networks, regional core network edges, network segments, VPC attachments, centralized policy and controlled inter-segment routing.
AWS Cloud WAN Core Network & Regional Edges
Select a component to inspect its role. This conceptual design connects application VPCs across Europe, North America and Asia-Pacific through a centrally managed Cloud WAN core network.
Centralized Policy, Distributed Connectivity
Regional Core Network Edges
Cloud WAN provides a centrally managed global core network with regional core network edges where supported attachments connect.
REGIONAL CONNECTIVITYPolicy-Based Segmentation
Segments define routing domains. Segment actions and sharing policies determine permitted route exchange between otherwise isolated environments.
CONTROLLED ROUTE SHARINGAttachment Associations
Attachment policies can assign resources to network segments using supported attachment attributes, tags and policy rules.
CENTRALIZED GOVERNANCEConfigure Global Routing & Segmentation
Toggle core network availability, regional attachment status, route propagation and segment-sharing policy. Observe how these changes affect multi-region traffic reachability.
Regional Connectivity Controls
Routing & Segment Policy Controls
Trace Cross-Region Cloud WAN Traffic
Choose a traffic flow and inject a failure. The simulation checks regional edges, core connectivity, attachment associations, segment policy and return-path routing.
Global Routing Simulation
Cloud WAN Route Trace
READY TO TRACEValidate Your AWS Cloud WAN Knowledge
Five questions covering core networks, regional edges, segments, attachment policies and route sharing.
Complete the AWS Cloud WAN Lab
After exploring the multi-region core network, modifying segment policies and investigating global routing failures, mark Lab 10 complete. Progress is self-reported and synchronized with the AWS workspace dashboard.
Amazon Route 53 DNS & Traffic Engineering
Engineer DNS resolution, public and private hosted zones, Route 53 Resolver endpoints, hybrid forwarding, weighted traffic distribution, latency-based routing, failover and DNS health-check behavior in a production-style AWS architecture.
Public DNS, Private DNS & Hybrid Resolution
Select a component to inspect how DNS queries flow between clients, recursive resolvers, Route 53 authoritative hosted zones and private AWS VPC environments.
Route 53 Routing Policies
Weighted Routing
Distribute DNS answers between eligible records using configured relative weights. DNS caching means request-level traffic ratios are not guaranteed.
TRAFFIC DISTRIBUTIONLatency-Based Routing
Return records based on AWS latency measurements between users' resolver locations and AWS Regions, subject to routing configuration.
REGIONAL PERFORMANCEFailover Routing
Use primary and secondary records with health evaluation to influence authoritative DNS responses during service failures.
RESILIENCE & RECOVERYConfigure DNS Infrastructure & Health
Toggle public DNS, private DNS and hybrid forwarding dependencies, and change endpoint health to investigate how DNS resolution behaves.
DNS Infrastructure
Routing & Endpoint Health
Run the DNS Resolution & Routing Simulator
Choose a DNS query type and routing policy, then inject a fault. The simulator explains the resolution path and the resulting DNS response.
DNS Query Controls
DNS Resolution Trace
READY TO RESOLVEValidate Your DNS Engineering Knowledge
Five questions covering public DNS, private hosted zones, hybrid DNS, routing policies and health-based failover.
Complete the Route 53 & DNS Engineering Lab
After exploring DNS architecture, configuring routing and health controls, and investigating resolution failures, mark Lab 11 complete. Progress is self-reported and synchronized with the AWS workspace dashboard.
AWS Load Balancing & Application Delivery
Engineer highly available application delivery with Application Load Balancers, Network Load Balancers, listeners, target groups, TLS termination, multi-AZ target health, AWS WAF and traffic-routing policies. Diagnose application outages by tracing each layer of the request path.
Multi-AZ Load Balancing & Target Groups
Select an architecture component to inspect how incoming traffic passes through the load balancer, listener, routing policy and healthy application targets.
ALB, NLB & Application Security
Application Load Balancer
Supports HTTP/HTTPS routing using listener rules, hostnames, paths, headers and target groups. Can integrate with AWS WAF.
APPLICATION-AWARE ROUTINGNetwork Load Balancer
Handles TCP, UDP and TLS traffic using transport-level listeners and target groups. Supports static IP addressing per enabled Availability Zone.
TRANSPORT-LEVEL DELIVERYTarget Health & Multi-AZ
Health checks determine target eligibility. Distributing healthy targets across Availability Zones improves availability during failures.
HEALTH-AWARE TARGET SELECTIONConfigure Listener, Security & Target Health
Toggle the dependencies required for successful application delivery. The simulated request path updates when you change the configuration.
Listener & Security Controls
Target Group & Availability Controls
Trace a Load-Balanced Application Request
Choose a request scenario and inject a failure. The engine evaluates listener availability, TLS, WAF, target groups, security groups and application target health.
Application Traffic Simulation
Application Delivery Trace
READY TO TRACEValidate Your AWS Load Balancing Knowledge
Five questions covering ALB, NLB, listener rules, target groups, health checks and AWS WAF.
Complete the AWS Load Balancing Lab
After inspecting the application architecture, modifying listener and target controls, and investigating delivery failures, mark Lab 12 complete. Progress is self-reported and synchronized with the AWS workspace dashboard.
Advanced AWS Networking Completion Tracker
Track your progress across AWS Cloud WAN, Route 53 DNS engineering and enterprise application delivery. Open any activity, mark your learning complete, or revisit a lab whenever needed.
AWS Cloud WAN & Global Networks
Core networks, regional edges, network segments, attachment policies and global routing investigation.
Amazon Route 53, DNS & Traffic Engineering
Public and private DNS, hybrid Resolver endpoints, routing policies, health checks and DNS troubleshooting.
AWS Load Balancing & Application Delivery
ALB, NLB, listeners, target groups, TLS, health checks, AWS WAF and multi-AZ resilience.
Network Observability · Failure Investigation · Enterprise Capstone
AWS Network Observability, VPC Flow Logs & Traffic Analysis
Investigate enterprise AWS networking with VPC Flow Logs, CloudWatch, Reachability Analyzer, Traffic Mirroring and network telemetry. Learn how to distinguish rejected traffic, missing routes, application failures and incomplete observability.
Traffic, Telemetry & Investigation Pipeline
Select a component to inspect how VPC traffic can be observed using flow records, metrics, configuration analysis and packet-level capture.
Four Complementary Observability Capabilities
VPC Flow Logs
Capture metadata about IP traffic at supported VPC, subnet or network-interface scopes. Analyze ACCEPT, REJECT, addresses, ports, protocols and byte counts.
TRAFFIC METADATAReachability Analyzer
Perform static network configuration analysis between supported sources and destinations. Identify configuration blockers without sending real test packets.
PATH REACHABILITYTraffic Mirroring & CloudWatch
Mirror supported EC2 network-interface traffic to a monitoring target, while CloudWatch provides metrics, alarms and operational visibility.
PACKETS & METRICSConfigure Visibility & Network Controls
Change the modeled network configuration and observability capabilities. Observe how missing telemetry can complicate incident investigation.
Network Path Controls
Observability Controls
Run the AWS Traffic Analysis Engine
Select a traffic scenario and inject a fault. The investigation engine checks routing, security controls, application health and telemetry availability.
Traffic Investigation Controls
Network Investigation Trace
READY TO INVESTIGATEValidate Your AWS Network Observability Knowledge
Five questions covering flow metadata, static reachability, packet capture, CloudWatch and security troubleshooting.
Complete the AWS Network Observability Lab
After inspecting the observability architecture, modifying telemetry controls and investigating network failures, mark Lab 13 complete. Progress is self-reported and synchronized with the AWS workspace dashboard.
AWS Network Failure Investigation & Production Troubleshooting
Investigate enterprise AWS network incidents across VPC routing, Transit Gateway, security groups, network ACLs, DNS, hybrid connectivity and application delivery. Build a structured troubleshooting workflow using evidence, packet paths and root-cause isolation.
Multi-VPC, Transit Gateway & Hybrid Connectivity
Select any component to inspect its role in production connectivity. The diagram highlights the enterprise routing and security layers investigated in this lab.
Select an AWS Network Failure Scenario
Choose one of six incident types. Each scenario changes the modeled configuration, diagnostic outputs and root-cause evidence.
Diagnose the Incident Using Evidence
Run a diagnostic command, inspect its output and trace the modeled packet path. Commands are simulated AWS investigation shortcuts rather than live AWS CLI calls.
Diagnostic CLI Console
Incident Packet-Path Analysis
INCIDENT ACTIVERoot-cause evidence will appear after running diagnose.
Validate Your Production Troubleshooting Knowledge
Five questions covering Transit Gateway routing, security enforcement, asymmetric paths, DNS and evidence-based fault isolation.
Complete the AWS Failure Investigation Lab
After investigating routing, security, DNS and hybrid network incidents, mark Lab 14 complete. Progress is self-reported and synchronized with the AWS workspace dashboard. No assessment score is required.
Enterprise AWS Networking & Security Capstone
Design, validate and troubleshoot an enterprise AWS network spanning multiple VPCs, centralized routing, hybrid connectivity, security inspection, private application access, DNS, load balancing and observability. Apply the engineering principles developed throughout the previous fourteen labs.
Global AWS Networking & Security Architecture
Inspect the enterprise topology. Select a component to understand its engineering role, operational dependencies and production failure considerations.
Five Production Architecture Requirements
Connect regional networks using approved Cloud WAN segments and routing policies.
Provide controlled on-premises access through approved VPN or Direct Connect paths.
Apply appropriate inspection and network segmentation to protected traffic.
Enable private application access with correct endpoints, DNS and policy controls.
Validate load balancing, route health, telemetry and failure investigation.
Configure the Enterprise Network
Enable or disable architecture capabilities and evaluate how the resulting design affects enterprise connectivity. This is a conceptual simulation, not a live AWS deployment.
Connectivity & Routing Controls
Security & Application Controls
Validate Five Critical Network Flows
Select a production traffic flow and run the modeled packet-path evaluation. The engine checks required routing, security, DNS and application dependencies.
Traffic Scenario
Packet Path & Root-Cause Analysis
READY TO EVALUATEEnterprise AWS Architecture Knowledge Check
Review the critical design principles from the AWS networking and security workspace.
Complete the Enterprise AWS Capstone
After reviewing the architecture, validating network paths and completing the engineering assessment, mark Lab 15 complete. Completion is self-reported and synchronized with the AWS workspace dashboard.
Production Engineering Completion Tracker
Complete the final stage of the AWS Cloud Networking & Security Learning Workspace. Track progress across network observability, production failure investigation and the enterprise AWS architecture capstone.
Track Your Production Engineering Progress
Open any lab, mark it complete or incomplete, and monitor your progress. Completion is self-reported and does not depend on assessment scores or simulator validation.