SERVICE DOMAIN
Architecture
Architecture patterns, best practices, and design decisions.PUBLIC NOTES
Knowledge Notes
AWS Well-Architected Framework
Uses six pillars to evaluate and improve cloud architectures.
→Serverless Architecture
Uses managed, on-demand services to reduce server management while retaining application-level security and reliability duties.
→Specialized Solutions Overview
Choose by the real object involved: APIs, business communications, end-user computing, or IoT.
→Amazon Connect
Build an on-demand cloud contact center for voice, chat, IVR, queues, agents, and callbacks.
→Amazon SES
Send transactional, notification, and marketing email from applications through an API or SMTP.
→Amazon WorkSpaces Applications
Stream desktop applications from AWS without providing users an entire virtual desktop.
→Amazon WorkSpaces Secure Browser
Enter an AWS-managed isolated browser session from an existing local browser.
→Amazon WorkSpaces
Provide users with a complete managed Windows or Linux cloud desktop.
→AWS Amplify
A full-stack development, continuous-deployment, and hosting platform for web and mobile teams.
→AWS AppSync
Managed GraphQL APIs, resolvers, multiple data sources, and real-time subscriptions.
→AWS Cloud Adoption Framework
Guides cloud adoption from business, people, governance, platform, security, and operations perspectives.
→AWS IoT Core
Securely connect large fleets of physical devices to AWS for telemetry and cloud-to-device commands.
→Cost Optimization
Continuously matches resource size, capacity, and pricing model while preserving reliability, security, and performance goals.
→AWS Shared Responsibility Model
AWS secures the cloud infrastructure, while customers secure their configurations, identities, applications, and data in the cloud.
→Data Analytics & ML Pipeline
Send ongoing DynamoDB changes into an S3 data lake so the same history supports Athena analytics and SageMaker training.
→Disaster Recovery Strategies
Select backup and restore, pilot light, warm standby, or multi-site active/active according to RTO, RPO, cost, and complexity.
→High Availability and Fault Tolerance
High availability reduces downtime through redundancy and recovery, while fault tolerance continues operation with minimal interruption.
→Multi-Account Architecture
Separates accounts by environment, team, or risk boundary while keeping governance centralized.
→Decoupling & Event-Driven Architecture
Uses queues, events, and stable contracts to separate upstream and downstream speed, failure, and scaling boundaries.
→Scalability & Elasticity
Separates the ability to handle growth from the ability to automatically match resources to actual demand.
→TOPIC INDEX