ANS-C01 Network Security Features and Architecture Guide

Study ANS-C01 network security architecture for WAF, Shield, Network Firewall, Gateway Load Balancer, security groups, NACLs, endpoint policies, perimeter VPCs, and trust boundaries.

Network security architecture questions on ANS-C01 start with the traffic path. AWS is not only testing whether you recognize WAF, Shield, Network Firewall, security groups, or endpoint policies. It is testing whether you place the right control on the right boundary without breaking routing, availability, or compliance intent.

The current AWS task statement is to implement and maintain network security features. The official scope includes threat models, common networking threats, inbound and outbound controls, inter-VPC and multi-account controls, perimeter VPCs, untrusted network zones, three-tier architectures, compliance testing, and automated incident reporting or alerting.

What the exam is really testing

Security decision What a strong answer checks
Traffic direction Inbound, outbound, east-west, hybrid, service-to-service, or administrator access.
Layer of enforcement DNS, edge, Layer 3/4, Layer 7, identity, endpoint policy, or workload security group.
Trust boundary Internet edge, perimeter VPC, shared services VPC, inspection VPC, application tier, data tier, or AWS service endpoint.
Routing support Whether traffic is actually steered through the selected control.
Operational model Single account, multi-account, central inspection, delegated admin, audit evidence, and alerting ownership.
Failure behavior Whether the control fails open, fails closed, or creates an availability bottleneck.

The strongest answers usually combine a control with the architecture that makes that control see the traffic.

Threat-boundary flow

Use this mental model before choosing a service.

    flowchart LR
	  U["Untrusted user or network"] --> E["Edge controls: Route 53, CloudFront, WAF, Shield"]
	  E --> P["Perimeter or ingress VPC"]
	  P --> I["Inspection path: Network Firewall, GWLB appliance, proxy"]
	  I --> A["Application tier: ALB, security groups, workload identity"]
	  A --> D["Data and service tier: security groups, endpoint policies, KMS"]
	  D --> L["Detection and audit: logs, metrics, Security Hub, alerts"]

If an answer adds a firewall but does not steer traffic through it, it is usually weaker than an answer that explicitly designs the route and inspection boundary.

Control placement chooser

Requirement Better first fit Why
Block SQL injection or application-layer web attacks AWS WAF on CloudFront, ALB, API Gateway, or AppSync where supported WAF evaluates HTTP(S) request attributes, not arbitrary packet flows.
Improve resilience against volumetric DDoS attacks AWS Shield plus edge-aware architecture Shield protects supported AWS edge and public resources from DDoS classes of attack.
Inspect outbound or east-west network flows AWS Network Firewall, GWLB appliances, or proxy architecture The traffic must be routed through an inspection point.
Restrict workload-to-workload access Security groups and segmentation Security groups are stateful workload boundary controls.
Add coarse subnet boundary filtering Network ACLs NACLs are stateless and subnet-scoped; they are not a replacement for security groups.
Restrict access to AWS services privately VPC endpoint policies, IAM, and service-specific policies Endpoint policy controls service access through the endpoint boundary.
Govern network security across accounts AWS Firewall Manager, Organizations, and delegated administration Central policy management is stronger than manual per-account drift.
Detect and escalate security events Logs, metrics, alarms, EventBridge, SNS, Security Hub, and ticketing integration Alerting must connect evidence to an operational response path.

Do not choose a control because it sounds more secure. Choose it because it can observe and enforce the relevant traffic.

Inbound security patterns

Inbound traffic usually crosses the most obvious trust boundary: public or partner traffic entering AWS.

Pattern Strong architecture
Public web application Route 53 or Global Accelerator to CloudFront or ALB, WAF at the supported edge or application entry point, security groups on downstream tiers.
DDoS-resistant public endpoint Shield-aligned public resource, WAF for application-layer filtering, autoscaling or resilient origin design, and health-based routing.
Partner or private ingress VPN, Direct Connect, PrivateLink, or peering/TGW with strict routing, security groups, endpoint policies, and logging.
Centralized inbound inspection Perimeter VPC or inspection VPC with route tables that force ingress through firewall appliances or Network Firewall where supported.
Administrative access Avoid broad public management ports; use private access patterns, identity controls, bastion only when justified, or managed access services.

Exam traps often put WAF, Shield, and Network Firewall in the same answer set. WAF is best for HTTP(S) application-layer filtering. Network Firewall is best for network-flow inspection and filtering. Shield is about DDoS protection for supported resources.

Outbound security patterns

Outbound control is about what workloads can reach and how that access is monitored.

Requirement Strong answer
EC2 workloads need S3 without public internet traversal S3 gateway endpoint plus bucket policy or endpoint-aware policy conditions.
Workloads need private access to AWS APIs Interface endpoints with endpoint policies where supported, security groups, and private DNS.
Internet egress must be inspected Route egress through Network Firewall, a proxy, or GWLB appliance fleet before NAT or internet exit.
Domain-based egress control is required Proxy, DNS controls, or firewall features that can enforce the needed layer.
Exfiltration risk is the concern Endpoint policies, IAM conditions, egress filtering, DNS logging, flow logs, and alerting.

Do not treat NAT gateway as a security control by itself. NAT changes the path to the internet, but it does not inspect application intent or enforce least privilege.

Inter-VPC and multi-account controls

ANS-C01 expects security architecture to work across accounts and VPCs, not just inside one subnet.

Design goal Strong pattern
Separate production, development, and shared services Separate accounts and VPC route domains, then connect only the required paths.
Centralize inspection Transit Gateway route tables, appliance mode where appropriate, Network Firewall, GWLB, or inspection VPC design.
Prevent accidental broad connectivity Control route propagation, use specific TGW route tables, avoid peering sprawl, and document permitted paths.
Expose one shared service to many consumers PrivateLink instead of broad network routing when consumers only need the service.
Apply consistent firewall policy AWS Firewall Manager with Organizations where central governance is required.
Audit cross-account posture Centralized logs, Security Hub aggregation, Config rules, and delegated administrator patterns.

The key exam distinction is routing versus service exposure. Transit Gateway gives routable network domains. PrivateLink exposes a service endpoint without giving consumers broad access to the provider VPC.

Three-tier and perimeter architectures

A professional AWS network security design usually separates tiers and trust zones.

Zone or tier Typical controls
Edge Route 53, CloudFront, WAF, Shield, Global Accelerator, public ALB or NLB where required.
Perimeter or ingress VPC Public subnets, ingress routing, firewall or appliance insertion, logging, and strict route boundaries.
Application tier Private subnets, ALB or NLB internal placement, security groups, autoscaling, and no unnecessary direct internet exposure.
Data tier Private subnets, tightly scoped security groups, endpoint policies, KMS, database-native controls, and backup/audit evidence.
Shared inspection Transit Gateway, Network Firewall, GWLB, route tables, appliance mode where needed, and centralized logging.
Shared services DNS Resolver, endpoints, directory services, logging, and management services with least-privilege access.

Three-tier architecture is not just “public, private, database.” For ANS-C01, it means controlled trust transitions and route-aware inspection between tiers.

Security groups, NACLs, and endpoint policies

These controls are often confused in answer choices.

Control Exam distinction
Security group Stateful, attached to ENIs or supported resources, and usually the first workload-level allow-list control.
Network ACL Stateless, subnet-scoped, ordered rules; useful for coarse guardrails but easier to misconfigure for ephemeral return traffic.
Route table Determines where traffic goes; it is not a filtering control unless it intentionally omits a path or uses blackhole behavior.
Endpoint policy Restricts what can be accessed through a VPC endpoint; combine with IAM and resource policy when needed.
IAM policy Authorizes API actions; it does not replace network path controls.
Resource policy Controls access to the target resource, often useful with endpoint or organization conditions.

Strong answers often combine these layers. For example, a private S3 access pattern may use a gateway endpoint, route table entry, bucket policy, IAM policy, and logging.

Inspection architecture pitfalls

Pitfall Why it is weak
Deploying a firewall without route-table changes The firewall cannot inspect traffic that does not traverse it.
Centralizing every flow through one inspection path It may create cost, latency, availability, and blast-radius problems.
Using WAF for non-HTTP network flows WAF is not a general-purpose network firewall.
Assuming VPC peering supports transitive inspection Peering is not transitive; hub inspection needs TGW or another supported pattern.
Applying NACLs as fine-grained identity controls NACLs are subnet and IP/port based, not identity-aware workload policy.
Forgetting return path symmetry Stateful inspection appliances often require symmetric routing or appliance-aware designs.

If the prompt includes “centralized inspection,” look for Transit Gateway route tables, Gateway Load Balancer, Network Firewall, route propagation control, and return-path symmetry.

Compliance and automated alerting

Task 4.1 includes compliance testing and automated incident reporting or alerting. The exam usually wants security controls to produce evidence and response, not just enforcement.

Need Useful AWS pattern
Prove that firewall rules are present AWS Config rules, Firewall Manager policy status, and change records.
Detect unexpected traffic VPC Flow Logs, Network Firewall logs, load balancer logs, WAF logs, CloudWatch metrics, and alarms.
Aggregate findings Security Hub and delegated administrator patterns.
Trigger operational response EventBridge rules, SNS notifications, ticketing or incident tooling integration, and runbooks.
Preserve audit trail CloudTrail, centralized logging accounts, S3 retention controls, and least-privilege log access.

Do not over-index on the monitoring service in this page. The architectural point is that security controls need observable outputs and a defined response path.

Common exam traps

Stem clue Weak answer Stronger answer
“SQL injection on public web app” Network ACL only WAF at CloudFront, ALB, API Gateway, or another supported HTTP entry point.
“east-west inspection between VPCs” WAF Network Firewall, GWLB appliance, or TGW-routed inspection path.
“workloads should access S3 privately” NAT gateway only S3 gateway endpoint plus IAM/resource policy controls.
“central governance across many accounts” Manual firewall rules in each account Firewall Manager and Organizations/delegated admin.
“untrusted partner network” Flat peering with broad routes Segmented ingress, explicit routes, security groups, endpoint policies, and logging.
“firewall deployed but no traffic is inspected” Add another firewall Fix routing and return-path symmetry.

Sample exam question

A company has many workload VPCs connected to a Transit Gateway. Security requires all outbound internet traffic from the workload VPCs to pass through a centrally managed inspection layer before reaching NAT gateways. The current design deploys firewall appliances in an inspection VPC, but some workload traffic still exits directly through local NAT gateways. Which change most directly addresses the architecture problem?

  • Attach AWS WAF to the workload subnets.
  • Update Transit Gateway route tables and VPC subnet route tables so outbound traffic is steered through the inspection VPC before internet egress.
  • Replace all security groups with stateless network ACLs.
  • Create a public hosted zone for every workload VPC.

Answer: Update the Transit Gateway and VPC route tables so traffic is actually steered through the inspection VPC.

Why: The problem is not the absence of a named firewall service; the problem is traffic bypassing the inspection boundary. Centralized inspection only works when route tables force the intended flows through the inspection path and the return path is compatible with the inspection design.

Fast decision rule

For ANS-C01 security architecture, identify flow direction, trust boundary, enforcement layer, and routing path before choosing a service. WAF protects HTTP(S) application entry points, Shield supports DDoS resilience, Network Firewall and GWLB appliance patterns inspect routed flows, security groups protect workload boundaries, NACLs provide stateless subnet guardrails, and endpoint policies restrict private AWS service access.

Quiz

Loading quiz…

Continue with 4.2 Security Validation, Monitoring, and Audit to connect these controls to evidence, logging, and compliance validation.

Revised on Monday, June 15, 2026