Zero-Trust Network Architecture
The traditional castle-and-moat security model โ trusting everything inside the VPC and blocking everything outside โ fails catastrophically when an attacker gains initial access to any internal resource. Zero-trust architecture eliminates implicit trust by requiring authentication and authorization for every request, regardless of network location. In this challenge, you will design a zero-trust network architecture on AWS that secures a microservices application with multiple teams and varying sensitivity levels. The network layer uses VPC with private subnets only โ no public subnets at all. All inbound traffic enters through AWS PrivateLink endpoints or API Gateway with mutual TLS (mTLS). Service-to-service communication uses AWS App Mesh (Envoy proxy) with mTLS between all services, where certificates are managed by AWS Certificate Manager Private CA with automatic rotation. Each service runs with a unique IAM role scoped to exactly the AWS resources it needs โ no shared roles, no wildcard permissions. The authorization layer implements attribute-based access control (ABAC) using IAM policy conditions that check resource tags, request context, and service identity. Network micro-segmentation uses security groups as identity-based firewalls: each service has its own security group, and rules explicitly whitelist only the specific services that need to communicate, with flow logs capturing every denied connection for anomaly detection. Secrets never appear in environment variables or config files โ all secrets live in Secrets Manager with automatic rotation, and services retrieve them at runtime via the Secrets Manager API with IAM-enforced access. The logging and monitoring layer uses VPC Flow Logs, CloudTrail, and GuardDuty to detect anomalous behavior patterns: unusual API calls, network scanning, or credential usage from unexpected locations. AWS Config rules continuously validate that all resources comply with zero-trust policies, automatically remediating drift. This challenge teaches zero-trust architecture principles, network micro-segmentation, and the AWS services that enable identity-based security at scale.
AWS Services You'll Use
Challenge Details
- Path
- Security & Resilience
- Difficulty
- Advanced
- Duration
- 70 min
- Plan
- Pro
Architecture Patterns You'll Learn
Why This Challenge?
Unlike whiteboard exercises or multiple-choice quizzes, this challenge requires you to design a real architecture with actual AWS services, evaluate trade-offs, and defend your decisions. Our automated validators check your design against production-grade criteria. Complete it and it shows up in your verified portfolio with your architecture diagram and design rationale.
More from Security & Resilience
Cascading Failure Prevention
Design resilience patterns that prevent a single service failure from cascading across your entire system.
Advanced ยท 75 minSecrets Management Pipeline
Design an enterprise secrets management system with automatic rotation, zero-knowledge access, and audit trails.
Advanced ยท 65 minCompliance Automation Engine
Design an automated compliance system that continuously validates, remediates, and reports on cloud governance.
Advanced ยท 70 minReady to design this for real?
Get the full scenario, design your architecture using real AWS services, and validate against production-grade criteria. Your completed challenge shows up in your verified portfolio.
Start Challenge