12.3 Network Protection & Edge Security Auditing
Key Takeaways
Amazon Route 53 Resolver DNS Firewall inspects and filters outbound DNS queries from within VPCs, utilizing allowlists, blocklists, and AWS Managed Domain Lists to block botnet C2 domains and DNS exfiltration.
AWS WAF operates at Layer 7 on ALBs, API Gateway, CloudFront, and AppSync, leveraging AWS Managed Rules and custom rate-based rules to mitigate application attacks and brute-force DDoS.
AWS Shield Standard provides automatic, free Layer 3/4 DDoS protection for all AWS customers; AWS Shield Advanced adds 24/7 Shield Response Team (SRT) access, financial DDoS Cost Protection, and automated Layer 7 mitigation.
AWS Network Firewall provides stateful and stateless deep packet inspection at VPC boundaries, supporting Suricata IPS rules, 5-tuple filtering, and domain SNI/Host header filtering.
Network cost optimization requires deploying local-AZ NAT Gateways to avoid $0.01/GB inter-AZ transfer fees, while implementing free Gateway Endpoints for S3 and DynamoDB completely eliminates the $0.045/GB NAT data processing charge.
12.3 Network Protection & Edge Security Auditing
CloudOps Blueprint Focus: The AWS Certified CloudOps Engineer – Associate (SOA-C03) exam tests network security auditing and cost optimization. You must master Route 53 Resolver DNS Firewall, AWS WAF, AWS Shield Standard and Advanced, AWS Network Firewall, and proven cost-reduction strategies including Gateway Endpoints.
Multi-Layer Network Defense Architecture
Comprehensive cloud security requires layered defense across the OSI model: from DNS resolution (Layer 7 DNS), through edge and application filtering (Layer 7 HTTP/HTTPS), to VPC boundary packet inspection (Layer 3/4 network/transport, Layer 7 deep packet inspection).
| Service | Layer | Target Resources | Primary Protection Scope |
|---|---|---|---|
| Route 53 DNS Firewall | Layer 7 (DNS) | Amazon VPC | Outbound DNS query filtering; blocks botnet C2 and DNS tunneling. |
| AWS WAF | Layer 7 (HTTP/S) | ALB, API Gateway, CloudFront, AppSync | Web application attack mitigation (SQLi, XSS); rate-based anti-DDoS. |
| AWS Shield Standard | Layer 3 & 4 | All AWS customers (Free) | Automatic protection against SYN floods, UDP reflection, and ACK floods. |
| AWS Shield Advanced | Layer 3, 4 & 7 | CloudFront, ALB, NLB, Route 53, Global Accelerator | 24/7 Shield Response Team (SRT), DDoS Cost Protection, auto-WAF rules. |
| AWS Network Firewall | Layer 3 to 7 | Dedicated Firewall Subnets | Stateful and stateless deep packet inspection; Suricata IPS rules; SNI filtering. |
Amazon Route 53 Resolver DNS Firewall
Adversaries often bypass IP-based security groups using Domain Generation Algorithms (DGAs) and DNS tunneling for data exfiltration. Route 53 Resolver DNS Firewall provides domain-level filtering for all outbound DNS queries originating within a VPC.
Domain Lists & Rule Actions
DNS Firewall evaluates queries against Domain Lists:
- Allowlists: Enforce zero-trust egress by permitting DNS queries only to pre-approved domains (e.g.,
*.example.com,*.amazonaws.com), blocking all others. - Blocklists: Explicitly block queries to known malicious domains.
- AWS Managed Domain Lists: Curated threat intelligence lists maintained by AWS, including Malware Domains and Botnet Command-and-Control (C2) Domains.
Matching queries trigger one of three actions: ALLOW (resolves normally), BLOCK (halts resolution, returning NODATA, NXDOMAIN, or OVERRIDE to a sinkhole IP), or ALERT (permits resolution while generating an audit log entry).
Route 53 Resolver Query Logging
Enabling Route 53 Resolver Query Logging records the querying instance IP, domain name, query type, timestamp, and firewall action. Logs stream natively to Amazon CloudWatch Logs, Amazon S3, or Amazon Kinesis Data Firehose for centralized auditing.
AWS WAF & AWS Shield: Application & DDoS Protection
AWS WAF (Web Application Firewall)
AWS WAF inspects HTTP/HTTPS requests on Application Load Balancers, API Gateway, CloudFront, and AppSync using Web ACLs containing:
- AWS Managed Rules (AMR): Maintained by AWS Threat Research, including the Common Rule Set (CRS) (OWASP Top 10), SQL Database Rule Set (SQLi), and Known Bad Inputs Rule Set.
- Custom Rate-Based Rules: Track requests per client IP across a 5-minute sliding window. Exceeding the threshold (e.g., 2,000 requests in 5 minutes) triggers an automatic block, mitigating Layer 7 DDoS and brute-force attacks.
- IP & Geo-Match Sets: Filter traffic based on source CIDR ranges or geographic countries.
- Actions: Rules can
ALLOW,BLOCK(returning HTTP 403 or 429),COUNT,CAPTCHA, orCHALLENGE.
AWS Shield: Standard vs. Advanced
Every AWS customer receives AWS Shield Standard automatically at no charge, defending against common Layer 3 and Layer 4 volumetric attacks (SYN floods, UDP reflection).
For mission-critical environments, AWS Shield Advanced ($3,000/month base fee plus data usage) provides:
- 24/7 Shield Response Team (SRT): Direct access to AWS DDoS engineers who write custom mitigation rules during active attacks.
- DDoS Cost Protection: Reimburses scaling cost spikes (EC2 Auto Scaling or CloudFront egress) caused by verified DDoS attacks.
- Automatic Layer 7 Mitigation: Automatically generates and tunes WAF rate-limiting rules based on attack traffic signatures.
- Proactive Engagement: Integrates Route 53 health checks to initiate direct outreach from the SRT when application health degrades during an attack.
AWS Network Firewall: Perimeter Deep Packet Inspection
AWS Network Firewall delivers managed, stateful network inspection at VPC boundaries. Deployed in dedicated firewall subnets in each AZ, it intercepts traffic at the Internet Gateway via VPC Ingress Routing, NAT Gateways, or Transit Gateways using a dual-engine architecture:
- Stateless Rule Engine: Evaluates packets individually using 5-tuple matching (source IP/port, destination IP/port, protocol) in strict numerical priority order, executing Drop, Pass, or Forward to the stateful engine.
- Stateful Rule Engine: Tracks connection state, supporting 5-tuple rules, Domain Name Filtering (inspecting TLS Server Name Indication [SNI] and HTTP
Hostheaders to enforce domain allowlists), and open-source Suricata-compatible IPS rules for deep packet payload inspection.
Network Architecture Cost Optimization
Network data transfer is a major operational expense. CloudOps engineers must audit and eliminate architectural cost drivers:
| Data Transfer Flow | Pricing Rate | Optimization Strategy |
|---|---|---|
| Intra-AZ (Same AZ, Same VPC) | Free ($0.00 / GB) | Co-locate high-bandwidth workloads in the same AZ. |
| Inter-AZ Data Transfer | $0.01 / GB in + $0.01 / GB out ($0.02 / GB round trip) | Route private subnets to local-AZ NAT Gateways; use AZ-aware client routing. |
| NAT Gateway Data Processing | $0.045 / GB (+ $0.045/hr base) | Deploy Gateway VPC Endpoints for S3/DynamoDB to bypass NAT completely. |
| Cross-Region Data Transfer | $0.02 / GB (varies by Region) | Compress payloads; leverage Amazon CloudFront for caching. |
| Internet Data Egress | $0.09 / GB (first 10 TB/month) | Offload public assets to CloudFront (lower tier pricing and free origin egress). |
Eliminating NAT Gateway Data Processing Fees
Routing heavy Amazon S3 backup or data lake traffic through a NAT Gateway incurs a $0.045/GB data processing charge ($4,500 per 100 TB). Deploying a Gateway VPC Endpoint for Amazon S3 (which is 100% free) directs S3 traffic directly over the AWS private network, completely bypassing the NAT Gateway and dropping data processing fees to $0.00.
An e-commerce enterprise hosts a multi-tier retail platform on Amazon EC2 instances behind Application Load Balancers, with static media cached through Amazon CloudFront. During a major promotional sales event, the platform is targeted by an organized, sophisticated multi-vector distributed denial-of-service (DDoS) attack. The attack combines a massive Layer 4 UDP reflection flood with a Layer 7 HTTP flood designed to exhaust backend database connection pools. The chief information security officer requires a comprehensive DDoS protection solution that provides: (1) 24/7 direct access to dedicated AWS DDoS specialists who can write mitigation rules during the attack, (2) financial protection against unexpected cost spikes resulting from EC2 auto-scaling during the attack, and (3) automatic mitigation of Layer 7 attacks. Which AWS service fulfills all requirements?
Deploy AWS WAF with default AWS Managed Rules on the Application Load Balancer and rely on the automatic protections of AWS Shield Standard.
Configure AWS Network Firewall in dedicated firewall subnets with Suricata IPS rules and request manual service credits from AWS Billing after the incident.
Deploy Amazon CloudFront with Origin Shield enabled and configure Amazon Route 53 latency-based routing across multiple AWS Regions.
Subscribe to AWS Shield Advanced, associate protected Application Load Balancers and CloudFront distributions, configure 24/7 Shield Response Team (SRT) proactive engagement and IAM permissions, and enable Automatic Application Layer DDoS Mitigation.
A security audit of an enterprise VPC hosting production microservices reveals that compromised EC2 instances could theoretically exfiltrate corporate data by sending sensitive payloads encoded inside DNS queries to malicious external nameservers (DNS tunneling) or communicate with command-and-control (C2) servers via domain names generated by algorithms. The security team mandates that outbound DNS queries originating from within the VPC must be inspected and restricted to approved domain names, known botnet C2 domains must be blocked automatically, and all DNS activity must be logged centrally. Which AWS architecture fulfills this requirement with minimal operational overhead?
Attach an AWS WAF Web ACL to the VPC Internet Gateway with an SQL injection inspection rule and stream WAF logs to Amazon S3.
Deploy Amazon Route 53 Resolver DNS Firewall, associate firewall rule groups containing the AWS Managed Domain Lists for Malware and Botnet C2 with the VPC, configure a domain blocklist, and enable Route 53 Resolver query logging to Amazon CloudWatch Logs.
Create an outbound Network Access Control List (NACL) on all VPC subnets that denies UDP port 53 traffic to the default VPC router.
Deploy an Amazon GuardDuty malware protection agent on all EC2 instances to terminate processes communicating over port 53.
A CloudOps engineer conducts a quarterly cost audit and discovers that a financial data pipeline VPC incurs over $3,500 per month in AWS NAT Gateway charges. Investigation reveals that backend analytics instances in private subnets transfer 80 terabytes of daily compressed transaction logs to an Amazon S3 bucket within the same AWS Region. The network route table in the private subnets currently directs default traffic (0.0.0.0/0) to an AZ-local NAT Gateway, which processes all S3-bound traffic. How can the engineer eliminate these NAT Gateway data processing charges while maintaining secure, private connectivity to Amazon S3?
Deploy an AWS Transit Gateway and route all Amazon S3 traffic across a private Direct Connect connection to an on-premises proxy.
Replace the NAT Gateway with an Auto Scaling group of t4g.nano EC2 NAT instances running iptables masquerade rules.
Create a Gateway VPC Endpoint for Amazon S3 at no additional cost, associate it with the private subnet route tables to direct S3 prefix list traffic directly to the endpoint, and allow S3 traffic to bypass the NAT Gateway entirely.
Provision an Interface VPC Endpoint (AWS PrivateLink) for Amazon S3 in each private subnet and enable cross-Region replication to compress log files.
Sections you finish are checked off in the contents.