AWS Solutions Architect flashcards, generated for you.

Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization. (Note: The framework has five pillars, not three—this is commonly tested.)

For production databases requiring high availability and automatic failover. RDS Multi-AZ synchronously replicates data to a standby instance in a different AZ and automatically fails over if the primary fails.

S3 Standard offers consistent performance for frequent access. S3 Intelligent-Tiering automatically moves objects between frequent and infrequent access tiers based on usage patterns, optimizing cost without retrieval fees.

Auto Scaling Groups automatically launch or terminate EC2 instances based on defined scaling policies and CloudWatch metrics (CPU, memory, custom metrics) to maintain desired capacity and meet demand while minimizing cost.

CloudFront is a global content delivery network (CDN) that caches and distributes content from edge locations worldwide, reducing latency and improving performance for end users accessing static and dynamic content.

Two or more Availability Zones. Distributing resources across multiple AZs protects against single-AZ failures and ensures high availability and disaster recovery capabilities.

IAM uses policies that grant only the minimum permissions necessary for users, groups, and roles to perform their job functions. Permissions are explicitly denied by default unless granted, following deny-by-default security model.

EBS snapshots are point-in-time copies of individual volumes stored in S3. AWS Backup provides centralized, policy-based backup for multiple services (EC2, RDS, DynamoDB, EFS) with compliance and lifecycle management across AWS resources.

Use load balancing (ELB/ALB) across multiple AZs, Auto Scaling Groups for compute, caching layers (ElastiCache), CDN (CloudFront), and right-sized instance types with reserved capacity for baseline and on-demand for spikes. Separate stateless and stateful components.

Use asynchronous messaging with Amazon SQS (queues) or Amazon SNS (publish-subscribe) to decouple producers and consumers, allowing independent scaling and improving system resilience through asynchronous communication.