AWS Architecture

Cloud architecture on AWS is the practice of combining services and design principles to build systems that are secure, resilient, efficient, and cost‑effective. It is not enough to know what each service does; you must understand how they interact, how to design for failure, and how to make trade‑offs that balance competing priorities.

This section organises AWS architectural knowledge into a set of interconnected topics. It covers the frameworks that guide design, the patterns that solve common problems, and the operational practices that keep systems healthy in production. Use this hub to explore architecture by domain and to build the design intuition that distinguishes experienced cloud engineers.

Architecture Learning Path

Architecture sits between concepts and operations. It transforms a mental model of the platform into concrete designs that can be built, tested, and evolved.

Cloud Foundations

↓

AWS Concepts

↓

AWS Services

↓

AWS Architecture (this section)

↓

AWS Best Practices

By studying architecture after services, you shift from “what can I use?” to “how should I put these pieces together?” That shift is what turns a list of resources into a production‑ready system.

AWS Well-Architected Framework

The Well‑Architected Framework is AWS’s structured approach for evaluating and improving cloud workloads. It is organised around six pillars that together define a sound architecture.

• Operational Excellence – Running and monitoring systems to deliver business value while continuously improving processes and procedures.
• Security – Protecting data, systems, and assets while delivering business value through risk assessments and mitigation strategies.
• Reliability – Ensuring a workload performs its intended function correctly and consistently when it is expected to, including the ability to recover from failures.
• Performance Efficiency – Using computing resources efficiently to meet system requirements and maintaining that efficiency as demand changes and technologies evolve.
• Cost Optimization – Avoiding unnecessary costs by understanding and controlling where money is being spent, and selecting the most appropriate and right‑sized resources.
• Sustainability – Minimising the environmental impact of cloud workloads through efficient resource usage and a shared responsibility model.

Availability & Resilience

Resilience is the ability of a system to withstand and recover from failures. These topics cover how to design applications that remain available when components fail.

• High Availability – Designing systems that stay operational through component failures by using redundancy and automatic failover.
• Fault Tolerance – Ensuring zero service interruption even when individual components fail, typically through replicated synchronous operations.
• Disaster Recovery – Strategies and patterns for restoring service after a large‑scale, region‑wide outage.
• Backup Strategy – Policies and mechanisms for creating point‑in‑time copies of data to support recovery and compliance.
• Multi‑AZ Design – Placing resources across multiple Availability Zones within a region to protect against data‑centre failures.
• Multi‑Region Design – Extending an architecture across multiple geographic regions for global resilience and low‑latency user access.
• Active‑Active Architecture – Running workloads in multiple regions simultaneously, with each region actively serving traffic.
• Active‑Passive Architecture – Running workloads in a primary region while keeping a standby in a secondary region ready to fail over.
• Business Continuity – The broader organisational capability to maintain essential functions during and after a disruption.

Scalability & Performance

Scalability ensures your system can handle growth in users, data, or transactions. These topics address how to design for variable demand and maintain performance under load.

• Horizontal Scaling – Adding more instances or nodes to a system to distribute load, often preferred for cloud‑native designs.
• Vertical Scaling – Increasing the capacity of a single instance, suitable for workloads that cannot easily be distributed.
• Auto Scaling – Dynamically adjusting the number of running instances based on demand, reducing cost while maintaining performance.
• Elastic Architecture – Designing systems that can rapidly provision and release resources in response to fluctuating demand.
• Load Balancing – Distributing incoming traffic across multiple targets to improve responsiveness and availability.
• Stateless Design – Architecting applications so that individual instances do not hold session state, making horizontal scaling straightforward.
• Performance Optimization – Tuning compute, storage, and networking to reduce latency and increase throughput.
• Caching Strategy – Using in‑memory stores and content delivery networks to serve repeated requests faster and reduce origin load.

Cloud-Native Architecture

Cloud‑native architecture embraces the capabilities of the cloud to build flexible, loosely coupled, and resilient systems.

• Microservices – Decomposing applications into small, independently deployable services that communicate over well‑defined APIs.
• Event‑Driven Architecture – Building systems that react to events in real time, enabling loose coupling and responsiveness.
• Serverless Architecture – Designing applications that use fully managed compute and integration services, eliminating server management.
• Container Architecture – Packaging applications with their dependencies for consistency across environments and efficient orchestration.
• Kubernetes Architecture – Deploying and managing containerised workloads at scale using industry‑standard orchestration patterns.
• API‑First Design – Treating APIs as the primary interface to services, enabling platform thinking and external consumption.
• Domain‑Driven Design – Aligning system boundaries with business domains to create maintainable, evolvable architectures.

Security Architecture

Security architecture embeds protection into every layer of the system, from identity to data.

• Zero Trust – A model where no user or system is inherently trusted; every access request is verified.
• IAM Strategy – Designing role structures, permission boundaries, and access policies that balance least privilege with operational agility.
• Network Segmentation – Isolating resources into subnets and security groups to contain potential breaches.
• Encryption – Protecting data at rest and in transit using managed key services and secure protocols.
• Secrets Management – Storing and rotating credentials, API keys, and certificates securely.
• Defense in Depth – Applying multiple, overlapping security controls so that the failure of one does not compromise the system.
• Identity Federation – Extending existing identity providers into AWS so that users access resources with a single set of credentials.
• Security Monitoring – Continuously collecting and analysing logs and events to detect and respond to threats.

Landing Zone & Governance

A landing zone provides the multi‑account foundation for security, compliance, and operational excellence at scale.

• AWS Control Tower – A managed service that automates the setup of a well‑architected, multi‑account environment with pre‑configured guardrails.
• Landing Zone – A custom‑built foundation that includes account structure, networking, identity, logging, and security baselines.
• Multi‑Account Strategy – Organising workloads into separate AWS accounts based on environment, team, or business unit to improve isolation and billing.
• Organizational Units – Grouping accounts to apply policies and manage access at scale.
• SCP – Service Control Policies that set permission boundaries at the organisation or OU level.
• Governance at Scale – Applying consistent policies, controls, and automation across a growing number of accounts and resources.
• Resource Tagging – Attaching metadata to resources to support cost allocation, automation, and compliance tracking.

Hybrid & Multi-Cloud

These topics address architectures that span cloud and on‑premises environments or multiple cloud providers.

• Hybrid Cloud – Integrating on‑premises data centres with AWS through networking, identity, and management tools.
• AWS Outposts – Fully managed racks of AWS hardware in customer data centres, extending the AWS operating model on‑premises.
• Direct Connect – A dedicated, private network connection between an on‑premises facility and AWS.
• Multi‑Cloud Strategy – Designing systems that use services from multiple cloud providers to meet specific requirements.
• Edge Computing – Placing compute and storage resources closer to users to reduce latency for real‑time applications.
• Global Infrastructure Design – Architecting for worldwide user bases by selecting regions, managing data residency, and optimising traffic routing.

Reference Architectures

Reference architectures are proven designs for common workload types. They serve as starting points that can be adapted to specific requirements.

• Three‑Tier Web Architecture – A classic pattern with presentation, application, and data tiers running in a VPC.
• Highly Available Web Application – A web application distributed across multiple Availability Zones with auto scaling and load balancing.
• Serverless Web Application – A fully serverless design using Lambda, API Gateway, DynamoDB, and S3 for hosting.
• Microservices Architecture – A collection of independently deployable services connected via messaging or API calls.
• Data Analytics Platform – A pipeline for ingesting, processing, and querying large datasets with services like Kinesis, Glue, and Athena.
• AI Application Architecture – Patterns for integrating machine learning models into production applications.
• Kubernetes Platform – A managed container orchestration environment built on Amazon EKS.
• Disaster Recovery Architecture – Designs that meet specific RPO and RTO targets with backup, pilot light, warm standby, or active‑active strategies.

Recommended Learning Path

1. Learn Cloud Foundations.
2. Understand AWS Concepts.
3. Learn Core AWS Services.
4. Study AWS Architecture Patterns (this section).
5. Apply AWS Best Practices.
6. Design Production Systems.

Continue Learning

• AWS Concepts – The foundational platform ideas that underpin every architecture decision.
• AWS Services – The building blocks you will arrange and connect when designing systems.
• AWS Best Practices – Operational guidance for running what you architect.
• Cloud Foundations – The vendor‑neutral principles that provide a universal design vocabulary.