Quibank app: now on the App Store — free, works offline. Get the app ↗

AWS Cloud Practitioner Cheat Sheet: Key Facts

Every key takeaway and common trap from the AWS Cloud Practitioner study guide on one page, grouped by chapter. Tap a lesson link to read the full explanation.

77 facts · 10 chaptersFacts checked 2026-11-15
  1. Cloud Concepts: Benefits & Economics
  2. Cloud Concepts: Well-Architected & Migration
  3. Security: Shared Responsibility & Compliance
  4. Security: IAM & Access Management
  5. Security: Services & Resources
  6. Technology: Deployment & Global Infrastructure
  7. Technology: Compute & Networking
  8. Technology: Databases & Storage
  9. Technology: AI, Analytics & Other Services
  10. Billing, Pricing & Support

Chapter 1

Cloud Concepts: Benefits & Economics

Key takeaways

Common trap

Quick reference

The six advantages of cloud computing →
AdvantageThe problem it answers
Trade fixed expense for variable expensePaying a lot up front before you know how much you will use
Benefit from massive economies of scaleA small buyer cannot reach low unit costs alone
Stop guessing capacityForecasts leave servers idle or short at busy times
Increase speed and agilityWaiting weeks for hardware makes experiments slow and costly
Stop spending money running and maintaining data centersStaff spend their time racking, powering and replacing servers
Go global in minutesDistant users see slow responses and you have no local facility

Chapter 2

Cloud Concepts: Well-Architected & Migration

Key takeaways

Common trap

  • Two pairs are easy to confuse. Logging actions to hold people accountable is security (traceability), while collecting telemetry about workload health is operational excellence (observability). Reducing resources to save energy is sustainability, while reducing them to cut spending is cost optimization. → Pillar trade-offs and the AWS Well-Architected Tool
  • AWS Elastic Disaster Recovery replicates servers much like AWS Application Migration Service, but its purpose is recovering from an outage, not migrating. Likewise, AWS Storage Gateway gives on-premises apps access to cloud storage; it does not migrate a database. → AWS migration services and tools

Quick reference

The six pillars of the Well-Architected Framework →
PillarFocus and a typical principle
Operational excellenceRunning workloads well and improving processes: observability, frequent small reversible changes
SecurityProtecting data and systems: maintain traceability by logging and auditing every action
ReliabilityWorking correctly and recovering from failure: scale horizontally so one failure affects less
Performance efficiencyUsing resources efficiently to meet requirements: go global in minutes for lower latency
Cost optimizationBusiness value at the lowest price point: attribute spending, stop paying for undifferentiated heavy lifting
SustainabilityLowering environmental impact: maximize utilization so less energy is used per unit of work
Migration strategies: the 7 Rs →
StrategyWhat happens
Rehost (lift and shift)Servers move to AWS unchanged
RelocateA whole platform moves in bulk to the cloud version of the same platform
Replatform (lift and reshape)Some optimization, such as a managed database, with no redesign
Refactor (re-architect)Redesign for cloud-native features; the most complex and costly path
Repurchase (drop and shop)Replace with a different product, often SaaS
RetainKeep it where it is for now, for example because of data residency
RetireShut it down because it no longer has business value

Chapter 3

Security: Shared Responsibility & Compliance

Key takeaways

Common trap

  • Wrong answers often say AWS must patch the guest operating system because AWS owns the servers, or split a duty half and half. Owning the hardware does not move the guest OS to AWS, and in a shared control each side does all of its own part. → Security of the cloud and security in the cloud
  • A common distractor says that moving to a managed service hands the customer's code, data or permissions to AWS. Managed means AWS runs more of the infrastructure, never that AWS owns the customer's content or its access decisions. → How responsibility shifts with the service you choose
  • Watch for answers that treat an AWS Artifact report as proof that the customer itself is compliant, claim that AWS is HIPAA certified, or let one in-scope service cover a whole account or Region. → Compliance reports, programs and where data lives

Quick reference

Security of the cloud and security in the cloud →
Control typeWho carries it outExamples
InheritedAWS alone; the customer cites AWS's evidencePhysical and environmental controls at data centers
SharedEach party, in the layer it controlsPatch management, configuration management, awareness and training
Customer specificThe customer aloneProtecting the data and traffic of its own application
How responsibility shifts with the service you choose →
ServiceAWS also runsThe customer still owns
Amazon EC2Only the hosts, hardware and virtualizationGuest OS patches, installed software, security groups, data, access
Amazon RDSThe database host and its operating systemNetwork access, database logins, the choice to encrypt
AWS LambdaServers and, with a managed runtime, runtime patchingFunction code, data, permissions
Compliance reports, programs and where data lives →
ProgramWhat it is about
PCI DSSPayment card data
HIPAAUS health information law, with no formal certification
FedRAMPUS government use of cloud services

Chapter 4

Security: IAM & Access Management

Key takeaways

Common trap

  • Distractors often put a role or an EC2 instance inside a user group, nest one group in another, or copy IAM users into a second account. None of these is possible. The fix is almost always a role. → IAM users, user groups and roles
  • Wrong answers treat read-only access as automatically safe, or let the newest or the user-level policy beat an explicit deny. Safe-sounding broad access is still not least privilege, and an explicit deny always wins. → Policies, deny rules and least privilege

Quick reference

IAM users, user groups and roles →
IdentityWhat it isKey limit
IAM userOne person or workload in one account, with long-term credentialsBelongs to a single account
IAM user groupA set of IAM users that share attached policiesHolds only IAM users, not roles or other groups
IAM roleA set of permissions that a trusted person, service or account assumesGives temporary credentials, no long-term ones
Federation, IAM Identity Center, Amazon Cognito and secrets →
NeedService
Employees reach many accounts in an organization with one sign-in from the corporate directoryAWS IAM Identity Center, with permission sets for each job function
Customers of a web or mobile app sign up and sign in, including with Google or AppleAmazon Cognito
A managed Microsoft Active Directory on AWSAWS Directory Service
A database password kept out of code and rotated on a scheduleAWS Secrets Manager
Plain settings such as endpoints, in a hierarchy, with no rotationAWS Systems Manager Parameter Store

Chapter 5

Security: Services & Resources

Key takeaways

Common trap

Quick reference

Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie →
ServiceWhat it looks forTypical finding
Amazon GuardDutySuspicious activity, using threat intelligence and machine learningAn instance contacting known malicious IP addresses or mining cryptocurrency
Amazon InspectorKnown software vulnerabilities in EC2 instances, container images in Amazon ECR and Lambda functionsA package with a published vulnerability
Amazon MacieSensitive data in objects stored in Amazon S3Files holding names and account numbers
AWS Marketplace and where to find security help →
ResourceUse it for
AWS Knowledge CenterHow-to and troubleshooting articles for common questions
AWS Security BlogIn-depth articles and walkthroughs by AWS experts
AWS Security CenterThe central website for AWS security resources, including how to report a vulnerability
AWS Security BulletinsAnnouncements of vulnerabilities
AWS Trust and SafetyReporting AWS resources used for abuse, such as port scans or spam, even by non-customers

Chapter 6

Technology: Deployment & Global Infrastructure

Key takeaways

Common trap

  • Do not mix deployment models with service models. IaaS and SaaS describe how much a provider manages, not where the application runs, and a VPC is a network inside AWS, not an on-premises data center. → Deployment tools and cloud deployment models
  • Wrong answers claim that a bigger instance is highly available, that AWS copies instances between zones on its own, or that only a second Region can survive a data center failure. Multiple Availability Zones are the expected answer. → Regions, Availability Zones and high availability

Quick reference

Ways to access AWS: console, CLI, SDKs and APIs →
MethodBest fit
AWS Management ConsoleA browser interface for one-time or visual tasks, with no code needed
AWS CLICommands typed in a terminal or saved in shell scripts
AWS SDKsCalling AWS from inside an application, in its programming language
AWS CloudFormationDescribing whole environments as code so they can be built again the same way

Chapter 7

Technology: Compute & Networking

Key takeaways

Common trap

Quick reference

Amazon EC2 instance types, auto scaling and load balancers →
CategoryClue in the question
Memory optimizedLarge data sets processed in memory, such as an in-memory database
Compute optimizedHigh-performance processors: batch processing, media transcoding, game servers
Storage optimizedHeavy sequential reads and writes on local disks
General purposeAn even mix of compute, memory and networking
Inside a VPC: subnets, gateways, security groups and network ACLs →
FeatureSecurity groupNetwork ACL
Applies toAn instanceA subnet
StateStateful: return traffic is allowed automaticallyStateless: return traffic needs its own rule
RulesAllow onlyAllow and deny
Route 53 and connecting networks to AWS →
NeedService
Consistent performance, traffic off the public internet, from a data centerAWS Direct Connect
Encrypted office-to-VPC link set up quickly over the internetAWS Site-to-Site VPN
Individual remote workers on their own laptopsAWS Client VPN
One hub for many VPCs and on-premises networksAWS Transit Gateway
Private access to a supported service through a VPC endpointAWS PrivateLink
Create, publish and manage an API in front of LambdaAmazon API Gateway

Chapter 8

Technology: Databases & Storage

Key takeaways

Common trap

Quick reference

Relational databases: Amazon RDS, Aurora and databases on EC2 →
FeaturePurpose
Multi-AZ DB instance deploymentA standby in another Availability Zone takes over automatically if the primary fails; it does not serve reads
Read replicasAsynchronously updated copies that answer read-only queries and take load off the primary
SnapshotA point-in-time copy that must be restored by hand before use
Amazon S3 object storage, storage classes and lifecycle policies →
Storage classBest fit
S3 StandardFrequently read data
S3 Standard-IARarely read data that must open at once, kept across several Availability Zones
S3 One Zone-IARarely read data you can re-create, kept in one Availability Zone for less
S3 Intelligent-TieringUnknown or changing access; moves objects between tiers by observed access, with no retrieval fees
S3 Glacier Instant RetrievalArchives read a few times a year that must open immediately
S3 Glacier Flexible Retrieval and S3 Glacier Deep ArchiveArchives that can wait for a restore; Deep Archive is the lowest-cost storage in AWS, with the slowest restore

Chapter 9

Technology: AI, Analytics & Other Services

Key takeaways

Common trap

Quick reference

AI and machine learning services: pre-trained services and SageMaker AI →
ServiceInput to output
Amazon TranscribeSpeech to text
Amazon PollyText to lifelike speech
Amazon TranslateText in one language to another language
Amazon ComprehendText to meaning, such as positive or negative sentiment
Amazon TextractScanned documents to text, forms and tables
Amazon RekognitionImages and video to labels, including unsafe content flags
Amazon LexConversations: chatbots and voice bots that understand intent
Developer tools, cloud desktops, AWS Amplify and AWS IoT Core →
NeedService
A full, persistent Windows desktop joined to Active DirectoryAmazon WorkSpaces
One desktop application streamed to a browser, no data on the deviceAmazon AppStream 2.0 (now called Amazon WorkSpaces Applications in AWS documentation)
Internal websites and SaaS apps only, no VPN, no software on the laptopAmazon WorkSpaces Secure Browser
Full-stack web and mobile app with Git-based deploys and pull request previewsAWS Amplify
Connect thousands of devices securely and route their messagesAWS IoT Core

Chapter 10

Billing, Pricing & Support

Key takeaways

Common trap

Quick reference

EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware →
OptionWhen it fits
On-Demand InstancesNo commitment; short, spiky or unpredictable work that must not be interrupted
Spot InstancesLowest cost for flexible, interruption-tolerant work; AWS can reclaim the capacity
Compute Savings PlansHourly spend commitment that applies across instance families, Regions, EC2, Fargate and Lambda
EC2 Instance Savings PlansCommitment locked to one instance family in one Region
Standard or Convertible Reserved Instances1-year or 3-year term; Convertible can be exchanged for other attributes for a smaller discount, Standard cannot be exchanged
On-Demand Capacity ReservationsGuaranteed capacity in one Availability Zone with no fixed term; not a discount
Dedicated HostsA whole physical server with socket and core visibility for bring-your-own per-core licenses
Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer →
ToolWhat it answers
AWS Pricing CalculatorWhat will a planned architecture cost, upfront, monthly and yearly, before we build it
AWS Cost ExplorerWhat did we actually spend over past months, what is the trend and what is the forecast
AWS BudgetsAlert us by email or Amazon SNS when actual or forecasted cost or usage crosses a threshold
AWS Cost and Usage ReportsThe most detailed line items by resource, hour and tag, delivered to our own S3 bucket for Athena or Amazon Quick
AWS Compute OptimizerWhich resources are oversized, based on actual utilization metrics