study guide
AWS Certified Solutions Architect – Professional · SAP-C03 · exam live from Nov 17, 2026

SAP-C03 Study Guide

For the AWS (Amazon Web Services) Certified Solutions Architect – Professional exam. Every task and skill from the current official SAP-C03 exam guide, explained simply, with the design trade-offs the questions test. Pick a domain tab or search any service. Yellow boxes are memory hooks; dashed boxes are exam tips.

No matches. Try a shorter word, a service name, or an acronym.
Start here

How the exam works

Format, scoring, dates, what changed from SAP-C02, and what's in scope.

The exam at a glance

This is a professional-level exam. Questions are long business scenarios with several constraints. Usually two or more answers would work; you must pick the one that meets every constraint best (cheapest, least operational overhead, most resilient, fastest to deliver). You will not write code.

75questions (65 scored + 10 unscored)
180minutes, so about 2.4 minutes per question
720passing scaled score (out of 1,000)
0penalty for guessing, so answer everything
$300USD (50% off if you hold an active AWS cert)
3 yrscertification validity

Question types

TypeWhat you do
Multiple choicePick 1 correct answer out of 4.
Multiple responsePick 2 or more correct answers out of 5 or more. All must be right to get credit.

Scoring is compensatory: you only need to pass the exam overall, not each domain. Unscored questions are not marked, so treat every question as real. Delivered at a Pearson VUE test center or online proctored.

The passing score dropped from 750 (SAP-C02) to 720 (SAP-C03). The question count and time are unchanged. The exam uses short service names; a list of short and full names is under the Help button during the exam.
Read the last sentence first. It holds the real question ("MOST cost-effective", "LEAST operational overhead"). Then read the scenario hunting for the constraints that kill wrong answers.

Key dates: SAP-C02 → SAP-C03

DateWhat happens
October 27, 2026SAP-C03 registration opens (all languages); full exam guide published.
November 16, 2026Last day to take SAP-C02.
November 17, 2026SAP-C03 general availability (GA) delivery begins.
Most practice exams and courses on the market were written for SAP-C02. They still cover a lot of SAP-C03 (networking, DR, migration, cost), but they miss the new AI, post-quantum, DevSecOps and observability skills. Everything marked New in C03 in this guide is new content.

Where the points are

DomainWeightApprox. scored questions
1. Architecture Design and Implementation Built for the Cloud25%~16
2. Security, Compliance, and Governance25%~16
3. Cost-Optimized Architecture Design15%~10
4. Resilience, Migration, and Business Continuity15%~10
5. Operational Excellence and Automation20%~13

Domains 1 and 2 are half the exam. Security is now its own 25% domain, so IAM policy logic, Organizations, KMS and data perimeters matter more than ever.

How SAP-C02 domains map to SAP-C03

SAP-C02 domain%SAP-C03 domain%
1. Design Solutions for Organizational Complexity26%1. Architecture Design and Implementation Built for the Cloud25%
2. Design for New Solutions29%2. Security, Compliance, and Governance25%
3. Continuous Improvement for Existing Solutions25%3. Cost-Optimized Architecture Design15%
4. Accelerate Workload Migration and Modernization20%4. Resilience, Migration, and Business Continuity15%
—5. Operational Excellence and Automation20%

AWS says the reorganization consolidates C02 skills rather than dropping them: domains are now grouped by pillar (security, cost, resilience, operations) instead of by project stage (new vs existing vs migration).

What's new in SAP-C03

AWS's own summary groups the additions into these themes. Each is covered in its domain tab.

ThemeNew skillsWhere
GenAI and agentic AIBedrock integrations (multi-account), AgentCore agents with tools, RAG with Knowledge Bases, SageMaker AI inference, Guardrails, AgentCore Identity, human-oversight approval workflows, AI cost and AI monitoring, Bedrock Evaluations1.2, 2.5, 3.1, 3.2, 5.2, 5.3
Cloud-native patternsServerless data pipelines, durable workflows (Step Functions, Lambda durable functions), service mesh (VPC Lattice, ECS Service Connect), container image security (ECR), ingress patterns, WebSockets, multi-tenant isolation1.1
Data and analyticsLakehouse (Lake Formation, Apache Iceberg, Redshift Spectrum), real-time and batch pipelines (EMR, MSK, AppFlow), cross-account data sharing (Clean Rooms)1.5
Hybrid and networkHybrid compute (Outposts, Local Zones, EKS/ECS Anywhere), IPv6 dual-stack migration1.3, 1.4
IdentityCognito, OAuth 2.0, EKS Pod Identity, IAM Roles Anywhere2.1
Post-quantum cryptographyKMS ML-DSA signing keys; ML-KEM hybrid post-quantum TLS2.2
ComplianceData residency controls, AWS Artifact evidence, threat modeling and risk assessment2.4
Resilience engineeringMulti-cluster container DR, Fault Injection Service, Resilience Hub, ARC, automated runbooks, safe remediation (circuit breakers, bulkheads, backoff)4.2, 4.3, 5.4
DevSecOps and observabilityPipeline vulnerability scanning and signing, cross-account pipelines, Container Insights, Synthetics and RUM, cost-effective observability3.4, 5.2, 5.3

Removed from the blueprint

"Application upgrade path", "Delegating to AWS" and "Migration-tool security". AWS notes these may still be implicit in other skills.

In-scope and out-of-scope services

AWS publishes a list of services that can appear as right answers and a short list that should not. Both are "non-exhaustive". C03 lists parent services only, so features count too (for example Bedrock Guardrails, AgentCore, S3 Object Lock, Route 53 Resolver). In the Services A–Z tab each card shows In scope, Out of scope or Not listed (on neither list; still might appear, but less likely to be the answer).

CategoryIn scope (SAP-C03)
AnalyticsAppFlow, Athena, EMR, Kinesis Data Streams, MSK, OpenSearch Service, QuickSight, Redshift, Clean Rooms, Glue, Lake Formation
Application integrationEventBridge, Amazon MQ, SNS, SQS, Step Functions
Cloud financial managementBudgets, Cost and Usage Report, Cost Categories, Cost Explorer, Reserved Instances, Savings Plans
ComputeEC2, Application Auto Scaling, Elastic Beanstalk, Fargate, Lambda, Local Zones, Outposts
ContainersECR, ECS, EKS
DatabaseAurora, DocumentDB, DynamoDB, ElastiCache, Keyspaces, MemoryDB, Neptune, RDS, Timestream
Developer toolsCDK, CloudFormation, CodeBuild, CodeCommit, CodeDeploy, CodePipeline, AWS Distro for OpenTelemetry, X-Ray
AI / MLAmazon Bedrock, Amazon SageMaker AI
Management & governanceCloudWatch, CloudTrail, Compute Optimizer, Config, Control Tower, Organizations, Resilience Hub, Resource Access Manager, Service Quotas, Systems Manager
Migration & transferAWS Transform MGN (was Application Migration Service), Data Transfer Terminal, DMS, DataSync, SCT, Storage Gateway, Transfer Family, AWS Transform
NetworkingAPI Gateway, CloudFront, Route 53, VPC, VPC Lattice, Cloud WAN, Direct Connect, Global Accelerator, Network Firewall, PrivateLink, Transit Gateway, VPN, Elastic Load Balancing
Security, identity & complianceCognito, GuardDuty, Inspector, Security Lake, Verified Permissions, ACM, CloudHSM, Directory Service, IAM, KMS, Secrets Manager, Security Hub, Shield, Verified Access, WAF
StorageData Lifecycle Manager, EBS, EFS, FSx, S3, AWS Backup, Elastic Disaster Recovery
Testing & resilienceAWS Fault Injection Service

Out of scope, but you may see them as wrong answers

Amazon Managed Blockchain, Lightsail, RDS Custom for Oracle, Device Farm, GameLift, Comprehend Medical, Transcribe Medical, DeepComposer, DeepRacer, Amazon IVS, Elemental MediaConvert and MediaLive, Braket, Ground Station.

Dropped from the C02 list (now "not listed")

All IoT services, WorkSpaces and AppStream 2.0, Elastic Transcoder, Kinesis Video Streams, the individual AI services (Comprehend, Rekognition, Textract and so on), CodeGuru, Lightsail, Pinpoint, SES, Amplify, App Runner, AWS Batch, CodeArtifact, Data Exchange, Device Farm, Health Dashboard, License Manager, Proton, Service Catalog and Wavelength.

If an option is on the out-of-scope list, it's almost certainly a distractor. Cross it off first. If two options look equally good, lean toward the in-scope one.

Services closed to new customers

AWS moved these to maintenance on November 7, 2025 (existing customers only). Old practice questions love them; on a 2026 exam, prefer the current replacement when one exists.

ServicePrefer instead
AWS Snowball Edge (Storage and Compute Optimized)Direct Connect, DataSync over the network, or AWS Data Transfer Terminal (bring your own drives to an AWS facility)
AWS Migration Hub, AWS Application Discovery ServiceAWS Transform (agentic discovery, wave planning, rehost)
AWS Mainframe Modernization serviceAWS Transform for mainframe
Systems Manager Incident Manager and Change ManagerCloudWatch alarms + EventBridge + SSM Automation runbooks; Change Calendar
S3 Object Lambda, Amazon Glacier (the original vault service)Lambda behind S3 access points or API Gateway; S3 Glacier storage classes (still fully available)

Out of scope (don't over-study)

The guide says you are not expected to have: in-depth operating-system knowledge, AI/ML model training, fine-tuning or data-science workflows, security incident forensics or detailed threat investigation, or application code development and debugging. You design and choose; you don't build models or debug code.

The classic answer-killers

Phrase in the questionWhat it rules out
"Least operational overhead" / "fully managed"Anything on EC2 you patch yourself, custom scripts, self-managed Kafka or databases
"Most cost-effective"Over-provisioning, active/active when pilot light meets the RTO, NAT gateway for S3 traffic
"Without changing application code"Refactoring, switching database engines, SDK changes
"Across all accounts" / "for new accounts automatically"Per-account manual setup; prefer Organizations, SCPs/RCPs, StackSets, Control Tower, delegated admin
"As quickly as possible"Long refactors; prefer rehost or replatform
"Overlapping CIDR ranges"VPC peering and Transit Gateway routing; prefer PrivateLink or VPC Lattice (or NAT)
Sources
Domain 1 · tied for largest

Architecture design and implementation built for the cloud

25% of scored content · Tasks 1.1–1.5

1.1Event-driven architectures and messaging

Services talk through messages and events instead of direct calls, so each part can scale and fail on its own. The exam tests which messaging service fits the delivery guarantee, ordering and fan-out needs.

ServicePatternOrdering & deliveryPick it when…
SQS standardQueue (one consumer group pulls)At-least-once, best-effort order, nearly unlimited throughputDecouple and buffer work; duplicates are OK or handled
SQS FIFOQueueStrict order per message group ID; exactly-once processing via deduplication ID (5-minute window)Order matters (bank transactions per account); no duplicates
SNS (standard / FIFO)Pub/sub push to many subscribersStandard: at-least-once; FIFO topics deliver in order to SQS FIFO queuesOne event, many consumers (fan-out: SNS → several SQS queues)
EventBridgeEvent bus with content-based rulesAt-least-once; no orderingRoute events by content to 20+ targets, SaaS events, cross-account / cross-Region buses, schedules, archive & replay
Kinesis Data StreamsStreaming logOrdered per shard (partition key picks the shard); many consumers re-read; retention 24 h up to 365 daysHigh-volume real-time streams, replay, multiple independent readers
Amazon MSKManaged Apache KafkaOrdered per partitionExisting Kafka apps/tools; lift Kafka with no code change
Amazon MQManaged ActiveMQ / RabbitMQ brokerBroker semantics (JMS, AMQP, MQTT, STOMP)Migrating apps that already use a standard broker protocol

Making consumers safe

  • Idempotency: processing the same message twice gives the same result. Store a processed-message ID (for example a DynamoDB conditional write, or Powertools for AWS Lambda idempotency) so retries don't double-charge.
  • Dead-letter queues (DLQs): park messages that keep failing; alarm on DLQ depth; redrive later.
  • Visibility timeout (SQS) must be longer than processing time, or another consumer picks the message up again.
  • Partial batch failure reporting for Lambda + SQS/Kinesis so one bad record doesn't retry the whole batch.
Queue = a to-do list one team works through. Topic = a megaphone. Bus = a mail sorter that reads the envelope. Stream = a tape recorder anyone can rewind.
Try it

Pick the messaging service

Cross-account and cross-Region event routing

EventBridge rules can target an event bus in another account or Region. A common pattern: every workload account forwards security or ops events to a central bus in a monitoring account. The target bus needs a resource-based policy allowing the source (use aws:PrincipalOrgID to allow the whole organization). EventBridge also offers global endpoints for Regional failover of event ingestion.

"Decouple and process in order per customer" → SQS FIFO with customer ID as the message group ID. "Fan out one order event to billing, shipping and analytics" → SNS → SQS (or EventBridge with three rules). "Replay last week's clickstream into a new consumer" → Kinesis Data Streams (or EventBridge archive and replay for events).

1.1Stateless apps, serverless pipelines and durable workflows

Externalize state

A stateless server keeps nothing it can't lose, so any instance can serve any request and Auto Scaling can kill instances freely. Put session data in ElastiCache or DynamoDB (with TTL), files in S3, shared POSIX files in EFS. Avoid sticky sessions as the main design: they pin users to instances that might disappear.

Serverless data pipelines New in C03

Producers→Kinesis Data Streams→Lambda (transform) or Amazon Data Firehose→S3 data lake (Parquet)→Glue crawler / Data Catalog→Athena SQL→QuickSight

No servers anywhere: you pay per GB or per request. Firehose buffers, converts to Parquet and partitions on the way into S3. Athena charges per TB scanned, so columnar formats and partitions cut cost.

Durable multi-step workflows New in C03

OptionMax durationExecution modelPick it for
Step Functions StandardUp to 1 yearExactly-once per step; full visual execution history; priced per state transitionLong-running, auditable business processes; human approvals
Step Functions ExpressUp to 5 minutesAt-least-once; priced per request and durationHigh-volume, short event processing (IoT, streaming transforms)
Lambda durable functionsUp to 1 yearCheckpoint and replay inside your Lambda code: steps, waits (no compute charge while waiting), callbacksDevelopers who want a workflow as ordinary sequential code rather than a state-machine definition
Plain Lambda15 minutesSingle invocationOne short task
Step Functions Standard = a registered letter (slow, tracked, exactly once). Express = bulk mail (fast, cheap, at least once).
Any workflow longer than 15 minutes rules out a single Lambda. Need a person to approve a step → Step Functions with a callback task token (.waitForTaskToken) or a Lambda durable function callback.

1.1Containers, service mesh and image management

OptionWhat it isPick it when…
Amazon ECSAWS-native container orchestration; simplerNo Kubernetes requirement; least operational overhead
Amazon EKSManaged Kubernetes control planeTeam already uses Kubernetes, needs its APIs, Helm, portability, or hybrid with EKS Anywhere
AWS FargateServerless compute for ECS or EKS tasks/podsNo EC2 nodes to patch or scale
EC2 launch type / managed node groups / KarpenterYou run the nodesGPUs, special instance types, daemonsets, maximum cost control with Spot

Service mesh and service-to-service networking New in C03

  • ECS Service Connect: built-in service discovery, load balancing, retries and traffic metrics between ECS services by short name. No sidecar config to manage yourself.
  • Amazon VPC Lattice: an application-layer network that connects services across VPCs and accounts (EC2, ECS, EKS, Lambda) with IAM auth policies, without peering or Transit Gateway, and even with overlapping CIDRs. Share service networks with AWS RAM.
  • AWS App Mesh was retired (end of support September 30, 2026); prefer Service Connect or VPC Lattice.

Container images in ECR New in C03

  • Basic scanning (on push, OS CVEs) vs enhanced scanning (Amazon Inspector: continuous, OS and language packages).
  • Lifecycle policies expire old or untagged images to cut storage cost.
  • Tag immutability stops a tag like v1.4 being overwritten; replication copies images cross-Region / cross-account (needed for DR).
  • Sign images (AWS Signer with Notation) and verify at deploy time.

Auto scaling for serverless and containers

WorkloadScaling control
LambdaReserved concurrency (cap and guarantee a slice), provisioned concurrency (pre-warmed, removes cold starts; can be scheduled with Application Auto Scaling)
ECSService auto scaling (target tracking on CPU, memory or ALB requests per target) via Application Auto Scaling; capacity providers scale the EC2 cluster
EKSHorizontal Pod Autoscaler (more pods), Cluster Autoscaler or Karpenter (more nodes)
DynamoDB, Aurora replicas, SageMaker endpoints, Spot Fleet…AWS Application Auto Scaling (one API for scaling non-EC2 resources)

1.1Ingress, edge and real-time

Entry pointLayerKey traitsPick it when…
Application Load Balancer7 (HTTP/HTTPS, gRPC)Path/host/header routing, Lambda targets, OIDC/Cognito auth, WAFWeb apps and microservices behind one URL
Network Load Balancer4 (TCP/UDP/TLS)Millions of requests/sec, ultra-low latency, static IP per AZ / Elastic IPs, TLS passthrough, fronts PrivateLink servicesNon-HTTP protocols, allow-listing fixed IPs, extreme performance
Gateway Load Balancer3 (GENEVE)Transparently inserts third-party firewalls/IDS appliancesScale a fleet of virtual security appliances
API Gateway (REST / HTTP / WebSocket)7Throttling, usage plans and API keys, request validation, caching (REST), authorizers; HTTP APIs are cheaper and simplerServerless APIs, per-client throttling, monetized APIs, WebSockets
AWS Load Balancer Controller—Kubernetes add-on: Ingress → ALB, Service type LoadBalancer → NLBEKS ingress
Try it

Pick the front door

Edge compute for latency

CloudFront FunctionsLambda@Edge
Runs atEdge locations (viewer request/response only)Regional edge caches (viewer and origin request/response)
Speed / scaleSub-millisecond, millions of requests/sec, cheapestMilliseconds to seconds
Can doHeader rewrites, redirects, URL normalization, cache-key tweaks, simple token checksNetwork calls, bigger code, body access, origin selection
Functions = flip a header. Lambda@Edge = do real work.

Real-time with WebSockets and pub/sub New in C03

API Gateway WebSocket APIs keep a two-way connection open. Store connection IDs in DynamoDB; backends push to clients through the @connections management API. Combine with SNS/EventBridge to publish one event to many connected clients.

1.1Multi-tenant SaaS isolation New in C03

ModelHowTrade-off
SiloEach tenant gets its own resources (account, VPC, database, or stack)Strongest isolation and easy per-tenant cost; most expensive and hardest to operate at scale
PoolTenants share resources; tenant ID in every row and requestCheapest and most efficient; noisy neighbors and isolation must be enforced in code and policy
Bridge (hybrid)Shared app tier, siloed data tier (or premium tenants siloed)Balance; common in practice

Tools for isolation

  • Cognito tenant context: a custom attribute (custom:tenant_id) in the JWT that every service reads.
  • Dynamic IAM with ABAC: assume a role with a tenant session tag; policies allow only resources tagged with the same tenant (DynamoDB dynamodb:LeadingKeys, S3 prefixes).
  • Row-level security (RLS): PostgreSQL policies so queries only see the tenant's rows.
  • Tenant-specific encryption: one KMS key per tenant (crypto-isolation; deleting the key "shreds" that tenant's data).
  • Per-tenant throttling with API Gateway usage plans to stop noisy neighbors.
"Regulated enterprise tenants demand dedicated infrastructure; small tenants must be cheap" → bridge/tiered model: silo the premium tier, pool the rest.

1.2Integrating generative AI and agents New in C03

You're the architect, not the data scientist: know which AWS building block to wire in and how to secure, scale and share it across accounts. Training and fine-tuning are out of scope.

Building blockWhat it doesPick it when…
Amazon BedrockServerless API (InvokeModel, Converse) to foundation models from Amazon and other providersAdd GenAI to an app without managing model servers
Bedrock Knowledge BasesManaged RAG: ingestion, chunking, embeddings, vector store, retrieval with citationsAnswer from company documents; data changes often
Bedrock AgentsManaged agent with action groups (Lambda / OpenAPI) and Knowledge BasesSimple managed agent inside Bedrock
Bedrock AgentCoreRun any agent framework securely at scale: Runtime, Memory, Gateway (APIs/Lambda → MCP tools), Identity, Policy (Cedar), Observability, built-in Browser and Code InterpreterProduction agents, any framework or model, tool access with enterprise identity
SageMaker AI endpointsHost your own or open-weight modelsCustom model, specific instance/GPU control, model not on Bedrock

Multi-account GenAI patterns

  • Central AI platform account exposes models through API Gateway + Lambda (or a gateway on ECS) so workload accounts get one governed endpoint with logging, quotas, guardrails and chargeback.
  • Or let each workload account call Bedrock directly, governed by SCPs (allow only approved model IDs/Regions), mandatory Guardrails (IAM condition bedrock:GuardrailIdentifier), and org-wide model invocation logging.
  • Application inference profiles carry tags per team or app for cost tracking.
  • Cross-Region inference profiles (geographic such as US or EU, or global) spread requests across Regions for throughput and resilience, with no extra routing charge; geographic profiles keep processing inside that geography.
  • Private access: Bedrock interface VPC endpoints (PrivateLink) keep traffic off the internet.

RAG architecture, in order

  1. Ingest documents from S3 (or connectors such as SharePoint, Confluence, web crawler); sync on a schedule or event.
  2. Chunk them (fixed-size, hierarchical, semantic, or none).
  3. Create embeddings with an embeddings model.
  4. Store vectors (OpenSearch Serverless, Aurora PostgreSQL with pgvector, Neptune Analytics, Amazon S3 Vectors, or partner stores).
  5. At query time retrieve the top chunks (optionally hybrid search, metadata filters, reranking).
  6. Send question + chunks to the model; return answer with citations.
Answers must reflect documents updated daily → RAG with Knowledge Bases, not fine-tuning. Already on Aurora PostgreSQL → pgvector with the fewest new services. Different users may see only their documents → metadata filtering at retrieval on a user/department attribute.

ML inference options (SageMaker AI)

TypePick it when…
Real-time endpointSteady traffic, low latency
Serverless inferenceSpiky or idle traffic; scales to zero (cold starts)
Asynchronous inferenceLarge payloads (up to 1 GB), long processing; queue-based; can scale to zero
Batch transformScore a whole dataset offline
Multi-model endpoints / inference componentsMany models sharing one endpoint's instances to cut cost
Bedrock = rent a model by the word. SageMaker endpoint = run your own model's server. AgentCore = the secure office your agents work in.

1.3Hybrid connectivity with redundancy

OptionWhat it isStrengthsLimits
Site-to-Site VPNIPsec over the internet, 2 tunnels per connection, BGP or staticUp in minutes, cheap, encrypted~1.25 Gbps per tunnel; internet variability. Use ECMP over Transit Gateway to aggregate; Accelerated VPN uses Global Accelerator
Direct Connect (DX)Private fiber link to AWS: dedicated 1/10/100/400 Gbps, or hosted from a partner (50 Mbps–25 Gbps)Consistent latency, high bandwidth, lower egress priceWeeks to provision; not encrypted by default (use MACsec on dedicated links or VPN over DX)
DX + VPN backupVPN as failover for DXCheap redundancyBackup bandwidth is lower

Direct Connect building blocks

  • Virtual interfaces (VIFs): private VIF (to one VPC's VGW or a DX gateway), transit VIF (to a DX gateway attached to Transit Gateways), public VIF (AWS public endpoints like S3 over DX).
  • Direct Connect gateway: global object; one DX connection reaches VPCs/TGWs in many Regions and accounts.
  • SiteLink: send traffic between your own sites over the AWS backbone.
  • Resiliency models (DX Resiliency Toolkit): Maximum resiliency = separate connections on separate devices in two or more locations (99.99% SLA); High resiliency = one connection at each of two locations (99.9%); Development and test = two connections on separate devices at one location (no SLA).
DX is a private highway; VPN is a tunnel through public roads. Redundancy = two highways from two different on-ramps.
"Encrypted, 10 Gbps, private" → DX with MACsec (or IPsec VPN over a DX public/transit VIF). "Need connectivity next week while DX is ordered" → VPN now, DX later, keep VPN as backup. Prefer BGP with AS_PATH prepending or local preference to make one path primary.

1.3Hybrid data sync, legacy integration and DNS

ServiceJobPick it when…
AWS DataSyncOnline, scheduled, incremental copy (NFS, SMB, HDFS, object storage, other clouds) ↔ S3, EFS, FSx; verifies dataMove or sync large file sets over the network
Storage Gateway – S3 File GatewayNFS/SMB share on-premises backed by S3, local cacheOn-prem apps keep using a file share; data lands in S3
Storage Gateway – Volume GatewayiSCSI block volumes backed by S3 with EBS snapshots (cached or stored)Block storage backup/DR to AWS
Storage Gateway – Tape GatewayVirtual tape library to S3 GlacierReplace physical tapes with no backup-software change
AWS Transfer FamilyManaged SFTP, FTPS, FTP, AS2 endpoints into S3/EFSPartners already send files by SFTP or AS2

Modernizing legacy integration

Put a facade in front of the old system: API Gateway + Lambda to transform payloads (XML/SOAP ↔ JSON), or Amazon MQ to keep JMS/AMQP producers unchanged while new consumers come online. EventBridge Pipes can filter and enrich between sources and targets.

Hybrid DNS with Route 53 Resolver

DirectionUse
Inbound endpointOn-premises DNS servers forward queries into AWS to resolve private hosted zone names
Outbound endpoint + forwarding rulesVPC resources resolve on-premises names (corp.example.com) by forwarding to on-prem DNS. Share rules with other accounts through AWS RAM.
Private hosted zonesAssociate with many VPCs, including in other accounts (authorize, then associate)
Split-horizon DNSSame name, public zone answers internet users, private zone answers inside the VPC
INbound = queries coming IN to AWS. OUTbound = queries going OUT to your data center.

Hybrid compute New in C03

OptionPick it when…
AWS Outposts (rack or server)AWS-managed infrastructure in your data center: low latency to on-prem systems, local data processing, data residency
AWS Local ZonesAWS-run infrastructure in a metro area for single-digit-millisecond latency to users (media, gaming, real-time)
Amazon EKS AnywhereRun Kubernetes on your own hardware with EKS tooling (you manage the hardware and clusters)
Amazon ECS AnywhereRegister on-prem servers as ECS capacity, managed from the ECS control plane
Try it

Which hybrid option?

Think of your answer, then tap a card to check it.

1.4Multi-VPC and multi-account connectivity

OptionTransitive?Overlapping CIDRs?ScalePick it when…
VPC peeringNoNo1:1, full mesh gets messy past ~10 VPCsFew VPCs, highest bandwidth, no hourly charge
Transit Gateway (TGW)Yes (hub and spoke)NoThousands of attachments; route tables for segmentation; inter-Region peering; VPN and DX attachmentsMany VPCs + on-prem; central inspection; isolated route domains
AWS PrivateLinkN/A (service-level)YesOne service exposed to many consumers; consumer sees an ENI in its own VPCExpose one app/API to other accounts or SaaS customers privately, one direction
Amazon VPC LatticeN/A (service-level)YesService network across VPCs and accounts with IAM auth policiesMany microservices across accounts talking to each other at layer 7
AWS Cloud WANYesNoGlobal network from a central policy; segments; multi-Region automaticallyGlobal multi-Region WAN with central policy, many sites and Regions
Shared VPC (RAM subnet sharing)——Many accounts deploy into one VPC's subnetsCentral network team owns the VPC; app teams own their resources
Try it

Pick the connectivity option

Peering = a private hallway between two rooms. TGW = a central train station. PrivateLink = a service window in the wall: you can buy coffee but can't walk into the kitchen.

VPC design, IPAM and segmentation

  • Amazon VPC IP Address Manager (IPAM): plan, allocate and track CIDRs across accounts and Regions from pools (shared via RAM) so VPCs never overlap; audits usage and compliance.
  • Subnets per AZ in tiers (public for load balancers and NAT, private for apps, isolated for data). Reserve big ranges: a VPC can have extra secondary CIDRs.
  • Segment with separate VPCs/accounts and TGW route tables (prod can't reach dev), not just security groups.

1.4Network security and inspection

ControlLayer / scopeKey traits
Security groupsENI / instanceStateful, allow rules only, can reference other SGs
Network ACLsSubnetStateless (allow return traffic explicitly), allow and deny, rules evaluated in number order
AWS Network FirewallVPC (subnet-level endpoints)Managed stateful firewall + IPS (Suricata rules), domain allow/deny lists, TLS inspection
Gateway Load BalancerVPCBring your own third-party appliances, scaled and highly available
AWS WAFLayer 7 on CloudFront, ALB, API Gateway, AppSync, Cognito, Verified AccessSQL injection, XSS, rate-based rules, bot control, managed rule groups, geo-match
AWS ShieldEdgeStandard: free L3/4 DDoS protection. Advanced: L7 response team, cost protection, health-based detection
Route 53 Resolver DNS FirewallVPC DNSBlock DNS lookups of malicious domains (exfiltration)
VPC Flow LogsVisibilityMetadata of accepted/rejected flows to CloudWatch Logs, S3 or Firehose (not packet contents)

Centralized inspection pattern

Spoke VPCs→Transit Gateway→Inspection VPC (Network Firewall or GWLB endpoints)→Egress VPC (NAT) / other spokes / on-prem

Turn on TGW appliance mode on the inspection VPC attachment so both directions of a flow hit the same AZ's firewall (keeps stateful inspection symmetric). Firewall Manager can push Network Firewall, WAF and security group policies across the organization.

Block outbound traffic to all domains except an approved list → Network Firewall domain allow list (stateful) or DNS Firewall. A security group can't filter by domain name, and NACLs can't either.

1.4IPv6 and global traffic routing

IPv6 and dual-stack migration New in C03

  • Add an Amazon-provided (or BYOIP / IPAM-allocated) IPv6 /56 to the VPC, a /64 to each subnet; run dual-stack first, then IPv6-only subnets for new workloads.
  • All IPv6 addresses are globally unique, so there's no NAT. For private outbound-only IPv6 use an egress-only internet gateway.
  • IPv6-only workloads reach IPv4-only services through DNS64 + NAT64 (Route 53 Resolver + NAT gateway).
  • Update security groups, NACLs and route tables for ::/0; ALB/NLB/CloudFront support dual-stack.
  • Motivation: IPv4 exhaustion inside large organizations, and public IPv4 addresses carry an hourly charge.

Route 53 routing policies

PolicyUse
SimpleOne record, no health checks
FailoverActive-passive DR with health checks
WeightedSplit traffic by percentage (canary, blue/green)
LatencySend users to the Region with lowest latency
GeolocationBy the user's country/continent (content rights, compliance)
GeoproximityBy distance, with a bias to grow or shrink a Region's share
Multivalue answerUp to 8 healthy records, simple client-side load spreading
IP-basedBy the client's IP range (route a known ISP to a specific endpoint)

Global Accelerator vs CloudFront

AWS Global AcceleratorAmazon CloudFront
What2 static anycast IPs; traffic enters the AWS backbone at the nearest edgeCDN that caches content at the edge
ProtocolsTCP and UDP (any app)HTTP/HTTPS (and WebSockets)
FailoverSeconds, no DNS caching problemOrigin failover groups
Pick whenGaming/VoIP/IoT, fixed IPs for allow-lists, fast multi-Region failoverStatic and dynamic web content, cost of egress, edge security
CloudFront keeps copies. Global Accelerator finds the fastest lane and never changes its phone number.

1.5Data lakes, lakehouses and analytics pipelines

Lakehouse on AWS New in C03

  • Amazon S3 stores data in open formats (Parquet) and open table formats like Apache Iceberg (ACID transactions, row-level updates/deletes for GDPR, schema evolution, time travel). S3 Tables are S3 buckets with built-in Iceberg management.
  • AWS Glue Data Catalog holds table definitions; Glue crawlers discover schemas; Glue ETL jobs (Spark) transform.
  • AWS Lake Formation governs access: fine-grained table, column, row and cell permissions, LF-Tags (tag-based access control), and cross-account sharing.
  • Query engines read the same data: Athena (serverless SQL), Redshift Spectrum (warehouse joins with lake data), EMR (Spark, Hive, Presto).

Real-time vs batch pipelines

NeedServices
Streaming ingestionKinesis Data Streams, Amazon MSK (Kafka), Firehose for delivery
Stream processingLambda, Amazon Managed Service for Apache Flink, Spark streaming on EMR/Glue
Batch processingGlue (serverless Spark), EMR (on EC2, EKS or Serverless) for big custom Spark/Hadoop
WarehouseAmazon Redshift (provisioned RA3 or Serverless), zero-ETL integrations from Aurora/RDS/DynamoDB, data sharing between clusters/accounts
SaaS ingestionAmazon AppFlow (Salesforce, SAP, ServiceNow, Slack… → S3/Redshift), no code
Search and log analyticsAmazon OpenSearch Service
DashboardsAmazon QuickSight

Cataloging and cross-account sharing

NeedAnswer
Share catalog tables with another account, with column-level controlLake Formation cross-account grants (uses RAM under the hood)
Share live warehouse data, no copiesRedshift data sharing
Two companies analyze combined data without either seeing the other's raw recordsAWS Clean Rooms (analysis rules, aggregation thresholds, differential privacy) New in C03
"Analysts in many accounts, one governed lake, column-level permissions, least operational overhead" → central Glue Data Catalog + Lake Formation with LF-Tags, not S3 bucket policies per prefix.

1.5Choosing and scaling databases

ServiceModelPick it when…
Amazon RDSManaged relational (MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, Db2)Lift a relational app; commercial engines
Amazon AuroraAWS-built MySQL/PostgreSQL-compatible; storage auto-grows, 6 copies across 3 AZsHigher performance and availability, up to 15 replicas, Global Database, Serverless v2
Amazon DynamoDBServerless key-value / document, single-digit ms at any scaleKnown access patterns, massive scale, serverless apps, global tables
Amazon DocumentDBMongoDB-compatible document databaseExisting MongoDB workloads
Amazon KeyspacesServerless Apache Cassandra–compatibleExisting Cassandra workloads (CQL)
Amazon NeptuneGraph (Gremlin, openCypher, SPARQL)Relationships: fraud rings, social graphs, knowledge graphs
Amazon TimestreamTime-seriesIoT and operational metrics over time
Amazon MemoryDBDurable in-memory (Valkey/Redis OSS compatible), multi-AZ transaction logMicrosecond reads as the primary database (leaderboards, sessions that can't be lost)
Amazon ElastiCacheIn-memory cache (Valkey, Redis OSS, Memcached)Cache in front of a database; session store
Amazon RedshiftColumnar data warehouseAnalytics/BI over large data (OLAP), not transactions

High availability and scaling

FeatureWhat it gives you
RDS Multi-AZ (instance)Synchronous standby in another AZ; automatic failover; standby is not readable
RDS Multi-AZ DB clusterWriter + 2 readable standbys in 3 AZs; faster failover
Read replicasAsynchronous copies for read scaling (also cross-Region; can be promoted for DR)
Aurora replicasUp to 15, share storage, failover targets; reader endpoint load-balances; Aurora Auto Scaling
Aurora Global DatabaseStorage-level replication to up to 10 secondary Regions, typically under 1 second of lag; managed switchover/failover for DR
DynamoDB global tablesMulti-active replicas in many Regions. Default: eventual consistency (last writer wins). Multi-Region strong consistency (MRSC): exactly 3 Regions (or 2 + a witness), zero RPO, higher write latency
RDS ProxyPools connections (Lambda storms), speeds failover
"Read-heavy reporting is slowing the primary" → read replica / Aurora replica (reader endpoint). "Survive an AZ failure" → Multi-AZ. "Survive a Region failure, RPO about a second" → Aurora Global Database. "Writes in several Regions at once" → DynamoDB global tables. Multi-AZ is for availability; replicas are for scale.

1.5Storage architectures and caching

ServiceTypePick it when…
Amazon S3ObjectUnlimited objects, data lakes, static sites, backups; 11 nines durability
Amazon EBSBlock, one AZ, attached to EC2Boot volumes, databases on EC2. gp3 (general), io2 Block Express (highest IOPS, Multi-Attach), st1 (throughput HDD), sc1 (cold HDD)
Amazon EFSShared NFS file system (Linux), multi-AZ, elasticMany Linux instances/containers/Lambdas share files
FSx for Windows File ServerSMB, Active Directory integratedWindows file shares, DFS, user home folders
FSx for LustreHigh-performance parallel file system, links to S3HPC, ML training, media rendering
FSx for NetApp ONTAPNFS + SMB + iSCSI, snapshots, SnapMirrorLift NetApp workloads; multi-protocol
FSx for OpenZFSNFS, ZFS featuresLift ZFS/Linux file workloads with low latency
Try it

Pick the storage

Caching strategies

CacheWhereUse
CloudFrontEdgeStatic and cacheable dynamic content near users
API Gateway cacheAPI (REST)Repeated identical API responses
ElastiCacheApp tierAny database or computed results; sessions
DynamoDB Accelerator (DAX)In front of DynamoDB onlyMicrosecond reads with no code rewrite beyond the DAX client

Lazy loading (cache-aside): read cache, on miss read DB and fill cache; data can be stale, set a TTL. Write-through: update cache on every write; always fresh, more writes.

DAX is a speed boost bolted to DynamoDB. ElastiCache is a general-purpose speed boost you wire into your code yourself.
Sources
Domain 2 · tied for largest

Security, compliance and governance

25% of scored content · Tasks 2.1–2.5

2.1Identity federation for the workforce

Service / standardWhat it does
AWS IAM Identity CenterSingle sign-on for people into many AWS accounts and apps. Connect an external IdP (Okta, Entra ID) by SAML 2.0, sync users and groups automatically by SCIM, grant access with permission sets (become roles in each account). Supports ABAC from IdP attributes.
SAML 2.0XML-based standard for browser SSO between an IdP and a service provider
OpenID Connect (OIDC)Identity layer on OAuth 2.0 using JWTs; used by Cognito, web/mobile logins and CI systems (GitHub Actions → IAM role, no stored keys)
SCIMSystem for Cross-domain Identity Management: automatic user/group provisioning and deprovisioning
IAM SAML / OIDC identity providersFederation directly into one account's roles (older pattern; Identity Center is preferred for many accounts)
AWS Directory ServiceManaged Microsoft AD (real AD in AWS, trusts with on-prem AD), AD Connector (proxy to on-prem AD, no directory in AWS), Simple AD (basic Samba)
"Employees use the corporate IdP; access to 200 accounts; leavers lose access automatically" → IAM Identity Center + SAML 2.0 + SCIM. "Apps in AWS need to join the on-prem domain with no directory replication" → AD Connector; "needs a domain in AWS that survives a link outage" → Managed Microsoft AD with a trust.

2.1Application authentication and workload identities New in C03

NeedAnswer
Sign up / sign in end users of a web or mobile app; social and SAML/OIDC federation; JWTsCognito user pools (authentication; issues ID, access and refresh tokens)
Give app users temporary AWS credentials to call S3/DynamoDB directlyCognito identity pools (trade a token for scoped IAM role credentials; supports guest access)
Fine-grained in-app permissions ("can this user edit this document?")Amazon Verified Permissions (Cedar policy language, central authorization decisions)
Machine-to-machine API callsOAuth 2.0 client credentials grant (Cognito resource server + scopes)
User login in an SPA or mobile appOAuth 2.0 authorization code grant with PKCE
Pods on EKS need AWS permissionsEKS Pod Identity (simplest: associate role with service account; no OIDC provider per cluster) or IRSA (IAM Roles for Service Accounts)
Servers on-premises or in another cloud need AWS credentials without long-term keysIAM Roles Anywhere: X.509 certificate from your CA (or AWS Private CA) registered as a trust anchor → temporary credentials
ECS tasks / Lambda / EC2Task role / execution role / instance profile (never store access keys)
User pools = who are you (login). Identity pools = what AWS keys do you get. Verified Permissions = what may you do inside the app.

2.1Least privilege and IAM policy evaluation

For a request inside one account, AWS checks every policy type. An explicit deny anywhere wins. Otherwise every guardrail layer that applies (SCP, RCP, permissions boundary, session policy) must allow it, and an identity-based or resource-based policy must grant it.

Explicit deny?→SCPs allow?→RCPs allow?→Resource-based policy?→Identity-based policy?→Permissions boundary?→Session policy?
Try it

Will this request be allowed?

A role in account A calls s3:GetObject on a bucket. Set each policy layer, then read the verdict.

SCP on the caller's account
RCP on the bucket's account
Identity policy on the role
Bucket policy (resource-based)
Permissions boundary on the role
Session policy (passed at AssumeRole)

Least-privilege tools

ToolUse
IAM roles + STS temporary credentialsCross-account access: trust policy in the target account, sts:AssumeRole from the source
External IDThird party assumes a role in your account; stops the confused deputy problem
Permissions boundaryMaximum permissions for a role/user; lets developers create roles safely (delegated admin)
Session policyNarrow a session further at AssumeRole time
ABACAllow when aws:PrincipalTag/project equals aws:ResourceTag/project; scales without editing policies for each new project
Session tags / sts:SourceIdentityCarry user attributes and identity through role chains for ABAC and auditing
SCPs, RCPs, boundaries and session policies are fences: they never grant, only limit. Identity and resource policies are keys. You need a key and must stay inside every fence.

2.1Data perimeters and external access

A data perimeter means: only trusted identities access trusted resources from expected networks.

PerimeterTypical condition keysEnforced with
Identity: only my org's principals reach my resourcesaws:PrincipalOrgID, aws:PrincipalIsAWSServiceRCPs, resource policies
Resource: my principals only reach my org's resourcesaws:ResourceOrgIDSCPs, VPC endpoint policies
Network: access only from my VPCs or corporate IPsaws:SourceVpc, aws:SourceVpce, aws:SourceIp, aws:ViaAWSServiceSCPs, RCPs, resource policies
  • VPC endpoint policies: limit what can be done through an endpoint (for example only buckets in my org).
  • IAM Access Analyzer: external access findings (resources shared outside your zone of trust), internal access findings, unused access (unused roles, keys, permissions), policy validation, custom policy checks in pipelines, and policy generation from CloudTrail.
  • AWS Verified Access: zero-trust access to internal web apps (and TCP resources) without a VPN; checks identity (Identity Center, OIDC) and device posture on every request.
"Stop anyone outside the organization reading any S3 bucket, even if a developer writes a bad bucket policy, across all accounts" → an RCP denying s3:* when aws:PrincipalOrgID isn't yours (with an exception for AWS service principals). An SCP can't do this: SCPs only limit your own principals.

2.2Encryption at rest with AWS KMS

Key typeWho controls itNotes
AWS owned keysAWS, shared across accountsDefault for some services; invisible to you; no audit
AWS managed keys (aws/s3…)AWS in your accountAuto-rotated yearly; you can't change the key policy or share cross-account
Customer managed keysYouYour key policy and grants, cross-account sharing, enable/disable, scheduled deletion, configurable automatic rotation (90–2,560 days) and on-demand rotation
  • Envelope encryption: KMS encrypts a data key; the data key encrypts the data. That's how services encrypt huge data with a key that never leaves KMS.
  • Multi-Region keys: same key material and ID in several Regions; decrypt in another Region without re-encrypting (DR, global tables, client-side encryption).
  • Key policy is the primary control; without a statement allowing the account, IAM policies alone can't use the key.
  • Bring your own: imported key material (you can delete it instantly), CloudHSM key store (keys in your CloudHSM cluster), external key store (XKS) (keys stay in your HSM outside AWS).
  • Cross-account: grant the other account in the key policy and give its principals IAM permission. Snapshots/AMIs encrypted with AWS managed keys can't be shared; re-encrypt with a customer managed key.
KMS keys are the master key in a bank vault; data keys are the keys to individual safe-deposit boxes, handed out and locked away again by the vault.

2.2Encryption in transit, HSMs and post-quantum crypto

Certificates

  • AWS Certificate Manager (ACM): free public TLS certificates with auto-renewal for ALB, NLB, CloudFront, API Gateway. CloudFront certificates must be in us-east-1. ACM also offers paid exportable public certificates for use on your own servers.
  • AWS Private CA: your own private certificate authority for internal TLS, mutual TLS (mTLS), IoT devices, and IAM Roles Anywhere trust anchors; short-lived certificate mode is cheaper.
  • Enforce modern TLS (1.2/1.3) with load balancer and CloudFront security policies; require HTTPS in bucket policies with aws:SecureTransport.

AWS CloudHSM

Single-tenant FIPS 140-3 Level 3 HSMs in your VPC that only you control (AWS can't access keys). Run a cluster across AZs. Pick it when a regulation demands dedicated HSMs or sole key custody, or when apps need standard HSM APIs (PKCS#11, JCE, Microsoft CNG/KSP), SSL/TLS offload, or Oracle/SQL Server TDE. Otherwise KMS is simpler, integrated and also uses FIPS 140-3 validated HSMs.

Post-quantum cryptography New in C03

ThreatAlgorithmOn AWS
"Harvest now, decrypt later": attackers record encrypted traffic today and decrypt it once quantum computers arriveML-KEM (FIPS 203) key encapsulation, used in hybrid TLS key exchange (classic ECDH + ML-KEM)Hybrid post-quantum TLS on AWS KMS, ACM and Secrets Manager endpoints; enable in the AWS SDK / CRT client
Forged signatures on long-lived artifacts (firmware, roots of trust, documents)ML-DSA (FIPS 204) digital signaturesKMS asymmetric keys with key specs ML_DSA_44, ML_DSA_65, ML_DSA_87; Sign/Verify APIs

A strategy: inventory where you use public-key crypto; prioritize data that must stay secret for many years; adopt hybrid PQ TLS for those connections first; use ML-DSA for new long-lived signing keys; design for crypto agility (swap algorithms without re-architecting). Symmetric AES-256 (what KMS uses for data) is already considered quantum-resistant.

KEM = Keeps secrets in transit (key exchange). DSA = Digital Signature: proves who signed.

2.3Multi-account structure and landing zones

  • AWS Organizations: accounts grouped into organizational units (OUs); consolidated billing; policies (SCPs, RCPs, tag policies, backup policies, AI opt-out, declarative policies); delegated administrator accounts for security services.
  • AWS Control Tower: sets up a landing zone (management, Log Archive and Audit accounts, Identity Center, central CloudTrail and Config) and applies controls: preventive (SCPs/RCPs), detective (Config rules), proactive (CloudFormation Hooks). Account Factory vends new compliant accounts; Account Factory for Terraform (AFT) and customizations (CfCT) automate baselines.
  • Recommended OUs: Security, Infrastructure, Workloads (Prod / Non-prod), Sandbox, Policy Staging, Suspended.

SCP vs RCP

Service control policy (SCP)Resource control policy (RCP)
LimitsWhat principals in your accounts can doWhat can be done to resources in your accounts, by anyone
Typical useDeny leaving the org, deny unapproved Regions, protect security tooling, require tagsData perimeter: block outside-org access to S3, KMS, SQS, Secrets Manager, STS role assumption
Affects management account?NoNo
Grants permissions?NeverNever
SCP = rules for your people. RCP = rules for your stuff.

Cross-account resource sharing

AWS Resource Access Manager (RAM) shares resources instead of copying them: VPC subnets (shared VPC), Transit Gateways, Route 53 Resolver rules, IPAM pools, prefix lists, Network Firewall policies, License Manager configs, Aurora clusters for cloning, VPC Lattice service networks, and more. Share with the whole org or an OU with no invitation needed.

2.3Centralized logging, compliance monitoring and patching

NeedAnswer
All API activity from every account in one placeCloudTrail organization trail → S3 in the Log Archive account (or CloudTrail Lake)
Configuration history and compliance across accountsAWS Config + aggregator; conformance packs; org-wide Config rules
Threat detection everywhereAmazon GuardDuty with a delegated admin and auto-enable for new accounts
One normalized security data lakeAmazon Security Lake (OCSF format in S3; CloudTrail, VPC Flow Logs, Route 53, Security Hub findings; subscribers like SIEMs)
Security posture checks and prioritized findingsSecurity Hub CSPM (best-practice controls and standards: AWS Foundational Security Best Practices, CIS, PCI DSS, NIST) + Security Hub (correlates findings into exposures, attack paths, response workflows)
Log GenAI prompts and responsesBedrock model invocation logging to S3 / CloudWatch Logs in each account, aggregated centrally; AgentCore Observability for agents
Find vulnerable softwareAmazon Inspector: continuous CVE scanning of EC2, ECR images and Lambda; network reachability; SBOM export; org-wide via delegated admin
Patch fleets on scheduleSystems Manager Patch Manager (patch baselines, maintenance windows; patch policies across the org via Quick Setup)
Auto-fix non-complianceConfig rule → automatic remediation with an SSM Automation document
"New accounts must automatically get GuardDuty, Config and CloudTrail with no manual steps" → Control Tower landing zone / Organizations integrations with delegated administrator + auto-enable. "Detect, then auto-fix an open security group" → Config rule + SSM Automation remediation (or Security Hub automation rule → EventBridge → Lambda).

2.4Meeting compliance, sovereignty and audit requirements

Data residency and sovereignty New in C03

  • Deploy only in approved Regions; enforce with an SCP denying actions when aws:RequestedRegion isn't allowed (Control Tower has a built-in Region deny control). Exempt global services (IAM, CloudFront, Route 53…).
  • Block transfers out: deny S3 replication to other Regions, deny KMS key sharing, restrict snapshot copy and AMI sharing.
  • For GenAI, use geographic cross-Region inference profiles (EU, US…) so prompts stay in the geography; avoid global profiles where residency applies.
  • Encryption doesn't move data; residency is about where data is stored and processed.

Audit trails, including AI services

  • CloudTrail management events (default) plus data events (S3 object reads, Lambda invokes, DynamoDB items) when needed; log file integrity validation (digest files) proves logs weren't changed.
  • Store logs in a separate Log Archive account, encrypted with KMS, with S3 Object Lock (compliance mode) for write-once-read-many retention.
  • CloudTrail records every Bedrock API call; model invocation logging records the actual prompts and outputs (it's off by default).

Evidence and risk

NeedAnswer
Download AWS's own SOC, ISO, PCI reports; accept agreements (HIPAA BAA)AWS Artifact New in C03
Continuously collect evidence from your accounts for your auditAWS Audit Manager (not on the C03 list, but still the matching service), Config conformance packs, Security Hub CSPM standards
Assess risk before buildingThreat modeling (for example STRIDE: spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege), Well-Architected reviews, mitigations mapped to controls New in C03
Artifact = AWS's report card. Audit Manager = your report card.

2.5Security and responsible AI controls New in C03

Amazon Bedrock Guardrails

PolicyBlocks or checks
Content filtersHate, insults, sexual, violence, misconduct (text and images), and prompt attacks (jailbreaks, injection)
Denied topicsSubjects you define ("no investment advice")
Word filtersSpecific words, profanity
Sensitive information filtersBlock or mask PII; custom regex (account numbers)
Contextual grounding checksAnswers not supported by the source or not relevant (hallucinations in RAG)
Automated Reasoning checksVerify answers against formal rules (policies) using logic

Guardrails work across models, and the ApplyGuardrail API can check text for any model, even ones outside Bedrock. Enforce them centrally: an IAM policy with the bedrock:GuardrailIdentifier condition key denies any inference call that doesn't use the approved guardrail.

Access controls for agents

  • AgentCore Identity: inbound authentication of users/apps calling the agent (Cognito, Okta, Entra ID…), and outbound credentials (OAuth tokens, API keys in a secure token vault) so agents act on behalf of a user with that user's consent and scope.
  • Policy in AgentCore: Cedar rules for which tools/actions an agent may call, enforced at the Gateway.
  • Least privilege for the agent's role: scope its IAM role to only the tools and data it needs; private VPC connectivity; log everything.

Human oversight workflows

AI proposes action→Step Functions task with .waitForTaskToken→SNS / email / ticket to reviewer→Approve or reject (SendTaskSuccess / Failure)→Execute or roll back

Use for high-impact or low-confidence actions (refunds above a limit, production changes). Lambda durable function callbacks and Bedrock Agents' user confirmation / return of control are alternatives.

"Every team's GenAI app must block PII leakage and prompt injection, enforced centrally" → one approved Guardrail + IAM/SCP deny when bedrock:GuardrailIdentifier doesn't match + invocation logging. "Agent must call Salesforce as the signed-in user" → AgentCore Identity (OAuth on behalf of user).
Sources
Domain 3

Cost-optimized architecture design

15% of scored content · Tasks 3.1–3.4

3.1Purchase options

OptionCommitmentMax discount (approx.)FlexibilityPick it when…
On-DemandNone0%TotalShort, spiky, unpredictable, or new workloads
Spot Instances / Fargate SpotNone; AWS can reclaim with a 2-minute warningUp to 90%Interruptible onlyStateless, fault-tolerant, flexible: batch, CI, big data, containers. Use many instance types + capacity-optimized allocation
Compute Savings Plans$/hour for 1 or 3 yearsUp to 66%Any EC2 family, size, OS, Region; also Fargate and LambdaSteady baseline but you expect to change instance types, Regions or move to containers/serverless
EC2 Instance Savings Plans$/hour, 1 or 3 years, one family in one RegionUp to 72%Size, OS, AZ within the familyStable family in one Region
Reserved Instances (Standard / Convertible)1 or 3 yearsUp to 72% / 66%Convertible can be exchanged; zonal RIs also reserve capacityMostly superseded by Savings Plans for EC2; still the model for RDS, ElastiCache, OpenSearch, Redshift reserved nodes
Database Savings Plans$/hour, 1 year, no upfrontUp to 35%Across Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS; any engine, size or RegionSteady database spend that may change engine or Region
SageMaker Savings Plans$/hour, 1 or 3 yearsUp to 64%SageMaker instance usageSteady ML hosting/training
On-Demand Capacity ReservationsNone (pay whether used or not)0% alone (combine with Savings Plans)Specific AZ and typeGuaranteed capacity for a launch event or DR failover
Provisioned capacity (DynamoDB, Bedrock Provisioned Throughput, Kinesis shards)VariesLower unit price at steady load—Predictable, steady throughput
Try it

Pick the purchase option

Layer it like a cake: Savings Plans for the steady base, On-Demand for the bumps, Spot for anything that can be interrupted.

3.1Cost-optimized architectures and rightsizing

  • Graviton (Arm) instances: up to ~40% better price-performance; also for Lambda, Fargate, RDS, ElastiCache. Usually a recompile or a multi-arch container image.
  • Step Functions: Standard bills per state transition; Express bills per request and duration. High-volume short workflows → Express is far cheaper.
  • Lambda: bills per ms × memory; right-size memory (Lambda Power Tuning), use Arm, avoid idle waits (durable functions waits don't bill compute).
  • Serverless vs always-on: low or spiky utilization → Lambda/Fargate/Aurora Serverless; steady high utilization → EC2/containers with Savings Plans.
  • AWS Compute Optimizer: ML rightsizing for EC2, Auto Scaling groups, EBS, Lambda, ECS on Fargate, RDS/Aurora, and commercial licenses. Turn on enhanced infrastructure metrics for 3 months of lookback.
  • Scaling for cost: scheduled scaling (shut dev down at night), target tracking, predictive scaling; Instance Scheduler for stop/start.

Optimizing AI/ML costs New in C03

LeverHow it saves
Bedrock service tiersStandard (pay per token), Priority (fastest, premium price), Flex (cheaper, for non-urgent work), Reserved (term commitment for predictable throughput)
Batch inferenceLarge non-urgent jobs from S3 at a lower price than on-demand
Prompt cachingRepeated long prompt prefixes (system prompt, documents) billed at a reduced rate and served faster
Smaller or distilled model; intelligent prompt routingSend easy requests to a cheaper model
Response cachingCache answers to frequent questions (ElastiCache / semantic cache) so you don't call the model at all
Cap output tokens; trim contextFewer tokens billed
SageMaker: serverless or async (scale to zero), multi-model endpoints, Savings Plans, Inferentia/Graviton instancesStop paying for idle GPUs
Bill too high for a nightly document-summary job → Bedrock batch inference (or Flex tier). Same 20-page policy sent with every chat → prompt caching.

3.2Data transfer and network costs

TrafficCost rule of thumb
Internet → AWS (inbound)Free
AWS → internetCharged per GB (the big one); CloudFront usually cheaper and origin → CloudFront from AWS origins is free
Same AZ, private IPFree
Across AZs in a RegionCharged in each direction (includes cross-AZ VPC peering)
Across RegionsCharged per GB (replication, peering, TGW peering)
NAT gatewayHourly + per-GB processing charge, on top of transfer
Gateway VPC endpoints (S3, DynamoDB)Free
Interface endpoints (PrivateLink)Hourly per AZ + per-GB processed (cheaper per GB than NAT)
Transit GatewayPer attachment-hour + per-GB processed
VPC peeringNo hourly or processing fee; only normal cross-AZ / cross-Region transfer
Direct ConnectPort-hours + lower data-transfer-out rate than internet
Try it

Cut the network bill

Think of your answer, then tap a card to check it.

Content delivery

  • CloudFront: cache static and cacheable dynamic content; long TTLs with versioned file names; cache policies that include only needed headers/cookies/query strings (higher hit ratio).
  • Origin Shield: an extra central caching layer that collapses requests to the origin (good for multi-Region or expensive origins).
  • Origin failover: origin groups switch to a secondary origin on errors.
  • Price classes limit edge locations to cheaper regions.

Cost-aware replication

Replicate only what DR needs: S3 Replication with filters (prefix/tag), lifecycle in the destination (replicate into cheaper storage classes), S3 Replication Time Control only when you need the 15-minute SLA; DynamoDB global tables charge for replicated writes in every Region, so add Regions deliberately.

Data is free to check in, cheap to stay in one room, and costs every time it changes rooms (AZ), buildings (Region) or leaves (internet).

3.3Cost allocation, visibility and alerts

NeedAnswer
Attribute spend to business units, projects, environmentsCost allocation tags (activate user-defined tags in Billing; AWS-generated tags like aws:createdBy)
Standardize tag keys and valuesTag policies (Organizations)
Block untagged resources at creationSCP denying create actions when aws:RequestTag/CostCenter is missing
Detect untagged resources after creationAWS Config required-tags rule (+ remediation)
Group costs by rules (team = these accounts + these tags)AWS Cost Categories
Split shared EKS/ECS cluster costs by pod or taskSplit cost allocation data in the Cost and Usage Report
Chargeback GenAI usage per teamBedrock application inference profiles with tags; CloudWatch token-count metrics (InputTokenCount, OutputTokenCount)
Most detailed billing data for SQL analysisCost and Usage Report (CUR 2.0 via Data Exports) → S3 → Athena / QuickSight
Explore and forecast spend, RI/SP recommendationsAWS Cost Explorer
Alert (or act) before spend passes a thresholdAWS Budgets (cost, usage, RI/SP coverage & utilization); budget actions can apply an SCP/IAM policy or stop EC2/RDS
Catch unusual spikes automaticallyAWS Cost Anomaly Detection (ML monitors per service, account, tag or cost category; SNS/email alerts)
Showback = show each team its bill. Chargeback = actually send them the bill.
Budgets is a threshold you set; Anomaly Detection finds spikes you didn't predict. "Stop a sandbox account spending past $500" → Budgets with a budget action that applies a deny SCP.

3.4Storage cost: S3 classes and lifecycle

ClassRetrievalMin. durationAZsPick it when…
S3 Standardms—≥3Frequently accessed
S3 Intelligent-Tieringms (optional archive tiers slower)—≥3Unknown or changing access; no retrieval fees; small monitoring fee per object (objects <128 KB aren't tiered)
S3 Standard-IAms, per-GB retrieval fee30 days≥3Infrequent but must be instant (monthly)
S3 One Zone-IAms30 days1Re-creatable infrequent data (secondary copies, thumbnails)
S3 Glacier Instant Retrievalms90 days≥3Rarely accessed (quarterly) but needed instantly (medical images)
S3 Glacier Flexible Retrievalminutes to 12 hours (free bulk)90 days≥3Archives, backups
S3 Glacier Deep Archive12–48 hours180 days≥3Cheapest; compliance archives kept 7–10 years
Try it

Pick the S3 storage class

Lifecycle rules transition objects by age (for example Standard → Standard-IA at 30 days → Glacier Flexible at 90 → Deep Archive at 365) and expire old versions and incomplete multipart uploads. S3 Storage Lens shows where to optimize. EFS lifecycle moves cold files to EFS Infrequent Access and Archive; EFS One Zone is cheaper for non-critical data.

Glacier names by speed: Instant (now), Flexible (later today), Deep (the day after tomorrow).

3.4Block storage, database, backup and observability costs

EBS volume types

TypePerformanceCost note
gp33,000 IOPS and 125 MiB/s baseline at any size; provision more IOPS/throughput independentlyAbout 20% cheaper per GB than gp2; usually the answer
gp23 IOPS per GiB (burst to 3,000 on small volumes); performance tied to sizeTeams over-provision size just to get IOPS → migrate to gp3 (no downtime)
io2 Block ExpressUp to 256,000 IOPS, sub-ms latency, 99.999% durability, Multi-AttachOnly for critical high-IOPS databases
st1 / sc1Throughput-optimized / cold HDDBig sequential (logs, data warehouse) / rarely accessed

Delete unattached volumes and old snapshots; EBS Snapshots Archive is up to 75% cheaper for snapshots kept 90+ days.

Database cost levers

LeverUse when
DynamoDB on-demandUnpredictable traffic, new tables, spiky
DynamoDB provisioned + auto scaling (+ reserved capacity)Predictable traffic; cheaper at steady load
DynamoDB Standard-IA table classStorage dominates cost, data rarely read
RDS reserved DB instances / Database Savings PlansSteady databases
Aurora Serverless v2Variable or intermittent load; scales in fine-grained ACUs (can scale to 0 with auto-pause)
Aurora I/O-OptimizedI/O charges are more than ~25% of Aurora spend; no per-I/O charges, higher instance/storage price
Aurora StandardLow-to-moderate I/O

Backup retention

  • AWS Backup plans: schedules, retention, lifecycle to cold storage (must stay 90+ days), cross-Region and cross-account copies.
  • Amazon Data Lifecycle Manager (DLM): automate EBS snapshot and AMI creation, retention, cross-Region copy and archiving, for free. New in C03
  • Keep only what the RPO and regulations require; tier long-term backups to cold/archive.

Cost-effective observability New in C03

  • Set CloudWatch Logs retention on every log group (default is never expire).
  • Use the Infrequent Access log class for logs you rarely query (cheaper ingestion).
  • Filter at the source (log level, subscription filter patterns) and sample debug logs; export old logs to S3 Glacier.
  • Aggregate metrics: Embedded Metric Format, fewer high-cardinality dimensions, standard (not high-resolution) metrics unless needed; metric filters instead of custom metric calls.
  • Avoid duplicate pipelines sending the same logs to several tools.
Sources
Domain 4

Resilience, migration and business continuity

15% of scored content · Tasks 4.1–4.3

4.1The 7 Rs of migration

StrategyWhat you doExample
RetireTurn it offAn app nobody uses
RetainKeep on-premises for nowRecently upgraded mainframe; compliance hold
Rehost ("lift and shift")Move servers as-is to EC2Fast data-center exit with Transform MGN
RelocateMove a whole platform without changing itVMware workloads to Amazon Elastic VMware Service (EVS)
Repurchase ("drop and shop")Switch to SaaSOn-prem CRM → Salesforce
Replatform ("lift, tinker and shift")Small changes to use managed servicesSelf-managed MySQL → RDS; app server → Elastic Beanstalk or ECS
Refactor / re-architectRebuild cloud-nativeMonolith → microservices on Lambda / containers
Try it

Which R?

Think of your answer, then tap a card to check it.

Effort and benefit both rise as you go Rehost → Replatform → Refactor: move it, tweak it, rebuild it.

4.1Discovery, wave planning and rehosting

  • Discovery and portfolio assessment: collect server inventory, utilization and network dependencies, then group tightly coupled apps into the same migration wave. AWS Transform does agentic discovery and wave planning; Migration Evaluator builds the business case. (Application Discovery Service and Migration Hub are closed to new customers.)
  • AWS Transform MGN (previously AWS Application Migration Service): installs an agent, does continuous block-level replication to a low-cost staging area, launches test instances, then cuts over in minutes. Post-launch actions can install agents and modernize. Can be driven by the AWS Transform agent (discovery → landing zone → network → rehost).
  • AWS Transform (agentic): also modernizes VMware, Windows/.NET, mainframe (COBOL to Java) and code upgrades.
  • Land in a prepared multi-account landing zone (Control Tower) with networking in place before wave 1.
"Move hundreds of servers quickly with minimal downtime and no code changes" → Transform MGN. Don't pick hand-built AMIs, VM Import scripts, or the old SMS (Server Migration Service, retired).

4.1Database and data migration

ToolJob
AWS DMSMigrate databases with full load + change data capture (CDC) for near-zero downtime; homogeneous (MySQL→MySQL) or heterogeneous (Oracle→PostgreSQL); DMS Serverless; also continuous replication to targets like S3, Kinesis, Redshift
DMS Schema Conversion / AWS SCTConvert schema, stored procedures and code between engines (heterogeneous); SCT also has data extraction agents for warehouses
Native toolsBackups/restore to RDS (for example SQL Server native backup to S3), Percona XtraBackup to Aurora MySQL, logical replication
AWS DataSyncFile and object data over the network, scheduled and incremental, with verification
AWS Data Transfer TerminalPhysical AWS facility: bring your own storage devices and upload at high speed (Enterprise Support customers) New in C03
Snowball EdgeShippable device (closed to new customers since Nov 2025; may still appear in old questions)
Direct ConnectSustained high-throughput network transfer
Try it

Network or physical? Estimate transfer time

Rule of thumb: 1 Gbps moves about 10 TB a day at full speed. If the math says weeks and the deadline says days, go physical or add bandwidth.

4.1Replatforming, refactoring and legacy modernization

  • Replatform targets: RDS/Aurora (no DB admin), ECS/Fargate (containerize without Kubernetes overhead), Elastic Beanstalk (managed app platform), Lambda (event-driven pieces), Amazon MQ (keep broker protocol), FSx (keep file protocol).
  • Strangler fig pattern: put a router (API Gateway, ALB rules, CloudFront) in front of the monolith; move one feature at a time to a new service; route that path to the new service; eventually retire the monolith. Low risk, incremental.
  • Decomposition: split by business capability / domain (orders, payments); give each service its own data store; communicate through events. Add an anti-corruption layer so new services aren't polluted by the legacy model.
  • Serverless adoption: move scheduled jobs to EventBridge Scheduler + Lambda, file processing to S3 events + Lambda, workflows to Step Functions.
  • Legacy (mainframe, .NET Framework, old databases): AWS Transform for mainframe and .NET (agentic code analysis and conversion), replatform COBOL runtimes, move DB2/Oracle to Aurora with DMS + schema conversion.
The strangler fig vine grows around the old tree until the tree can be removed. You never cut it down in one go.

4.2Disaster recovery strategies

RPO (recovery point objective): how much data you can lose, measured back in time. RTO (recovery time objective): how long you can be down.

StrategyWhat runs in the DR RegionRPORTOCost
Backup and restoreNothing but backups (AWS Backup copies, snapshots, S3 replication); rebuild with IaCHoursHours (up to 24)$
Pilot lightData replicated live (DB replica); app servers defined but off / not deployedMinutesTens of minutes to hours$$
Warm standbyFull stack running at reduced capacity; scale up on failoverSeconds to minutesMinutes$$$
Multi-site active/active (or hot standby)Full capacity serving traffic in both RegionsNear zeroNear zero$$$$
Try it

Pick the cheapest DR strategy that meets the targets

A pilot light in a furnace gives no heat but lights the burners fast. Warm standby is the furnace on low.

Services for DR

ServiceRole
AWS Elastic Disaster Recovery (DRS)Continuous block-level replication of servers (on-prem or another Region) to a cheap staging area; RPO in seconds, RTO in minutes; point-in-time recovery (ransomware); failback
AWS Resilience HubDefine RTO/RPO policy per app, assess the architecture, get recommendations, SOPs, alarms and FIS tests; track resilience drift
Systems Manager Automation runbooksScripted, repeatable recovery steps (promote replica, scale ASG, update DNS)
Route 53 health checks + failover routingDNS failover between Regions
AWS Global AcceleratorFast failover between Regional endpoints behind static IPs
Amazon Application Recovery Controller (ARC)Region switch (orchestrated multi-Region failover plans), routing controls (highly available on/off switches for DNS failover), zonal shift / zonal autoshift (move traffic away from an impaired AZ), readiness checks

Replicating data across Regions

DataReplication
AuroraGlobal Database (sub-second lag typical, managed failover)
RDSCross-Region read replica (promote) or automated backup replication
DynamoDBGlobal tables (MRSC for zero RPO)
S3Cross-Region Replication; Replication Time Control (15-minute SLA); Multi-Region Access Points with failover controls
EFS / FSxEFS replication; FSx backups or ONTAP SnapMirror
EBS / anythingAWS Backup cross-Region copy; DLM snapshot copy
ContainersECR replication + IaC/GitOps to recreate clusters
Fail over using data plane actions (health checks, ARC routing controls, pre-scaled capacity), not control-plane actions that might be impaired during an event, like creating resources or editing DNS records in the console. This is called static stability.

Multi-cluster containers for HA/DR New in C03

  • Run identical EKS or ECS clusters in two Regions (or two clusters per Region for blast-radius isolation), deployed from the same IaC/GitOps (for example Argo CD/Flux) source.
  • Replicate images (ECR replication) and data stores; route with Route 53 / Global Accelerator / ARC.
  • Keep state outside clusters (Aurora Global, DynamoDB global tables, S3) so a cluster can be replaced; back up Kubernetes resources and volumes with AWS Backup for EKS or Velero.
  • Blue/green clusters also make Kubernetes version upgrades safe.

4.3Backup governance and ransomware protection

  • AWS Backup with Organizations: backup policies applied to OUs; a delegated administrator; cross-account monitoring; resources selected by tags.
  • Cross-account and cross-Region copies into a separate, locked-down backup account protect against a compromised production account.
  • Logically air-gapped vaults keep backups isolated and shareable for recovery.
ControlProtects against
S3 Object Lock – governance modeDeletion/overwrite, except by users with a special permission
S3 Object Lock – compliance modeNobody, not even root, can delete before retention ends
Legal holdDeletion indefinitely until removed
EBS snapshot lockSnapshot deletion for a set period (governance or compliance mode)
AWS Backup Vault LockDeletion of recovery points or changes to retention (compliance mode is immutable after a grace period)
S3 Versioning + MFA DeleteAccidental overwrite/delete
Governance mode = a lock with a master key. Compliance mode = a time-lock safe: nobody opens it early.

4.3Resilient design, failover tests and chaos engineering

Design for failure

  • Redundancy: at least 2–3 AZs for every tier; Multi-AZ databases; NAT gateway per AZ.
  • Fault tolerance: load balancers with health checks, queues to absorb spikes, timeouts and retries with backoff.
  • Self-healing: Auto Scaling replaces unhealthy instances; ECS/EKS replace failed tasks/pods; Lambda retries.
  • Blast-radius reduction: cell-based architecture (independent copies of the stack, each serving a subset of customers), shuffle sharding, separate accounts.
  • Static stability: pre-provision enough capacity in each AZ to survive losing one, so recovery needs no new launches.

AWS Fault Injection Service (FIS) New in C03

  1. Define the steady state (normal metrics: p99 latency, error rate, orders/minute).
  2. Write a hypothesis: "if one AZ loses network, orders/minute stay within 5%".
  3. Build an experiment template: actions (stop instances, inject CPU stress, throttle APIs, AZ power interruption scenario, fail over RDS), targets (by tag), and stop conditions (CloudWatch alarms that halt the experiment).
  4. Run in pre-prod, then production with a small blast radius; measure recovery time against RTO.
  5. Fix weaknesses and repeat, ideally automated in pipelines.

Test failover too: flip Route 53 / ARC to the DR Region on a schedule and measure actual RTO and RPO.

"Prove the app survives an AZ outage, safely, with automatic abort if customers are affected" → FIS experiment with a CloudWatch alarm stop condition. Resilience Hub can recommend and run these tests.
Sources
Domain 5

Operational excellence and automation

20% of scored content · Tasks 5.1–5.4

5.1Infrastructure as code

ToolStyleKey features
AWS CloudFormationDeclarative (YAML/JSON templates: what you want)Change sets (preview), drift detection, rollback, stack policies, nested stacks, modules, DeletionPolicy: Retain/Snapshot, custom resources (Lambda), resource import
AWS CDKImperative code (TypeScript, Python, Java…) that synthesizes CloudFormationConstructs: L1 (raw), L2 (sensible defaults), L3 (patterns); loops and logic; aspects visit every construct to check or change it; cdk-nag rule packs
CloudFormation StackSetsOne template, many accounts and RegionsService-managed permissions with Organizations: auto-deploy to new accounts in an OU; concurrency and failure tolerance

Policy as code

WhenToolExample
Before code is mergedCDK aspects / cdk-nag, CloudFormation Guard in the pipelineFail the build if a bucket isn't encrypted
Before resources are created (proactive)CloudFormation Hooks (Guard rules or Lambda; Control Tower proactive controls are Hooks)Block a stack that opens port 22 to the world
Always (preventive)SCPs / RCPsDeny disabling CloudTrail anywhere
After creation (detective + remediation)AWS Config rules + SSM Automation remediation; CloudFormation drift detectionDetect a manually changed security group and revert it
Policy as code checks at three gates: the design desk (aspects, Guard), the front door (Hooks, SCPs) and the night patrol (Config).

Secrets in infrastructure code

AWS Secrets ManagerSSM Parameter Store
RotationBuilt in (managed rotation for RDS/Aurora/Redshift; Lambda for others)None built in
Cross-Region replication / cross-account resource policyYesAdvanced tier sharing via RAM only
CostPer secret per month + API callsStandard tier free
Best forDatabase credentials, API keys that must rotateConfig values, feature flags, non-rotating SecureStrings

Never hard-code secrets in templates. Use dynamic references ({{resolve:secretsmanager:MySecret:SecretString:password}}), let RDS manage the master password in Secrets Manager (ManageMasterUserPassword), and pass secrets to ECS/Lambda by ARN.

5.2CI/CD and DevSecOps pipelines

Source (CodeCommit / GitHub via CodeConnections)→Build & test (CodeBuild)→Scan (Inspector, ECR, Guard)→Sign (AWS Signer)→Deploy to test account→Manual approval→Deploy to prod accounts/Regions (CodeDeploy / CloudFormation)
ServiceJob
AWS CodePipelineOrchestrates stages; V2 pipelines add Git triggers (branches, tags, file paths), variables and execution modes
AWS CodeBuildManaged builds and tests (buildspec.yml); runs scanners
AWS CodeDeployDeploys to EC2/on-prem, Lambda and ECS with in-place or blue/green, canary or linear traffic shifting, and automatic rollback on CloudWatch alarms
AWS CodeCommitManaged private Git repositories

Security in the pipeline New in C03

  • Amazon Inspector CI/CD scanning (SBOM generator) in CodeBuild fails builds with critical CVEs; ECR enhanced scanning rescans images continuously after push.
  • Static checks: Guard/cdk-nag on IaC, Access Analyzer custom policy checks on IAM changes, secrets scanning.
  • Sign artifacts (AWS Signer for container images and Lambda code signing) and verify before deploy, so only trusted builds run.

Multi-account, multi-Region pipelines New in C03

  • Pipeline lives in a central tooling/deployment account.
  • Artifacts in S3 encrypted with a customer managed KMS key whose key policy allows the target accounts (AWS managed keys can't be shared).
  • Each target account has a cross-account deployment role that the pipeline assumes (role delegation); CloudFormation runs with a least-privilege execution role there.
  • Artifact promotion: build once, promote the same signed artifact dev → test → prod; never rebuild per environment.
  • Multi-Region: add actions per Region (CodePipeline cross-Region actions with an artifact bucket per Region) or use StackSets.

Evaluating AI applications New in C03

Amazon Bedrock Evaluations compares models and prompts on your own dataset with automatic metrics, LLM-as-a-judge (correctness, helpfulness, harmfulness…) or human reviewers, and evaluates RAG (retrieval relevance, faithfulness to sources). Run it as a pipeline gate before switching a model or prompt version.

5.2Deployment strategies with rollback

StrategyHowDowntimeRollback speedExtra cost
All at once (in-place)Update every instance togetherYesSlow (redeploy old)None
RollingUpdate in batchesReduced capacitySlowNone
Rolling with additional batchAdd a batch first, then rollNoSlowSmall
ImmutableNew instances in a new ASG, then swapNoFast (terminate new)Temporary double
Blue/greenFull new environment; shift traffic (DNS, ALB, CodeDeploy)NoInstant (switch back)Double during cutover
CanarySmall % first (for example 10% for 5 minutes), then the restNoFast, automatic on alarmLow
LinearEqual increments every N minutesNoFast, automatic on alarmLow
Feature flagsDeploy dark, enable with AWS AppConfigNoInstant toggleNone
Try it

Pick the deployment strategy

ECS: CodeDeploy blue/green, ECS-native blue/green deployments, and the deployment circuit breaker (auto-rollback when tasks fail to become healthy). Lambda: aliases with weighted traffic + CodeDeploy canary/linear + CloudWatch alarm rollback.

5.3Observability: metrics, logs and traces

NeedTool
Metrics, dashboards, alarms (static, anomaly detection, composite)Amazon CloudWatch
Centralized logs and queriesCloudWatch Logs + Logs Insights
Distributed tracing across servicesAWS X-Ray (service map, traces)
Vendor-neutral instrumentation for metrics and tracesAWS Distro for OpenTelemetry (ADOT): send once, to CloudWatch, X-Ray, Amazon Managed Prometheus or partners
APM: service health, latency, errors, SLOs out of the boxCloudWatch Application Signals
Container metrics and logs (ECS, EKS)CloudWatch Container Insights (enhanced observability for EKS/ECS) New in C03
Watch many accounts from oneCloudWatch cross-account observability (monitoring account linked to source accounts through Organizations)
Scripted checks from outside, 24/7CloudWatch Synthetics canaries (synthetic transactions: log in, add to cart) New in C03
Real browser experience (page load, JS errors) of actual usersCloudWatch RUM (real user monitoring) New in C03
Synthetics = a mystery shopper visiting your store every 5 minutes. RUM = cameras watching real shoppers.

Multi-account log aggregation

Log groups in every account→Subscription filter (account-level or per group)→Central destination (Kinesis Data Streams / Firehose) in the logging account→S3 (Glacier tiers via lifecycle) / OpenSearch / SIEM

Alternatives: CloudWatch cross-account observability for live viewing; organization-wide CloudTrail and Security Lake for security logs.

Alerting

CloudWatch alarm → SNS (email, SMS, chat, Lambda) and/or EventBridge (route to automation) and/or Systems Manager OpsCenter (OpsItems for operators). Use composite alarms to cut noise (page only when latency AND errors are high).

5.3Monitoring AI workloads and setting SLOs

AI/ML metrics to watch New in C03

MetricWhere
Invocations, latency, throttles, errors, input/output token countsBedrock CloudWatch metrics; model invocation logs
Agent performance: steps, tool calls, failures, session traces, latencyAgentCore Observability (OpenTelemetry traces into CloudWatch)
Model performance and drift (data quality, model quality, bias drift, feature attribution drift)SageMaker Model Monitor on endpoints
Endpoint latency, GPU/CPU utilizationSageMaker endpoint CloudWatch metrics
Answer quality over timeScheduled Bedrock Evaluations on sampled traffic; user feedback

Service-level objectives

  • SLI (indicator): what you measure, such as % of requests under 300 ms.
  • SLO (objective): the target, such as 99.9% over 28 days.
  • Error budget: 100% − SLO; how much badness you can spend before freezing risky releases.
  • CloudWatch Application Signals creates SLOs on latency/availability and alarms on burn rate.
Try it

Error budget calculator

5.4Operational automation and safe remediation

Health, capacity and responses

CloudWatch alarm / AWS Health event / Config change→EventBridge rule→SSM Automation runbook / Lambda / Step Functions→Notify via SNS; record OpsItem
  • Service Quotas: view and request limit increases, alarm on usage approaching quotas, quota request templates applied automatically to new accounts in the org.
  • Systems Manager: Automation (runbooks), Run Command, State Manager (keep config), Patch Manager, Maintenance Windows, Change Calendar (block changes during freezes), Session Manager (no SSH keys or bastions), Fleet Manager, OpsCenter.

Controlled remediation with safety constraints New in C03

PatternPlain meaningOn AWS
Circuit breakerStop calling a failing dependency for a while; fail fast instead of piling upApp libraries; ECS deployment circuit breaker; Step Functions error handling
Rate limitsCap how fast actions happenAPI Gateway throttling and usage plans; SSM Automation/Run Command concurrency and error thresholds; Lambda reserved concurrency
BulkheadsIsolate resources so one failure can't sink everythingSeparate queues, thread pools, cells, accounts; per-function concurrency
Retry with exponential backoff and jitterWait longer after each failure, with randomness, so clients don't retry in lockstepAWS SDKs do it by default; Step Functions Retry with BackoffRate and jitter
Idempotency and timeoutsRetries are safe; nothing waits foreverIdempotency tokens; Lambda/SDK timeouts
Human approvalRisky automated fixes pause for a personSSM Automation aws:approve step; Step Functions callback
Try it

See exponential backoff with jitter

Auto scaling policies

PolicyUse
Target trackingKeep a metric at a target (CPU 50%, requests per target) — the default choice
Step scalingAdd more capacity the further the alarm is breached
ScheduledKnown patterns (business hours, month-end)
Predictive scalingML forecast from history (needs at least 24 hours of data; better with 2 weeks) launches capacity before daily/weekly peaks; combine with target tracking
Warm poolsPre-initialized stopped instances for slow-booting apps

Automated failure recovery

  • Auto Scaling health checks: EC2 status checks by default; turn on ELB health checks so instances failing the app check are replaced.
  • ECS replaces tasks that stop or fail container/ALB health checks; EKS restarts pods on liveness probe failure.
  • Lambda: async invokes retry twice, then go to an on-failure destination or DLQ; stream sources can bisect batches and skip poison records.
  • EC2 auto recovery moves an instance to new hardware on a system status check failure.
  • Route 53 health checks remove failed endpoints from DNS.

Runbooks and incident response

Automate routine work with SSM Automation runbooks (AWS-provided like AWS-RestartEC2Instance, or your own): patching through Patch Manager in maintenance windows, remediation triggered by Config or alarms, scaling or failover steps. Start them from EventBridge, alarms or a chat channel; record every run for audit. (Systems Manager Incident Manager is closed to new customers.)

Sources
Compare

Service families

Questions usually hinge on choosing between close neighbors. Each table lists the members, what each does, and the clue that points to it. Click any name to open its card.

Connecting networks

ServiceJobClue in the question
VPC peeringPrivate link between two VPCs"two VPCs", "lowest cost", no transitive need
Transit GatewayRegional hub for VPCs, VPN, DX"hundreds of VPCs", "transitive", "central inspection", "isolated route domains"
Cloud WANGlobal WAN from one policy"global network", "many Regions and branches", "segments by policy"
PrivateLinkExpose one service privately"SaaS provider", "overlapping CIDRs", "one-way access to a service"
VPC LatticeService-to-service app network with IAM auth"microservices across accounts", "no network plumbing", "auth policies"
Direct ConnectDedicated private link to on-prem"consistent latency", "10 Gbps", "reduce egress cost"
Site-to-Site VPNIPsec over internet"quickly", "encrypted backup for DX"
Verified AccessZero-trust app access, no VPN"remote employees", "device posture", "replace VPN"

Traffic, edge and DNS

ServiceJobClue
CloudFrontCDN, caching, edge security"global users", "static content", "reduce origin load / egress"
Global AcceleratorStatic anycast IPs, backbone routing, fast failover"UDP", "gaming", "static IPs", "failover in seconds"
Route 53DNS, routing policies, health checks, Resolver"latency-based", "geolocation", "hybrid DNS"
ALB / NLB / GWLBL7 / L4 / appliances"path routing" / "static IP, TCP" / "third-party firewalls"
API GatewayManaged APIs"throttling per client", "usage plans", "WebSocket"
ARCRegion switch, routing controls, zonal shift"orchestrated Region failover", "shift away from impaired AZ"

Security, by job

JobServices
Who gets inIAM · Identity Center · Cognito · Verified Permissions · Directory Service · IAM Roles Anywhere
Set the fencesOrganizations (SCPs, RCPs, tag & backup policies) · Control Tower · Access Analyzer
Protect the dataKMS · CloudHSM · ACM · Private CA · Secrets Manager · Macie (not listed)
Protect the networkWAF · Shield · Network Firewall · security groups / NACLs · Firewall Manager (not listed)
Find problemsGuardDuty (threats) · Inspector (vulnerabilities) · Security Hub (posture, exposures) · Security Lake (security data lake)
Prove complianceCloudTrail · Config · Artifact · Audit Manager (not listed)
Keep AI safeBedrock Guardrails · AgentCore Identity & Policy · Step Functions approvals
GuardDuty finds intruders. Inspector finds weak spots. Macie finds secrets in S3. Security Hub is the control room. Security Lake is the archive.

Data stores

Shape of dataService
Relational, transactionsRDS · Aurora
Key-value at any scaleDynamoDB (+ DAX)
Documents (MongoDB)DocumentDB
Wide-column (Cassandra)Keyspaces
GraphNeptune
Time seriesTimestream
In-memory, durable primaryMemoryDB
In-memory cacheElastiCache
Warehouse (OLAP)Redshift
Search, logs, vectorsOpenSearch Service
Lake on S3S3 · Glue · Lake Formation · Athena

Migration and transfer

JobServiceClue
Discover, plan waves, migrate with agentsAWS Transform"agentic", "dependencies", "mainframe / .NET / VMware modernization"
Rehost serversTransform MGN"lift and shift", "minimal downtime", "continuous replication"
Migrate databasesDMS + SCT"CDC", "heterogeneous", "minimal downtime"
Move files onlineDataSync"NFS/SMB to S3/EFS/FSx", "scheduled", "verify"
Ongoing hybrid file accessStorage Gateway"on-prem apps keep a file share/iSCSI/tape"
Partner file exchangeTransfer Family"SFTP", "AS2"
Physical bulk uploadData Transfer Terminal"bring drives", "network too slow"
Server-level DRElastic Disaster Recovery"RPO seconds", "failback", "on-prem DR to AWS"

Observability and operations

JobService
Metrics, logs, alarms, dashboardsCloudWatch
TracesX-Ray · ADOT
Who did whatCloudTrail
What changedConfig
Fix things automaticallySystems Manager · EventBridge
Test resilienceFIS · Resilience Hub
LimitsService Quotas
RightsizingCompute Optimizer

Amazon Bedrock and AgentCore parts

FeatureJobClue
Bedrock model APIs (Converse, InvokeModel)Call foundation models"no infrastructure", "many model providers"
Knowledge BasesManaged RAG"answer from our documents", "citations"
GuardrailsContent, PII, prompt attacks, grounding"block topics", "mask PII", "stop jailbreaks"
AgentsManaged agent with action groups"agent calls Lambda APIs"
EvaluationsCompare models, prompts, RAG"is the cheaper model good enough"
Batch inference / service tiers / prompt cachingCost"overnight", "non-urgent", "same long prompt"
Cross-Region inference profilesThroughput and resilience across Regions"throttling", "keep data in the EU"
Model invocation loggingAudit prompts and responses"record what users asked the AI"
AgentCore RuntimeServerless, isolated agent hosting"run agents from any framework"
AgentCore MemoryShort- and long-term memory"remember across sessions"
AgentCore GatewayAPIs / Lambda → MCP tools"give agents our APIs as tools"
AgentCore IdentityInbound auth and outbound credentials"act on behalf of the user", "OAuth"
Policy in AgentCoreCedar rules on tool use"limit which tools an agent can call"
AgentCore ObservabilityTraces and metrics"debug agent steps", "agent latency"
Reference

Services A–Z

Every service and major feature you're likely to see, including the ones used as wrong answers. Each card says what it is, when to pick it, and what it gets confused with. Tags follow the SAP-C03 lists: In scope on the in-scope list (or a feature of a listed service), Out of scope, Not listed on neither list.
Try it

Service flashcards

Read the situation, name the service in your head, then reveal.

Night before

Quick review: "If you see this, pick that"

Each row maps a common exam clue to the answer it usually points to.

Architecture and networking

Security and governance

Cost

Resilience and migration

Operations and AI

Acronyms A–Z

Every acronym used in this guide. Type any of them in the search box to jump here.