S3 + CloudFront Static Website Architecture
Explains the baseline architecture for delivering a static site placed in S3 quickly and securely through CloudFront.
Architecture
Organize AWS architecture patterns for the SAA exam by services used, design points, and exam perspective. Built to help you understand AWS as architecture, not as a list of services to memorize.
Architectures
10
Exam scope
CLF / SAA
Learning theme
Design
Explains the baseline architecture for delivering a static site placed in S3 quickly and securely through CloudFront.
A foundational serverless API architecture that uses API Gateway as the entry point, executes processing in Lambda, and stores data in DynamoDB. Suited for contact forms and small-scale APIs.
A foundational three-tier web app architecture on AWS that separates the web, application, and database layers across Public Subnets, Private Subnets, and Database Subnets.
Distribute web servers across multiple AZs, balance load with ALB, and improve availability with Auto Scaling and RDS Multi-AZ.
A scheduled batch architecture that triggers Lambda from EventBridge schedules. Serves as the foundation for daily question delivery and periodic aggregation processing.
An architecture that lets resources in a private subnet access AWS services such as Amazon S3 and Amazon DynamoDB without going through the internet, using VPC Endpoints.
Queue requests in Amazon SQS and process them asynchronously with AWS Lambda — an architecture explained for beginners.
Deliver a single event through Amazon SNS to multiple SQS queues and branch into notification, update, and analytics processes.
Run a containerized web application on ECS Fargate and expose it via an Application Load Balancer over HTTPS.
An MVP-friendly operational monitoring architecture that uses CloudWatch Logs and CloudWatch Metrics to observe CloudFront, API Gateway, Lambda, and DynamoDB.
Check whether the design keeps the service running through failures.
Check whether the design reduces single points of failure.
Look at the architecture with fixed costs vs. usage-based pricing in mind.
Check exposure, IAM, network isolation, and encryption.