The official AWS Certified Solutions Architect - Professional syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Design architectures built for the cloud
SQS standard queues and Lambda event source mappings deliver at least once, so consumers must be idempotent. FIFO queues order messages per message group ID and deduplicate with a deduplication ID or content-based deduplication; SNS FIFO topics fan out to SQS queues, not directly to Lambda. In Kinesis, the partition key decides the shard and the per-key order.
FIFO queue delivery logic in Amazon SQS ↗Amazon SNS message delivery for FIFO topics ↗
A stateless application keeps session and user data outside the instance or task, in ElastiCache, DynamoDB, EFS or S3, so servers can be replaced and scaled without losing anything. DynamoDB global tables accept writes in every Region and TTL removes expired items; in an ElastiCache global datastore only the primary cluster accepts writes. S3 presigned URLs let clients upload files without going through the server.
REL05-BP06 Make systems stateless where possible ↗Global tables - multi-active, multi-Region replication ↗
A typical serverless pipeline ingests into Kinesis Data Streams, delivers to S3 with Amazon Data Firehose (which converts JSON to Parquet with a Glue Data Catalog schema and partitions dynamically) and queries with Athena. Glue job bookmarks prevent reprocessing data; in Athena, columnar formats, partitioning and partition projection reduce scanned data and maintenance.
Convert input data format in Amazon Data Firehose ↗Use partition projection with Amazon Athena ↗
Step Functions Standard workflows are exactly-once, support .sync and .waitForTaskToken and fit long, auditable processes; Express workflows are for short, high-volume events, at-least-once (asynchronous) or at-most-once (synchronous), and the type cannot change after creation. Lambda durable functions write the workflow in code with checkpointed steps and waits that incur no compute charges.
Choosing workflow type in Step Functions ↗Durable functions or Step Functions ↗
To receive events from other accounts, the target bus needs a resource-based policy that allows specific accounts or the whole organization by its ID, and sender rules target the bus ARN with an IAM role. EventBridge does not forward events received from another account on to a third account. Global endpoints fail over to a second Region with a Route 53 health check and recover automatically when replication is enabled.
Sending and receiving events between AWS accounts in Amazon EventBridge ↗Making applications Regional-fault tolerant with global endpoints in EventBridge ↗
Amazon ECS on Fargate removes server management and isolates each task; Amazon EKS keeps Kubernetes tooling, and EKS Auto Mode lets AWS scale and update nodes, with support for DaemonSets, which Fargate does not support. ECS Anywhere registers on-premises servers as external instances with the EXTERNAL launch type, without capacity providers, awsvpc or service load balancing.
Automate cluster infrastructure with EKS Auto Mode ↗Amazon ECS clusters for external instances ↗
Amazon ECS Service Connect builds service discovery and a mesh for ECS services in one Region, with a managed proxy that retries, performs outlier detection and publishes metrics, without code changes. Amazon VPC Lattice connects services on EC2, containers and Lambda across VPCs and accounts, supports overlapping CIDRs, is shared with AWS RAM and authorizes with IAM auth policies (AWS_IAM auth type and SigV4 signing).
Use Service Connect to connect Amazon ECS services with short names ↗What is Amazon VPC Lattice? ↗
ECR basic scanning checks operating system vulnerabilities on push or manually; enhanced scanning with Amazon Inspector adds programming language packages and, in continuous mode, rescans when a relevant CVE appears and publishes findings to EventBridge. Lifecycle policies expire images by tag, count or age, and tag immutability, with optional exclusions, prevents tags from being overwritten.
Scan images for OS and programming language package vulnerabilities in Amazon ECR ↗Automate the cleanup of images by using lifecycle policies in Amazon ECR ↗
In Lambda, provisioned concurrency pre-initializes environments and can be scheduled with Application Auto Scaling, while reserved concurrency caps scaling to protect downstream resources. ECS services scale with Application Auto Scaling; SQS workers should scale on backlog per task. In EKS, the Horizontal Pod Autoscaler needs the Metrics Server and the Cluster Autoscaler adjusts the nodes' Auto Scaling groups.
Configuring provisioned concurrency for an Event Function ↗Scale Amazon ECS services based on an Amazon SQS queue ↗
The Application Load Balancer routes HTTP by path or header; the Network Load Balancer works at layer 4 with TCP and UDP, static IP addresses per zone and client IP preservation. In EKS, the AWS Load Balancer Controller creates an ALB for each Ingress (shareable with IngressGroups) and an NLB for each LoadBalancer Service, with IP targets required on Fargate. REST APIs add API keys, usage plans, caching and WAF compared with HTTP APIs.
Route internet traffic with AWS Load Balancer Controller ↗Choose between REST APIs and HTTP APIs ↗
CloudFront Functions run lightweight JavaScript on viewer requests and responses with submillisecond duration and millions of requests per second: redirects, headers, cache keys and JWT validation, with data in KeyValueStore. Lambda@Edge (Node.js or Python) adds origin events, network and request body access, third-party libraries and longer execution times.
Differences between CloudFront Functions and Lambda@Edge ↗Amazon CloudFront KeyValueStore ↗
An API Gateway WebSocket API keeps two-way connections: the $connect, $disconnect and $default routes, plus custom routes chosen by an expression such as ${request.body.action}, invoke the backend. The backend sends messages to each connection ID with SigV4-signed POST requests to @connections. Authorization uses IAM or a Lambda authorizer, which applies only to $connect.
Overview of WebSocket APIs in API Gateway ↗Use @connections commands in your backend service ↗
In the silo model each tenant has its own resources; in the pool model resources are shared and isolation is applied at runtime with tenant-scoped STS credentials (for example, dynamodb:LeadingKeys). The tenant context travels in the Cognito token; in PostgreSQL, row-level security filters by a session variable, and KMS customer managed keys allow per-tenant encryption.
Preventing cross tenant access ↗Row-level security recommendations ↗
Integrate AI and ML services into architectures
Amazon Bedrock cross-Region inference uses Geographic profiles (US, EU, APAC), suited to data residency, or Global profiles; if SCPs block Regions, they must allow every destination Region in the profile. Tagged application inference profiles enable chargeback and usage metrics per team, and an interface VPC endpoint for bedrock-runtime keeps traffic off the internet.
Geographic cross-Region inference ↗Set up a model invocation resource using inference profiles ↗
Amazon Bedrock AgentCore splits an agent into parts: Runtime hosts agents from any framework in isolated microVM sessions, Gateway turns OpenAPI APIs, Lambda functions and services into MCP tools with inbound and outbound authentication, Identity handles OAuth 2.0 on behalf of users with a token vault, and Memory keeps short- and long-term context. Knowledge Bases provides RAG with metadata filters.
Overview - Amazon Bedrock AgentCore ↗Amazon Bedrock AgentCore Gateway: A secure AI gateway for agents, tools, and models ↗
SageMaker AI offers real-time inference (persistent, low-latency endpoint), serverless inference (intermittent traffic, scales to zero, no GPUs or VPC configuration), asynchronous inference (queued requests, large payloads in S3, long processing, scale to zero and SNS notifications) and batch transform (offline datasets without an endpoint). Multi-model endpoints share a fleet across many models, and SageMaker AI Runtime supports PrivateLink.
Inference options in Amazon SageMaker AI ↗Multi-model endpoints ↗
Amazon Bedrock Knowledge Bases implements RAG: it ingests documents, splits them into chunks (fixed, hierarchical, semantic or none), embeds them and stores them in a vector store. Syncing is incremental. At retrieval, results can be filtered with metadata from .metadata.json files, and hybrid search (vector plus raw text) is available for RDS, OpenSearch Serverless and MongoDB vector stores.
How content chunking works for knowledge bases ↗Configure and customize queries and response generation ↗
Design hybrid cloud integration patterns
For maximum resiliency, Direct Connect uses connections on separate devices in more than one location; high resiliency is one connection per location. On a transit gateway, static routes beat propagated routes and Direct Connect gateway routes beat VPN routes, so a BGP VPN is an automatic backup. ECMP across VPN tunnels needs dynamic routing and the same ASN, and does not work between different attachment types.
AWS Direct Connect Resiliency Recommendations ↗How AWS Transit Gateway works ↗
DataSync moves files and objects between on-premises storage (NFS, SMB, HDFS, object) and AWS services with scheduled, incremental tasks; with a VPC service endpoint the traffic avoids the internet. S3 File Gateway presents S3 as an NFS or SMB share with a local cache, and Transfer Family provides managed SFTP, FTPS, FTP and AS2 into S3 or EFS with post-upload workflows.
To modernize legacy systems without changing them, API Gateway REST APIs transform bodies with VTL mapping templates on non-proxy integrations (HTTP APIs transform only parameters), and passthroughBehavior decides whether unmapped content types are rejected. Amazon MQ is managed ActiveMQ or RabbitMQ using JMS, AMQP or MQTT without rewriting messaging code, and Lambda can consume and transform its messages.
Mapping template transformations for REST APIs in API Gateway ↗What is Amazon MQ? ↗
Route 53 VPC Resolver (formerly Route 53 Resolver) handles hybrid DNS with inbound endpoints (queries from on premises) and outbound endpoints with conditional forwarding rules that can be shared across accounts; forwarding to the VPC+2 address from on premises is not supported. Split-horizon uses same-named public and private zones; a missing private record returns NXDOMAIN, and a Resolver rule overrides a private zone of the same name.
What is Route 53 VPC Resolver? ↗Considerations when working with a private hosted zone ↗
Outposts brings AWS-managed capacity to customer sites as an extension of a Region, with a service link to the Region and a local gateway to the on-premises network. Local Zones place resources near large population centers. ECS Anywhere registers your servers as external instances of an ECS cluster, EKS Hybrid Nodes joins them to EKS over a reliable connection, and EKS Anywhere is customer-managed and can run disconnected.
What is AWS Outposts? ↗Amazon ECS clusters for external instances ↗
Design network architectures
VPC peering links two VPCs (also across accounts and Regions) with non-overlapping CIDRs, is not transitive, cannot use the other VPC's VPN, Direct Connect, NAT or internet gateway, and needs routes on both sides. AWS PrivateLink exposes a service behind a Network Load Balancer to consumer VPCs through interface endpoints, one-way and with overlapping CIDRs allowed. Transit Gateway adds transitive routing at scale.
How VPC peering connections work ↗AWS PrivateLink - Building a Scalable and Secure Multi-VPC AWS Network Infrastructure ↗
Amazon VPC IPAM organizes IP space into scopes, hierarchical pools per Region and environment and VPC allocations, monitors overlap and compliance, and with AWS Organizations shares pools through AWS RAM. An SCP denying ec2:CreateVpc and ec2:AssociateVpcCidrBlock without ec2:Ipv4IpamPoolId enforces it. Public subnets route to the internet gateway, private subnets egress through NAT, and subnet sharing centralizes the network.
How IPAM works ↗Enforce IPAM use for VPC creation with SCPs ↗
Centralized inspection through Transit Gateway needs appliance mode on the inspection VPC attachment so traffic is symmetric. Gateway Load Balancer transparently inserts third-party appliances for all IP traffic. AWS WAF protects resources such as ALB, CloudFront and API Gateway at layer 7. Security groups are stateful and allow-only, network ACLs are stateless and support deny rules, and Flow Logs only record traffic.
Example: Appliance in a shared services VPC ↗What is a Gateway Load Balancer? ↗
An IPv4 VPC can move to dual stack by associating IPv6 CIDR blocks with the VPC and subnets; IPv4 cannot be disabled and there is no migration from IPv4-only to IPv6-only subnets. Outbound-only IPv6 uses an egress-only internet gateway. IPv6-only workloads reach IPv4 services with DNS64 on the subnet and NAT64 on a NAT gateway. A dualstack ALB publishes an AAAA record.
DNS64 and NAT64 ↗Enable outbound IPv6 traffic using an egress-only internet gateway ↗
Route 53 offers failover (active-passive), latency, geolocation (continent, country or US state, with a default record for unmapped locations), geoproximity with bias, weighted, multivalue and IP-based routing; Evaluate Target Health on load balancer alias records steers traffic away from unhealthy resources. Global Accelerator provides static anycast IPs, TCP and UDP support, and regional failover that does not depend on DNS caching.
Choosing a routing policy ↗What is AWS Global Accelerator? ↗
Design data, storage, and database architectures
A data lake on Amazon S3 is cataloged in the AWS Glue Data Catalog and governed with AWS Lake Formation: column, row and cell permissions, LF-Tags to scale, and cross-account sharing through AWS RAM without copies. Redshift Spectrum queries S3 from Redshift through external tables that do not support updates. Apache Iceberg tables add record-level updates and deletes, schema evolution and snapshot isolation.
Amazon MSK runs managed Apache Kafka that works with existing applications, and Redshift streaming ingestion reads from MSK or Kinesis Data Streams directly into materialized views. Amazon AppFlow moves SaaS data such as Salesforce into S3 or Redshift without code, on a schedule or on events, including private flows. On EMR, On-Demand primary and core nodes with Spot task nodes protect HDFS while cutting processing cost.
Streaming ingestion to a materialized view ↗Configuring Amazon EMR cluster instance types and best practices for Spot instances ↗
Database choice follows the access pattern: DynamoDB for keyed access with millisecond latency at any scale and on-demand mode without capacity planning (no JOIN), DAX for microsecond eventually consistent reads, Aurora and RDS for relational OLTP with transactions and read-only replicas, and Redshift for analytics; an Aurora zero-ETL integration brings transactional data into Redshift in near real time.
Aurora Global Database replicates at the storage layer to other Regions; managed failover recovers from a Regional outage and adds the old Region back as a secondary, and write forwarding lets a secondary accept writes. DynamoDB global tables are active-active: MREC replicates asynchronously and MRSC synchronously with an RPO of zero. An RDS Multi-AZ DB cluster gives two readable standbys within one Region.
Using switchover or failover in Amazon Aurora Global Database ↗How DynamoDB global tables work ↗
Choose storage by protocol and access pattern: FSx for Lustre is a parallel POSIX file system linked to S3 with automatic import and export; FSx for NetApp ONTAP serves the same data over NFS and SMB; EFS (NFS only, no Windows) uses Elastic throughput for unpredictable spikes and lifecycle policies to Infrequent Access; EBS Multi-Attach works only for io1/io2 in one Availability Zone.
Linking your file system to an Amazon S3 bucket ↗Amazon EFS performance specifications ↗
DAX is a write-through cache that is API-compatible with DynamoDB and serves eventually consistent reads in microseconds; it passes strongly consistent reads to DynamoDB without caching them and does not see replicated global table writes, which appear only when the TTL expires. With ElastiCache, lazy loading caches only requested data and a TTL bounds stale data.
DAX and DynamoDB consistency models ↗Caching strategies for Memcached ↗
Lake Formation shares Glue Data Catalog resources with other accounts, organizations, or OUs through AWS RAM; LF-Tag based access control is the recommended method for large catalogs, and the recipient account needs resource links to query with Athena. AWS Clean Rooms lets partners analyze combined data without revealing the underlying data, under analysis rules that each data owner sets.
Cross-account data sharing in Lake Formation ↗What is AWS Clean Rooms? ↗