AWS Certified Cloud Practitioner (CLF-C02)

AWS Cloud Practitioner Study Guide: CLF-C02 Essentials

10 min read15 July 2026

An effective AWS Cloud Practitioner study guide should help you explain why organisations use cloud computing, distinguish common AWS services, identify security responsibilities and interpret basic pricing choices. These are the foundations of CLF-C02, the exam for the AWS Certified Cloud Practitioner credential. Start with the shared responsibility model, Regions and Availability Zones, then connect compute, storage, networking and database services to straightforward business requirements. Finally, revise billing tools and purchasing options. The aim is not to memorise every AWS product: it is to recognise which concept or service best answers a clearly described need and why the alternatives do not.

This reference organises AWS cloud computing basics around the decisions that commonly cause confusion: elasticity versus scalability, Amazon EC2 versus AWS Lambda, Amazon S3 versus Amazon EBS, and customer security duties versus AWS duties. Use it alongside the current official CLF-C02 exam guide, which defines the scope and may be updated. For structured learning, the Erudex [AWS Certified Cloud Practitioner (CLF-C02) course](/courses/aws-cloud-practitioner) and [practice tests](/practice) can support revision. An Erudex course certificate is separate from AWS certification; earning the AWS credential requires passing the official AWS exam. Build confidence by explaining each distinction in your own words rather than memorising answer patterns.

Key points

  • Organise CLF-C02 revision around the official domains and explain concepts in your own words.
  • Choose services by workload requirements, not by name recognition alone.
  • Security duties vary by service, but customer responsibility never disappears.
  • Separate pricing commitments, cost analysis and budget alerts when reviewing billing scenarios.

Understand the cloud concepts and exam domains first

CLF-C02 has four content domains: Cloud Concepts, Security and Compliance, Cloud Technology and Services, and Billing, Pricing and Support. Their published weightings are 24%, 30%, 34% and 12%, respectively; confirm these against the current official exam guide when planning revision. Cloud fluency starts with on-demand resources, measured usage and the ability to provision capacity without purchasing physical infrastructure. Scalability means adjusting capacity to meet demand, while elasticity emphasises expanding and contracting resources as demand changes. Neither means that costs automatically fall: architecture, purchasing choices and resource management still determine the financial outcome of a cloud deployment.

Understand how AWS global infrastructure supports availability and performance. A Region is a separate geographical area containing multiple Availability Zones. Each Availability Zone comprises one or more discrete data centres with redundant infrastructure. Deploying across Availability Zones can help an application tolerate a zone failure; using multiple Regions can address requirements such as disaster recovery or geographical reach. Edge locations bring selected services closer to users, but they are not substitutes for Regions. Connect these concepts to the AWS Well-Architected Framework, whose six pillars help teams assess operational excellence, security, reliability, performance efficiency, cost optimisation and sustainability.

  • High availability reduces interruptions; fault tolerance aims to keep systems operating through failures.
  • Disaster recovery covers restoring service after a disruptive event.
  • Agility means delivering and changing resources more quickly.
  • Cloud benefits depend on appropriate design and ongoing management.

Choose between compute and networking services

Amazon EC2 provides virtual servers when workloads need control over operating systems and software configuration. EC2 Auto Scaling can adjust instance capacity, while Elastic Load Balancing distributes traffic across healthy targets. AWS Lambda runs code in response to events without requiring customers to provision or manage servers, although customers still manage their code, permissions and configuration. For containers, Amazon ECS provides container orchestration and Amazon EKS provides managed Kubernetes. AWS Fargate supplies serverless compute for supported ECS and EKS workloads. At this level, focus on these roles rather than detailed deployment commands or container cluster administration.

Amazon VPC provides a logically isolated network in AWS, with subnets, routing and connectivity controls. A public subnet has a route to an internet gateway, but that alone does not make every resource publicly reachable: addressing and security settings also matter. Security groups control traffic for associated resources, while network ACLs operate at the subnet level. Amazon Route 53 supplies DNS and related routing capabilities; Amazon CloudFront is a content delivery network that caches and delivers content through edge locations. AWS Direct Connect offers dedicated connectivity to AWS, whereas AWS Site-to-Site VPN provides an encrypted connection over the internet.

  • EC2: virtual servers with customer-managed guest operating systems.
  • Lambda: event-driven code execution without server provisioning.
  • ECS and EKS: container orchestration services.
  • CloudFront: content delivery; Route 53: DNS and traffic routing.
  • Security groups are stateful; network ACLs are stateless.

Match storage and database services to the workload

Amazon S3 is object storage for data such as documents, media, backups and data lakes. It is not a block device attached to a server. Amazon EBS provides block storage for EC2 workloads, with volumes scoped to an Availability Zone. Amazon EFS provides managed NFS file storage that multiple clients can access. Within S3, storage classes suit different access patterns, retrieval requirements and resilience needs; some archival classes involve retrieval delays and additional charges. Lifecycle rules can transition or expire objects according to policy. Distinguish durability, which concerns preserving data, from availability, which concerns being able to access it when required.

Amazon RDS manages common relational database engines, helping with tasks such as provisioning, patching and backups. Amazon Aurora is a relational database compatible with MySQL and PostgreSQL, available through Amazon RDS. Amazon DynamoDB is a managed NoSQL database supporting key-value and document data models. Amazon Redshift supports data warehousing and analytics, while Amazon ElastiCache provides managed in-memory caching. Choose based on the access pattern: transactions with relational structures point towards a relational database, whereas predictable key-based access may suit DynamoDB. Managed services reduce operational work, but customers still decide access permissions, data structures, retention requirements and appropriate configuration.

  • S3 stores objects; EBS provides block storage; EFS provides shared file storage.
  • RDS Multi-AZ deployments support availability; read replicas commonly support read scaling.
  • AWS Database Migration Service helps migrate databases.
  • AWS Storage Gateway connects on-premises environments with cloud storage.
  • AWS Backup centralises backup management across supported services.

Explain security responsibilities and identify the right tools

The shared responsibility model separates security of the cloud from security in the cloud. AWS protects the underlying facilities, hardware, networking and virtualisation infrastructure. Customers remain responsible for their data, access decisions and configuration, with specific duties changing by service. On EC2, customers generally patch the guest operating system and their applications. With Lambda, AWS manages the underlying servers and operating systems, while customers secure their application code, dependencies and permissions. Avoid absolute claims such as 'AWS handles all security for managed services'. Compliance is also shared: using an eligible AWS service does not automatically make a customer's workload compliant.

AWS Identity and Access Management controls access through identities and policies. Apply least privilege, prefer temporary credentials where appropriate, protect the account root user with multi-factor authentication and avoid using it for routine work. AWS IAM Identity Center supports workforce access across accounts and applications. For monitoring, distinguish Amazon CloudWatch metrics, logs and alarms from AWS CloudTrail records of account activity and API calls. AWS Config records resource configurations and can evaluate them against rules. Amazon GuardDuty detects potential threats, Amazon Inspector identifies supported workload vulnerabilities, and AWS Artifact provides access to compliance reports and selected agreements.

  • AWS KMS manages encryption keys; AWS Secrets Manager manages secrets.
  • AWS WAF filters web requests; AWS Shield provides DDoS protection.
  • Amazon Macie helps discover sensitive data in Amazon S3.
  • Encryption does not replace access control or careful configuration.
  • AWS Organisations service control policies limit permissions but do not grant them.

Compare pricing options and control cloud spending

AWS pricing depends on the service, Region, usage and purchasing model. Common cost drivers include compute duration, storage capacity, requests and data transfer. On-Demand pricing avoids a long-term usage commitment, while Savings Plans offer lower eligible rates in exchange for a consistent hourly spending commitment over a defined term. Reserved Instances provide billing discounts for matching usage; capacity reservation behaviour depends on their scope and offering. EC2 Spot Instances use spare capacity at discounted rates but can be interrupted, so they suit fault-tolerant workloads. Do not assume that every discount applies across all services or that a commitment is always cheaper for unpredictable usage.

Use AWS Pricing Calculator to estimate proposed workloads, AWS Cost Explorer to analyse spending and usage, and AWS Budgets to track thresholds and send alerts. A budget alert is not a universal spending cap, although budget actions can automate selected responses when configured. AWS Organisations supports consolidated billing across accounts, and cost allocation tags help attribute supported costs when configured and activated. Free Tier offers have eligibility conditions, time limits or usage limits that should be checked against current terms. For support questions, revise the current AWS Support plans and AWS Trusted Advisor capabilities using official documentation rather than memorising potentially outdated pricing tables.

  • Right-size resources and remove unused capacity before buying commitments.
  • Check data transfer charges for the actual traffic path.
  • Distinguish cost estimates, spending analysis and budget notifications.
  • Review support-plan features and eligibility in current AWS documentation.
  • Use cost allocation to connect cloud spending with teams or workloads.

Frequently asked questions

How should I use an AWS Cloud Practitioner study guide for revision?
Start with the official exam domains and mark each topic as confident, uncertain or unfamiliar. Work through unfamiliar concepts first, then practise service comparisons and short scenarios. For each incorrect answer, explain both why the correct option fits and why the alternatives do not. Keep a compact revision sheet for recurring confusions such as CloudWatch versus CloudTrail and S3 versus EBS. Revisit weak areas before attempting another timed question set.
Do I need coding or hands-on experience for CLF-C02?
CLF-C02 is a foundational exam, not a programming assessment. Its focus is recognising cloud concepts, service purposes, security responsibilities and commercial principles rather than writing code or building complex architectures. Limited hands-on exploration can make abstract concepts easier to remember, but extensive engineering experience is not required. If you use an AWS account for practice, check current pricing and eligibility terms, configure billing notifications and delete resources when finished. Notifications alone do not prevent charges.
Which AWS service distinctions should I prioritise?
Prioritise distinctions that connect directly to a requirement. Compare EC2 with Lambda for compute control and server management; S3, EBS and EFS for object, block and file storage; and RDS with DynamoDB for relational versus NoSQL data models. Also separate CloudWatch monitoring from CloudTrail activity records and AWS Config configuration tracking. Learn the primary purpose of each service first, then add one meaningful limitation or responsibility. This is more useful than memorising long product descriptions.
How can I tell whether I am ready for the AWS Certified Cloud Practitioner exam?
Readiness means being able to explain the exam objectives and answer unfamiliar scenarios consistently, not simply recognising questions you have already seen. Review practice results by domain and check whether errors come from missing knowledge, confused service names or overlooked wording. You should be comfortable discussing shared responsibility, infrastructure, core service selection and billing tools without notes. Check the official exam page for current delivery details, policies and assessment information before booking; no study resource guarantees a pass.

Study it properly: AWS Certified Cloud Practitioner (CLF-C02)

Master fundamental cloud computing architectures, security governance, and AWS core services for the CLF-C02 exam.

More on this subject

All articles · Sitemap