AWS Cloud Practitioner (CLF-C02) Cheat Sheet

The core AWS services, concepts, and pricing/support facts worth memorising for CLF-C02 β€” on one page.

Entry-levelQuick referenceCLF-C02
⏱️ Reference

Much of Cloud Practitioner is knowing which AWS service does what. Nail these core services and concepts and most scenario questions become easy.

In short: This cheat sheet collects the most commonly tested AWS Cloud Practitioner essentials: core services (EC2, S3, Lambda, VPC, RDS, DynamoDB, IAM), the shared responsibility model, AWS global infrastructure (regions, availability zones, edge locations), the Well-Architected Framework pillars, and the AWS support plans.

Global infrastructure

Regions are geographic areas; each contains multiple Availability Zones (AZs) β€” physically separate datacenters. Spreading across AZs gives you high availability. Edge locations cache content close to users (used by CloudFront, AWS's CDN).

πŸ”‘ Shared responsibility, in one line

AWS is responsible for security OF the cloud (hardware, regions, the physical infrastructure); you are responsible for security IN the cloud (your data, identity/access, OS patching where applicable, and configuration). It's the single most-tested idea on the exam.

Core services by category

You need to know what each service is for, not how to configure it.

Frequently tested AWS services.
CategoryServiceUse it for
ComputeEC2Resizable virtual servers you manage (IaaS)
ComputeLambdaRun code without managing servers β€” serverless, pay per execution
ComputeElastic BeanstalkDeploy and run web apps without managing the platform (PaaS)
ComputeECS / EKSRun containers (Amazon's container service / managed Kubernetes)
StorageS3Virtually unlimited object storage (files, images, backups, data lakes)
StorageEBSBlock storage volumes (virtual disks) attached to EC2
NetworkingVPCYour own isolated private network inside AWS
NetworkingRoute 53DNS and domain registration
NetworkingCloudFrontContent delivery network (CDN) using edge locations
DatabaseRDSManaged relational databases (MySQL, PostgreSQL, etc.)
DatabaseDynamoDBFully managed NoSQL database, single-digit-ms latency
SecurityIAMManage users, groups, roles and permissions (who can do what)
πŸ’‘ Well-Architected Framework β€” the 6 pillars

AWS's design best-practice framework has six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. If a question asks about designing well on AWS, it's usually pointing at one of these.

Pricing, cost, and support tools

Domain 4 is small but easy marks if you know these.

Key CLF-C02 pricing, cost, and support tools.
Tool / conceptWhat it does
Pay-as-you-goAWS's core pricing model β€” pay only for what you use, no upfront cost
AWS Pricing CalculatorEstimate the cost of AWS services before you deploy
AWS Cost ExplorerVisualise and analyse your actual spending over time
AWS BudgetsSet custom cost/usage budgets and get alerts when you approach them
AWS Trusted AdvisorRecommendations across cost, security, fault tolerance, performance, limits
CloudWatchMonitoring β€” metrics, logs, and alarms for your resources
CloudTrailRecords API activity in your account for audit and governance
Support plansBasic (free), Developer, Business, Enterprise On-Ramp, Enterprise
βœ… Key takeaways
  • Regions contain Availability Zones (separate datacenters); edge locations serve CloudFront.
  • AWS secures OF the cloud; you secure IN the cloud (your data, identity, config).
  • Core services: EC2 (servers), Lambda (serverless), S3 (object storage), VPC (network), RDS (SQL), DynamoDB (NoSQL), IAM (access).
  • Well-Architected = 6 pillars (Operational Excellence, Security, Reliability, Performance, Cost, Sustainability).
  • Support plans: Basic β†’ Developer β†’ Business β†’ Enterprise On-Ramp β†’ Enterprise.

Frequently asked questions

What are the core AWS services for Cloud Practitioner?

Compute (EC2, Lambda), storage (S3, EBS), networking (VPC, Route 53, CloudFront), databases (RDS, DynamoDB), and security/identity (IAM).

What is the AWS shared responsibility model?

AWS is responsible for security OF the cloud (physical infrastructure, hardware, regions); the customer is responsible for security IN the cloud (data, identity and access, configuration, and OS patching where applicable).

Independent study resource. Not affiliated with, authorized, endorsed by, or sponsored by CompTIA, Amazon Web Services, Microsoft, or ISC2. All trademarks are the property of their respective owners and are used here for identification only. All practice questions are original.