Cloud Architect

Overview

About Cloud Architect

A cloud architect designs the systems that run on someone else's data centres: choosing the right services, wiring them together securely, and making sure the result is resilient, affordable, and easy to change. This course follows the order most architects learn it, starting with Cloud Fundamentals (service models, regions, and the shared responsibility model) and Cloud Networking (VPCs, subnets, DNS, CDNs, and load balancers).

Next come the building blocks. Compute & Containers covers virtual machines, autoscaling, serverless, Docker, and Kubernetes, while Storage & Databases covers object, block, and file storage alongside managed relational and NoSQL databases. Identity & Security then covers IAM, encryption, key management, and compliance.

Infrastructure as Code covers Terraform, CloudFormation, and GitOps, and CI/CD & DevOps Automation covers pipelines that build, test, and deploy infrastructure and applications automatically.

Finally, Resilience & Disaster Recovery covers high availability, backups, and failover, Observability & FinOps covers monitoring and cost control, and Architecture Patterns & Migration covers the Well-Architected frameworks, event-driven and microservice designs, landing zones, and multi-cloud strategy: the skills that turn a collection of services into a platform a business can depend on.

Content

10 modules
01

Cloud Fundamentals

IaaS, PaaS, and SaaS, regions and availability zones, the shared responsibility model, and how to choose between AWS, Azure, and Google Cloud.

AWSAzureGoogle Cloud
02

Cloud Networking

Designing VPCs and subnets, routing, DNS, CDNs, load balancers, and private connectivity between clouds and on-premises networks.

VPCLoad BalancersVPN
03

Compute & Containers

Virtual machines and autoscaling, serverless functions, and running containerized workloads with Docker and Kubernetes.

EC2ServerlessKubernetes
04

Storage & Databases

Choosing between object, block, and file storage, and between managed relational, NoSQL, and data warehouse services.

S3RDSDynamoDB
05

Identity & Security

Least-privilege IAM, encryption at rest and in transit, key management, secrets, zero trust, and meeting compliance requirements.

IAMKMSZero Trust
06

Infrastructure as Code

Defining environments in code, managing state and modules, and keeping infrastructure reviewable and repeatable with GitOps.

TerraformCloudFormationPulumi
07

CI/CD & DevOps Automation

Building pipelines that test and deploy applications and infrastructure, with blue/green and canary release strategies.

GitHub ActionsArgoCDBlue/Green
08

Resilience & Disaster Recovery

Designing for high availability across zones and regions, setting RTO and RPO targets, and planning backups and failover.

Multi-AZRTO / RPOFailover
09

Observability & FinOps

Monitoring with metrics, logs, and traces, setting alerts that matter, and controlling spend with tagging, budgets, and right-sizing.

CloudWatchPrometheusCost Optimization
10

Architecture Patterns & Migration

Well-Architected principles, event-driven and microservice designs, landing zones, multi-cloud trade-offs, and migrating legacy workloads.

Well-ArchitectedEvent-DrivenLanding Zones

What You Can Do After This Course

By the end of the curriculum you'll have worked through 5 hands-on projects and covered the core of what a junior to mid-level cloud architect or cloud engineer role expects. Concretely, you'll be able to:

Choose the right cloud services: compare providers and service models, and justify each choice against cost, performance, and risk.

Design secure networks: lay out VPCs, subnets, routing, and load balancing, and connect them to on-premises or other clouds.

Run workloads at scale: pick between VMs, serverless, and containers, and match storage and databases to each workload's access pattern.

Lock down your environment: apply least-privilege IAM, encrypt data, manage secrets and keys, and map controls to compliance needs.

Automate everything: define infrastructure in Terraform or CloudFormation and ship changes through a CI/CD pipeline.

Build for failure: design multi-zone and multi-region systems with clear recovery targets, tested backups, and failover plans.

Operate and optimize: monitor with metrics, logs, and traces, control cloud spend, and plan migrations using proven architecture patterns.