NI
NETWORK INSIGHT THE VISUAL AGE · LEARNING WORKSPACES
AWS Cloud Networking & Security · Workspace 10

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.

15 Engineering Labs
05 Learning Stages
AWS Enterprise Cloud Architecture
AWS ENTERPRISE NETWORK VPC NETWORKING SUBNETS · ROUTING TRANSIT GATEWAY MULTI-VPC CONNECTIVITY DIRECT CONNECT HYBRID ENTERPRISE NETWORK SECURITY FIREWALL · PRIVATELINK AWS CLOUD WAN GLOBAL CONNECTIVITY OBSERVABILITY FLOW LOGS · DIAGNOSTICS
Engineering Foundations · AWS Networking

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.

01 · CONNECTIVITY
Network Reachability

VPC CIDRs, subnet routing, gateways, attachments and network paths determine which destinations are reachable.

02 · ROUTING
Enterprise Transit

Transit Gateway and Cloud WAN connect distributed environments through managed routing constructs.

03 · SECURITY
Policy Enforcement

Security groups, network ACLs, firewalls and identity controls restrict permitted communication.

04 · OPERATIONS
Network Evidence

Flow Logs, route inspection, Reachability Analyzer and telemetry support troubleshooting.

Interactive Enterprise Architecture Explorer

Inside an AWS Enterprise Network

Explore six architecture layers and select individual network components to inspect their responsibilities, dependencies and engineering considerations.

Enterprise AWS Architecture CONCEPTUAL MODEL
Selected Path Network Services Security & Control
Architecture Component

Engineering Consideration

Interactive Engineering Investigation

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
Routing Path Available Required routes and attachments exist
Security Policy Permits Traffic Relevant security controls allow the flow
Destination Healthy Target service is available
Traffic Investigation Result
PATH AVAILABLE

Engineering Diagnosis
Structured Engineering Curriculum

Five Stages of Enterprise AWS Networking

Progress from foundational VPC architecture to enterprise connectivity, cloud security, advanced networking and production operations.

STAGE 01 · LABS 1–3
Network Foundations
  • VPC architecture
  • Subnets and route tables
  • Security groups and NACLs
STAGE 02 · LABS 4–6
Enterprise Connectivity
  • VPC peering
  • Transit Gateway
  • Direct Connect
STAGE 03 · LABS 7–9
Cloud Security
  • Network Firewall
  • PrivateLink
  • Multi-account security
STAGE 04 · LABS 10–12
Advanced Networking
  • Cloud WAN
  • Route 53
  • Load balancing
STAGE 05 · LABS 13–15
Production Engineering
  • Network observability
  • Failure investigation
  • Enterprise capstone
AWS Cloud Networking · 15 Engineering Labs

Your Enterprise AWS Engineering Journey

Each lab will provide a dedicated interactive engineering environment with architecture exploration, configurable scenarios, technical explanations and investigations.

Network Insight · Cloud Engineering

From Cloud Architecture to Engineering Mastery

Explore the architecture above, investigate traffic paths and prepare for the 15-lab AWS networking curriculum.

Launch Architecture Explorer ↑
Network Insight · The Visual Age

Explore the Architecture. Understand the Technology. Engineer the Future.

Network Insight · AWS Learning Workspace · Dashboard V2

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.

15 Engineering Labs 5 Learning Stages Interactive Architecture Production Troubleshooting Enterprise Capstone
0 / 15 Labs Completed
0 / 5 Stages Completed
15 Labs Remaining
ACTIVE Workspace Status
0% OVERALL PROGRESS
Five-Stage Learning Architecture

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.

Interactive Lab Directory

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.

Engineering Progress Matrix

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.

Workspace progress is ready.
Final Engineering Challenge

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.

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · 15 LABS · 5 STAGES · DASHBOARD V2

AWS Cloud Networking & Security · Stage 1 · Lab 01

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.

VPC & CIDR Two Availability Zones Public / Private Subnets Route Tables Security Groups Traffic Diagnostics
Interactive AWS VPC Engineering Model

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.

VPC 10.20.0.0/16 · eu-west-1 · Two AZs INTERACTIVE TOPOLOGY
Subnet Design & Route Table Investigation

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.

DestinationTargetPurpose
Interactive Connectivity & Failure Investigation

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
Required Route AvailableSubnet route table contains the appropriate target
Security Group Allows FlowRequired stateful security group rules permit traffic
Network ACL Allows FlowStateless subnet ACL permits request and response
Required Endpoint AvailableGateway, workload and service prerequisites are healthy
Engineering Diagnostic Trace
PATH AVAILABLE

Engineering Knowledge Check

Validate Your VPC Architecture Understanding

Answer five technical questions covering AWS networking fundamentals. Your score is calculated locally and does not control lab completion.

Select an answer for each question, then check your results.
Lab 01 · Learning Progress

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.

LAB NOT COMPLETED
Return to AWS Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 1 · LAB 01

AWS Cloud Networking & Security · Stage 1 · Lab 02

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.

Subnet RoutingInternet Gateway NAT GatewayLongest Prefix Match Route Table EditorFailure Investigation
02Engineering Lab
03Routing Investigations
05Knowledge Questions
Interactive AWS Network Architecture

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.

AWS VPC · 10.30.0.0/16 · eu-west-1 ROUTING ARCHITECTURE
Interactive AWS Route Table Configuration

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
DestinationTargetAction
Ready to configure routes.
Subnet Classification & Routing Analysis
Engineering Principle A subnet is classified as public when its associated route table has a route to an Internet Gateway. A NAT Gateway route provides outbound IPv4 internet connectivity for private workloads, not direct inbound internet access.
AWS Routing Decision Engine

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
Production-Style Network Investigation

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
Internet Gateway AvailableVPC IGW attached and operational
NAT Gateway AZ-A HealthyOutbound translation available in AZ-A
NAT Gateway AZ-B HealthyOutbound translation available in AZ-B
Security Policies Permit TrafficSecurity groups and NACLs allow the flow
Connectivity Diagnostic Output
PATH AVAILABLE
Engineering Knowledge Assessment

Test Your AWS Routing Knowledge

Five questions covering subnet classification, longest prefix match, NAT Gateway design, route-table associations and AWS networking fundamentals.

Select your answers and check your score.
Stage 1 · Lab 02 · Learning Progress

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.

LAB 02 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 1 · LAB 02

AWS Cloud Networking & Security · Stage 1 · Lab 03

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.

Stateful Security Groups Stateless Network ACLs Inbound / Outbound Rules Ephemeral Ports Packet Flow Simulation Security Troubleshooting
Interactive AWS Security Architecture

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.

AWS VPC · 10.40.0.0/16 · Security Architecture INTERACTIVE PACKET PATH
Interactive Security Policy Engineering

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.

STATEFUL · SECURITY GROUP
Web Server Security Group
ProtocolPortPeer CIDRAction
Security groups evaluate allow rules. Return traffic for tracked connections is automatically permitted.
STATELESS · NETWORK ACL
Public Subnet Network ACL
#PortCIDREffect
Network ACLs evaluate the lowest matching rule number first. An unmatched packet is denied.
Interactive Packet-Flow Investigation

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
Web Server AvailableTCP service listener and basic network reachability
This simulator evaluates TCP IPv4 packets and simplified security policies. It assumes valid VPC routing, public addressing where needed, and an established return path. It does not connect to AWS.
Packet Evaluation Trace
CONNECTION ALLOWED
TCP Return-Traffic Engineering

Why 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.

Ephemeral-port ranges vary by client operating system and configuration. AWS NACL rules should account for the actual clients and services involved rather than assuming one universal ephemeral range.
Engineering Knowledge Assessment

Validate Your AWS Security Knowledge

Five questions covering security group connection tracking, NACL rule ordering, default-deny behavior, subnet security and ephemeral TCP ports.

Select an answer for each question, then check your score.
Stage 1 · Lab 03 · Learning Progress

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.

LAB 03 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 1 · LAB 03

Network Insight · AWS Learning Workspace · Stage 01

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.

0% STAGE PROGRESS
0Labs Completed
3Labs Remaining
3Stage 1 Activities
LAB 01 NOT COMPLETED
AWS VPC Architecture Explorer

Explore VPC CIDRs, Availability Zones, subnets, routing domains and enterprise network architecture.

LAB 02 NOT COMPLETED
Subnets, Route Tables & Internet Gateways

Engineer subnet routes, inspect Internet Gateway and NAT dependencies, and investigate connectivity failures.

LAB 03 NOT COMPLETED
Security Groups vs Network ACLs

Compare stateful and stateless controls, configure security policies, and trace TCP return traffic.

Stage 1 In Progress Complete the three activities to finish Architecture & Foundations.
STAGE IN PROGRESS
AWS Cloud Networking & Security · Stage 2 · Lab 04

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.

Multi-VPC Architecture VPC Peering Connections CIDR Overlap Detection Bidirectional Routing Non-Transitive Connectivity Failure Investigation
03Isolated AWS VPCs
03Possible Peering Links
05Engineering Questions
Interactive Multi-VPC Architecture

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.

AWS Region · eu-west-1 · Enterprise VPC Peering INTERACTIVE TOPOLOGY
VPC Peering Control Plane

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
Requester / AccepterVPC A / VPC B
CIDR ValidationChecking
Peering StateActive
Select a connection to inspect its state.
VPC CIDR Configuration
This is a simulated CIDR editor. In AWS, changing a VPC primary CIDR is not equivalent to editing a text field; VPC CIDR lifecycle constraints apply.
Allow Application TrafficSimplified security group and NACL policy state
Bidirectional AWS Route Table Engineering

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
DestinationTargetAction
Choose a destination and direct peering target.
Routing Domain Analysis
Non-Transitive Routing

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.

Route Table Scope

This lab models one workload route table per VPC. Real VPCs may contain multiple subnets associated with different route tables.

Production Connectivity Investigation

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
Educational simulation only. It models IPv4 routing and simplified security conditions rather than live AWS VPC resources or packet captures.
Routing and Connectivity Trace
PATH AVAILABLE
Engineering Knowledge Assessment

Validate Your VPC Peering Knowledge

Five questions covering peering CIDR constraints, routing requirements, transitive routing, security controls and production network design.

Select an answer for each question, then check your score.
Stage 2 · Lab 04 · Learning Progress

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.

LAB 04 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 2 · LAB 04

AWS Cloud Networking & Security · Stage 2 · Lab 05

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.

Transit Gateway Hub VPC Attachments Route Table Associations Route Propagation Network Segmentation Blackhole Routes Traffic Investigation
04VPC Attachments
02TGW Route Tables
05Engineering Questions
Interactive Enterprise AWS Architecture

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.

AWS Region · eu-west-1 · Transit Gateway Hub INTERACTIVE TOPOLOGY
Transit Gateway Control Plane

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
VPC CIDR
Attachment Status
Attachment AvailableSimulate attachment failure or restoration
Select an attachment to inspect its routing domain.
Propagation Manager
Route Propagation EnabledAdvertise attachment CIDR into selected TGW table
Propagation adds a learned destination route to a selected Transit Gateway route table.
Important distinction: Association determines which route table an incoming packet consults. Propagation determines which routes an attachment contributes to a route table. These are independent controls.
Transit Gateway Route Table Engineering

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
DestinationTargetType
Static routes can override propagated routes for the same destination prefix.
Routing Domain Segmentation
Production Domain

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.

Application↔Production TGW RT↔Shared Services
Isolated Domain

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.

Analytics↔Isolated TGW RT
This simulator uses one non-overlapping IPv4 CIDR per VPC and one simplified subnet route table per VPC. Real Transit Gateway designs may require multiple subnet route tables, attachment subnets, AZ considerations and additional route propagation controls.
VPC Route Table Dependencies

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
Route to Transit GatewayDestination CIDR → TGW target
Select a source and remote destination to inspect the modeled VPC route.
VPC Routing Matrix
SourceRemote VPCs Routed via TGW
In AWS, route tables are associated with subnets. The simplified matrix here represents the route table used by each lab workload.
Production Network Failure Investigation

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
This is a conceptual AWS Transit Gateway control-plane and routing simulator. It does not connect to AWS or validate live security groups, network ACLs, firewalls or appliance mode behavior.
End-to-End Routing Trace
PATH AVAILABLE
Engineering Knowledge Assessment

Validate Your Transit Gateway Knowledge

Five questions covering attachment associations, propagation, route selection, blackholes and VPC-side routing dependencies.

Select an answer for each question, then check your score.
Stage 2 · Lab 05 · Learning Progress

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.

LAB 05 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 2 · LAB 05

AWS Cloud Networking & Security · Stage 2 · Lab 06

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.

Enterprise Data Centre Direct Connect Location Private & Transit VIFs Direct Connect Gateway BGP Routing Site-to-Site VPN Backup Hybrid Troubleshooting
02Hybrid Transport Paths
02Virtual Interface Models
05Engineering Questions
Interactive Hybrid Cloud Architecture

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.

Hybrid Network · On-Premises ↔ AWS eu-west-1 INTERACTIVE ARCHITECTURE
Hybrid Connectivity Control Plane

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
DX Physical Circuit AvailableCustomer router to AWS Direct Connect location
Transit VIF ConfiguredTransit VIF → Direct Connect Gateway → TGW
DX BGP Session EstablishedSimulated customer and AWS BGP adjacency
DXGW / TGW Association ValidGateway association and allowed prefixes modeled
Direct Connect is a dedicated network connection, not encryption by default. Use appropriate encryption technologies when confidentiality is required.
Site-to-Site VPN Backup
VPN Tunnel AvailableIPsec transport over the internet
VPN BGP Session EstablishedDynamic route exchange over VPN
TGW Hybrid Routes InstalledRequired TGW and VPC forwarding routes
Security Policy Allows TrafficSimplified SG, NACL and firewall permissions
The baseline has both Direct Connect and VPN paths available.
BGP Engineering Workbench

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
The numeric preferences are a simplified customer-side routing-policy model: higher is preferred. They are not editable AWS Direct Connect local-preference attributes.
Candidate Route Table
TransportNext HopPreferenceState
Selected Path: Direct Connect
Both candidate paths are available.
Virtual Interface Design

Private VIF vs Transit VIF

PRIVATE VIRTUAL INTERFACE
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.

Example: On-premises → Direct Connect → Private VIF → Virtual Private Gateway → VPC.
TRANSIT VIRTUAL INTERFACE
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.

Example: On-premises → Direct Connect → Transit VIF → DX Gateway → Transit Gateway → VPC attachments.
Production Failure Investigation

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
This lab simulates control-plane state and high-level traffic forwarding. It does not connect to AWS, validate live BGP sessions or model every AWS route-priority rule.
Connectivity Investigation Results
PATH AVAILABLE
Engineering Knowledge Assessment

Validate Your Hybrid Networking Knowledge

Five questions covering Direct Connect, BGP, transit VIFs, hybrid resilience and security.

Select an answer for each question, then check your score.
Stage 2 · Lab 06 · Learning Progress

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.

LAB 06 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 2 · LAB 06

Network Insight · AWS Learning Workspace · Stage 02

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.

VPC Peering & Routing Transit Gateway Direct Connect & BGP Hybrid Resilience
0% Complete
0 / 3 Engineering labs
completed in Stage 2
Stage 2 Engineering Progress 0 of 3 labs complete
Lab 4 · VPC Peering
Lab 5 · Transit Gateway
Lab 6 · Hybrid Networking

Stage 2 Engineering Activities

Self-reported completion · No quiz gating
04
NOT COMPLETED
AWS VPC Peering & Routing

Explore VPC peering connections, route-table dependencies, non-transitive routing, overlapping CIDR restrictions and connectivity troubleshooting.

VPC Peering Route Tables Non-Transitive Routing
Open Lab 4 ↗
05
NOT COMPLETED
AWS Transit Gateway Architecture

Engineer a scalable hub-and-spoke architecture using VPC attachments, Transit Gateway route-table associations, propagation, segmentation and blackhole routes.

TGW Attachments Route Propagation Segmentation
Open Lab 5 ↗
06
NOT COMPLETED
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.

Direct Connect BGP Routing VPN Failover
Open Lab 6 ↗

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.

◌ STAGE IN PROGRESS
AWS Cloud Networking & Security · Stage 3 · Lab 07

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.

AWS Network Firewall Inspection VPC Transit Gateway Stateless Rule Groups Stateful Rule Groups Symmetric Routing Failure Investigation
03VPC Security Domains
02Firewall Inspection Layers
05Engineering Questions
Interactive AWS Security Architecture

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.

AWS Region · eu-west-1 · Centralized Security Inspection INTERACTIVE ARCHITECTURE
Security Architecture Workbench

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
Transit Gateway RoutingSource and destination attachments have valid routes
Central Inspection RoutingTraffic is steered through inspection VPC
Firewall Endpoint AvailableAWS Network Firewall endpoint health
Return-Path SymmetryReturn traffic traverses same stateful inspection path
A Transit Gateway attachment's appliance mode can help maintain flow affinity through a stateful inspection appliance. It does not automatically configure all required route tables.
Firewall Policy Processing
Stateless Inspection EnabledEvaluate the lab's stateless policy layer
Stateful Inspection EnabledEvaluate connection-aware policy rules
Application Security Allows TrafficModeled security groups and network ACLs
All baseline routing and inspection dependencies are enabled.
Firewall Policy Engineering

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 InspectionPacket-oriented matching. In this lab, lower numerical priority is evaluated first. A matching forward action passes the packet to stateful inspection.
Stateful InspectionConnection-aware filtering. The lab evaluates explicit application rules and models a stateful response path when symmetry is maintained.
Stateless Rule Group
PriorityPortAction
Unmatched packets are forwarded to stateful inspection in this lab baseline.
Stateful Rule Group
ProtocolPortAction
The lab models a strict default-drop policy when no stateful pass rule matches.
Network Security Failure Investigation

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
Educational model: this lab simplifies AWS Network Firewall policy evaluation. Production behavior depends on rule-group order, stateless default actions, stateful rule-order configuration, stream state, routing and service-specific settings.
Firewall Inspection Results
READY TO INSPECT
Run a traffic scenario to inspect its forwarding and security decisions.
Engineering Knowledge Assessment

Validate Your AWS Network Firewall Knowledge

Five questions covering centralized inspection, stateless rules, stateful policies, routing symmetry and firewall endpoints.

Select an answer for each question, then check your score.
Stage 3 · Lab 07 · Learning Progress

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.

LAB 07 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 3 · LAB 07

AWS Cloud Networking & Security · Stage 3 · Lab 08

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.

Interface Endpoints Gateway Endpoints AWS PrivateLink Private DNS Endpoint Policies Security Groups Cross-VPC Services
03Endpoint Architectures
02DNS Resolution Models
05Engineering Questions
Interactive Private Connectivity Architecture

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.

Consumer VPC ↔ Private AWS Services INTERACTIVE ARCHITECTURE
Architecture Design Comparison

Choose the Correct Endpoint Architecture

INTERFACE ENDPOINT
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 GROUPS
GATEWAY ENDPOINT
S3 / 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 POLICY
ENDPOINT SERVICE
Private 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 ENDPOINT
Private Connectivity Workbench

Configure 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
Interface Endpoint AvailableEndpoint ENI deployed in consumer subnet
Private DNS Resolution CorrectService name resolves to endpoint private IP
Endpoint Security Group Allows TrafficInbound HTTPS from consumer workloads
Endpoint Service Permission GrantedConsumer permitted and connection accepted
Gateway Endpoint & Policies
Gateway Endpoint AvailableS3 gateway endpoint provisioned
Subnet Route Table AssociatedRelevant S3 prefix-list route installed
Endpoint Policy Permits RequestModeled endpoint-level authorization
Application Authorization Permits RequestModeled IAM and resource-policy permissions
All endpoint dependencies are enabled.
Production Connectivity Troubleshooting

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
Educational model: real endpoint access also depends on service-specific DNS behavior, subnet placement, NACLs, endpoint state, IAM, resource policies, TLS and service availability.
Private Connectivity Results
READY TO TRACE
Select a scenario and run the connectivity trace.
Engineering Knowledge Assessment

Validate Your AWS PrivateLink Knowledge

Five questions covering interface endpoints, gateway endpoints, DNS, endpoint services and authorization.

Select an answer for each question, then check your score.
Stage 3 · Lab 08 · Learning Progress

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.

LAB 08 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 3 · LAB 08

AWS Cloud Networking & Security · Stage 3 · Lab 09

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.

AWS Organizations Multi-Account Security Zero Trust TGW Segmentation IAM Authorization Security Groups East-West Isolation
04Enterprise Security Domains
03Policy Enforcement Layers
05Engineering Questions
Interactive Enterprise AWS Security Architecture

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.

AWS Organization · Segmented Enterprise Network INTERACTIVE ARCHITECTURE
Zero Trust Security Principles

Three Independent Security Decisions

NETWORK CONTROL
Transit Gateway Segmentation

Transit Gateway route-table associations and propagations control which VPC attachments can route to other network domains.

ROUTING REACHABILITY
WORKLOAD CONTROL
Security Groups & Network ACLs

Workload-level security groups and subnet network ACLs enforce permitted traffic independently of the routing architecture.

PACKET FILTERING
IDENTITY CONTROL
Identity & Application Authorization

IAM, resource policies and application-level authentication determine whether an identity can perform a protected operation.

LEAST-PRIVILEGE AUTHORIZATION
Segmentation Engineering Workbench

Configure 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
Production → Shared Services RouteProduction TGW route table includes Shared Services prefix
Development → Production RouteDevelopment network can reach Production prefix
Production → Security Services RouteProduction can reach security inspection services
Return Routes AvailableDestination networks have valid return routes
Workload & Identity Security Controls
Shared Services Security GroupPermits approved application traffic
Production Security GroupPermits approved access to Production
Identity AuthorizationRequesting identity has required permissions
Service Control Policy Allows OperationNo applicable organization-level explicit deny
Baseline: Production can access approved shared services, while Development is isolated from Production.
Zero Trust Access Decision Engine

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
Educational model: AWS Transit Gateway controls routing, not user identity. IAM and SCP checks apply to AWS API operations, while ordinary application traffic may require separate application authentication and authorization.
Security Decision Trace
READY TO EVALUATE
Select a scenario and evaluate the access request.
Engineering Knowledge Assessment

Validate Your AWS Zero Trust Knowledge

Five questions covering multi-account boundaries, TGW segmentation, security groups, identity authorization and least privilege.

Select an answer for each question, then check your score.
Stage 3 · Lab 09 · Learning Progress

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.

LAB 09 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 3 · LAB 09

Network Insight · AWS Learning Workspace · Stage 03 of 05

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.

Lab 07 · Network Firewall Lab 08 · PrivateLink Lab 09 · Zero Trust Self-Reported Progress Dashboard Synchronization
0% STAGE PROGRESS
0 of 3 labs completed
ENGINEERING LAB 07

AWS Network Firewall & Centralized Inspection

Inspect firewall endpoints, stateless and stateful rules, centralized security routing and symmetric inspection paths.

NOT COMPLETED
Open Activity ↗
ENGINEERING LAB 08

AWS PrivateLink & VPC Endpoints

Explore interface endpoints, gateway endpoints, private DNS, endpoint policies and private connectivity troubleshooting.

NOT COMPLETED
Open Activity ↗
ENGINEERING LAB 09

AWS Zero Trust & Multi-Account Segmentation

Investigate cross-account trust boundaries, Transit Gateway segmentation, workload security and identity authorization.

NOT COMPLETED
Open Activity ↗
Your progress is saved locally in this browser and shared with the AWS workspace dashboard.
AWS Cloud Networking & Security · Stage 4 · Lab 10

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 Core Network Edges Network Segments Attachment Policies Inter-Region Routing Failure Investigation
03Regional Network Domains
02Segmentation Policies
05Engineering Questions
Interactive Global Network Architecture

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.

AWS Global Network · Multi-Region Core INTERACTIVE ARCHITECTURE
Cloud WAN Design Principles

Centralized Policy, Distributed Connectivity

CORE NETWORK
Regional Core Network Edges

Cloud WAN provides a centrally managed global core network with regional core network edges where supported attachments connect.

REGIONAL CONNECTIVITY
NETWORK SEGMENTS
Policy-Based Segmentation

Segments define routing domains. Segment actions and sharing policies determine permitted route exchange between otherwise isolated environments.

CONTROLLED ROUTE SHARING
ATTACHMENT POLICY
Attachment Associations

Attachment policies can assign resources to network segments using supported attachment attributes, tags and policy rules.

CENTRALIZED GOVERNANCE
Cloud WAN Engineering Workbench

Configure 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
Europe Core Network Edgeeu-west-1 core network connectivity
North America Core Network Edgeus-east-1 core network connectivity
Asia-Pacific Core Network Edgeap-southeast-1 core network connectivity
Inter-Region Core ConnectivityModeled core path between regional edges
Routing & Segment Policy Controls
Production Segment SharingAllow approved Production cross-region routes
Development → Production SharingPermit cross-segment route sharing
VPC Attachment AssociationsVPC attachments assigned to intended segments
Return Routes AvailableBidirectional reachability between source and destination
Baseline: Production regions are connected; Development remains isolated from Production.
Global Network Failure Investigation

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
Educational model: AWS Cloud WAN behavior depends on the deployed core network policy, attachment state, segment configuration, route propagation and regional service support. This simulator is not connected to an AWS account.
Cloud WAN Route Trace
READY TO TRACE
Select a scenario and run the global routing trace.
Engineering Knowledge Assessment

Validate Your AWS Cloud WAN Knowledge

Five questions covering core networks, regional edges, segments, attachment policies and route sharing.

Select an answer for each question, then check your score.
Stage 4 · Lab 10 · Learning Progress

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.

LAB 10 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 4 · LAB 10

AWS Cloud Networking & Security · Stage 4 · Lab 11

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.

Route 53Public Hosted Zones Private Hosted ZonesRoute 53 Resolver Hybrid DNSWeighted Routing Latency RoutingFailover
04DNS Architecture Components
04Routing Policy Scenarios
05Engineering Questions
Interactive DNS 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.

Enterprise AWS DNS Resolution Architecture INTERACTIVE
DNS Traffic Engineering

Route 53 Routing Policies

WEIGHTED
Weighted Routing

Distribute DNS answers between eligible records using configured relative weights. DNS caching means request-level traffic ratios are not guaranteed.

TRAFFIC DISTRIBUTION
LATENCY
Latency-Based Routing

Return records based on AWS latency measurements between users' resolver locations and AWS Regions, subject to routing configuration.

REGIONAL PERFORMANCE
FAILOVER
Failover Routing

Use primary and secondary records with health evaluation to influence authoritative DNS responses during service failures.

RESILIENCE & RECOVERY
DNS Engineering Workbench

Configure DNS Infrastructure & Health

Toggle public DNS, private DNS and hybrid forwarding dependencies, and change endpoint health to investigate how DNS resolution behaves.

DNS Infrastructure
Public Hosted Zone RecordPublic authoritative record exists
Private Hosted Zone AssociationPrivate zone associated with querying VPC
Resolver Inbound EndpointHybrid on-premises queries can reach inbound resolver
Resolver Forwarding RuleOutbound DNS forwarding for on-premises domain
Routing & Endpoint Health
Primary Endpoint HealthyPrimary application endpoint passes health check
Secondary Endpoint HealthySecondary application endpoint passes health check
Hybrid Network Path AvailableConnectivity and DNS security rules permit queries
Baseline: public and private DNS records are configured, hybrid resolution is available and both application endpoints are healthy.
DNS Failure Investigation

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
This is a conceptual DNS simulator. DNS TTL, recursive resolver caching, health-check intervals and resolver behavior can delay observed changes. Weighted policies distribute authoritative answers, not individual application requests.
DNS Resolution Trace
READY TO RESOLVE
Select a query scenario and run the DNS resolution simulator.
Engineering Knowledge Assessment

Validate Your DNS Engineering Knowledge

Five questions covering public DNS, private hosted zones, hybrid DNS, routing policies and health-based failover.

Select an answer for each question, then check your score.
Stage 4 · Lab 11 · Learning Progress

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.

LAB 11 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 4 · LAB 11

AWS Cloud Networking & Security · Stage 4 · Lab 12

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.

Application Load BalancerNetwork Load Balancer ListenersTarget Groups TLS TerminationHealth Checks Multi-AZ ResilienceAWS WAF
02Load Balancer Architectures
03Application Delivery Layers
05Engineering Questions
Interactive Enterprise Application Architecture

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.

Internet → ALB → Multi-AZ Application Targets INTERACTIVE
Load Balancer Design Principles

ALB, NLB & Application Security

LAYER 7
Application Load Balancer

Supports HTTP/HTTPS routing using listener rules, hostnames, paths, headers and target groups. Can integrate with AWS WAF.

APPLICATION-AWARE ROUTING
LAYER 4
Network 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 DELIVERY
RESILIENCE
Target Health & Multi-AZ

Health checks determine target eligibility. Distributing healthy targets across Availability Zones improves availability during failures.

HEALTH-AWARE TARGET SELECTION
Application Delivery Engineering Workbench

Configure 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
HTTPS Listener EnabledALB listener accepts TCP/443 HTTPS requests
TLS Certificate ValidClient can validate the presented certificate
AWS WAF Permits RequestAssociated WAF web ACL allows the request
Load Balancer Security GroupInbound HTTPS allowed from the client
Target Group & Availability Controls
Target Group ConfiguredListener forwards requests to target group
Availability Zone A HealthyApplication targets in AZ-A pass health checks
Availability Zone B HealthyApplication targets in AZ-B pass health checks
Target Security Group Permits TrafficLoad balancer can reach application target port
Baseline: HTTPS listener, WAF, security groups and application targets are healthy.
Production Application Failure Investigation

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
Educational model: ALB operates at the application layer, while NLB supports transport-level load balancing. AWS WAF attaches directly to supported application-layer resources such as ALB, not directly to NLB. Health checks, cross-zone settings and fail-open behavior can affect real-world outcomes.
Application Delivery Trace
READY TO TRACE
Select a request scenario and run the application delivery trace.
Engineering Knowledge Assessment

Validate Your AWS Load Balancing Knowledge

Five questions covering ALB, NLB, listener rules, target groups, health checks and AWS WAF.

Select an answer for each question, then check your score.
Stage 4 · Lab 12 · Learning Progress

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.

LAB 12 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 4 · LAB 12

AWS Cloud Networking & Security · Stage 4 Completion

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.

0 of 3 Labs Completed Stage 4 learning in progress
0%
Complete Labs 10–12 to finish Stage 4.
10 NOT COMPLETED

AWS Cloud WAN & Global Networks

Core networks, regional edges, network segments, attachment policies and global routing investigation.

Open Activity
11 NOT COMPLETED

Amazon Route 53, DNS & Traffic Engineering

Public and private DNS, hybrid Resolver endpoints, routing policies, health checks and DNS troubleshooting.

Open Activity
12 NOT COMPLETED

AWS Load Balancing & Application Delivery

ALB, NLB, listeners, target groups, TLS, health checks, AWS WAF and multi-AZ resilience.

Open Activity
AWS Cloud Networking & Security · Stage 5 · Lab 13

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.

VPC Flow Logs CloudWatch Reachability Analyzer Traffic Mirroring ACCEPT / REJECT Network Diagnostics
04Observability Tools
06Failure Investigation Checks
05Engineering Questions
Interactive Network Observability Architecture

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.

AWS Network Observability Architecture INTERACTIVE
AWS Network Investigation Toolkit

Four Complementary Observability Capabilities

FLOW RECORDS
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 METADATA
CONFIGURATION ANALYSIS
Reachability Analyzer

Perform static network configuration analysis between supported sources and destinations. Identify configuration blockers without sending real test packets.

PATH REACHABILITY
PACKET VISIBILITY
Traffic Mirroring & CloudWatch

Mirror supported EC2 network-interface traffic to a monitoring target, while CloudWatch provides metrics, alarms and operational visibility.

PACKETS & METRICS
Network Telemetry Workbench

Configure Visibility & Network Controls

Change the modeled network configuration and observability capabilities. Observe how missing telemetry can complicate incident investigation.

Network Path Controls
Route Table Entry Present Required route to destination exists
Security Group Permits Traffic Stateful security group rules allow flow
Network ACL Permits Traffic Stateless subnet ACL permits required directions
Application Listener Healthy Destination service accepts connections
Observability Controls
VPC Flow Logs Enabled Traffic metadata available for analysis
CloudWatch Metrics Available Operational metrics and alarms configured
Reachability Analysis Available Static path configuration analysis enabled
Traffic Mirroring Configured Supported packet capture source and target configured
Baseline: routing and security permit traffic; Flow Logs, CloudWatch and Reachability Analyzer are available.
Production Network Incident Investigation

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
This is an educational configuration and telemetry model. VPC Flow Logs contain sampled or aggregated flow metadata rather than full packet payloads. A missing flow record does not conclusively prove that no packet was transmitted.
Network Investigation Trace
READY TO INVESTIGATE
Select a scenario and run the traffic investigation.
Engineering Knowledge Assessment

Validate Your AWS Network Observability Knowledge

Five questions covering flow metadata, static reachability, packet capture, CloudWatch and security troubleshooting.

Select an answer for each question, then check your score.
Stage 5 · Lab 13 · Learning Progress

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.

LAB 13 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 5 · LAB 13

AWS Cloud Networking & Security · Stage 5 · Lab 14

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.

VPC Routing Transit Gateway Security Groups Network ACLs DNS Resolution Asymmetric Routing Root-Cause Analysis
06Production Incident Scenarios
08Diagnostic CLI Commands
05Engineering Questions
Interactive Enterprise AWS Topology

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.

Enterprise AWS Network · Incident Topology INTERACTIVE
Production Incident Generator

Select an AWS Network Failure Scenario

Choose one of six incident types. Each scenario changes the modeled configuration, diagnostic outputs and root-cause evidence.

Select a production incident to begin.
Network Engineering Investigation Console

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
network-insight@aws-investigation SIMULATED CLI
Supported commands: help, show routes, show tgw, show security, show dns, show flowlogs, ping, traceroute and diagnose.
Incident Packet-Path Analysis
INCIDENT ACTIVE
Select a scenario and run a diagnostic investigation.
Root-Cause Investigation

Root-cause evidence will appear after running diagnose.

Engineering Knowledge Assessment

Validate Your Production Troubleshooting Knowledge

Five questions covering Transit Gateway routing, security enforcement, asymmetric paths, DNS and evidence-based fault isolation.

Select an answer for each question, then check your score.
Stage 5 · Lab 14 · Learning Progress

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.

LAB 14 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 5 · LAB 14

AWS Cloud Networking & Security · Stage 5 · Final Capstone

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.

Multi-VPC Architecture Transit Gateway Cloud WAN Hybrid Connectivity Network Firewall PrivateLink Route 53 Load Balancing Observability
15 / 15 Final Engineering Lab
05 Architecture Objectives
05 Enterprise Traffic Scenarios
Interactive Enterprise Architecture

Global AWS Networking & Security Architecture

Inspect the enterprise topology. Select a component to understand its engineering role, operational dependencies and production failure considerations.

Enterprise AWS Architecture · Global View INTERACTIVE
Capstone Engineering Objectives

Five Production Architecture Requirements

01 Global Connectivity

Connect regional networks using approved Cloud WAN segments and routing policies.

02 Hybrid Networking

Provide controlled on-premises access through approved VPN or Direct Connect paths.

03 Centralized Security

Apply appropriate inspection and network segmentation to protected traffic.

04 Private Services

Enable private application access with correct endpoints, DNS and policy controls.

05 Production Resilience

Validate load balancing, route health, telemetry and failure investigation.

Capstone Architecture Configuration

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
Recommended baseline loaded. Run the architecture evaluation to validate the configured enterprise network.
Enterprise Traffic Engineering Challenge

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
0 / 5 Run the enterprise evaluation to calculate the modeled connectivity score.
Traffic evaluations are simplified logical checks. Actual AWS forwarding depends on subnet and TGW route tables, Cloud WAN policies, security rules, endpoint configuration and regional service behavior.
Packet Path & Root-Cause Analysis
READY TO EVALUATE
Select a traffic flow and run the evaluation.
Final Engineering Assessment

Enterprise AWS Architecture Knowledge Check

Review the critical design principles from the AWS networking and security workspace.

Select an answer for each question, then check your score.
Stage 5 · Lab 15 · Final Capstone

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.

LAB 15 NOT COMPLETED
Return to Dashboard ↑

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · FINAL CAPSTONE · LAB 15

AWS Cloud Networking & Security · Stage 5 Completion

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.

13–15 Labs in This Stage
0 / 3 Labs Completed
IN PROGRESS Stage Completion Status
0% STAGE COMPLETION
Final Three Engineering Labs

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.

Return to Workspace Dashboard ↑
Stage 5 progress is ready.

NETWORK INSIGHT · AWS CLOUD NETWORKING & SECURITY · STAGE 5 · PRODUCTION ENGINEERING