1. Home
  2. TintoDev Academy
  3. AWS
  4. Guides
TintoDev Academy · Guides

AWS Cloud Practitioner certification: how to prepare for it step by step

In short

AWS Certified Cloud Practitioner is the entry-level AWS certification and covers cloud concepts, security, the core services and the billing model, not advanced configuration skills. With five to eight hours a week and some technical background, preparation usually takes four to six weeks, combining a course, hands-on practice in your own account and practice exams. Price, duration and passing score change, so confirm them on the official AWS Certification page before booking.

What Cloud Practitioner is and who it makes sense for

It is the foundational-level AWS certification. It shows that you understand what the cloud is, what AWS offers, how security is split between AWS and the customer and how billing works. It does not ask you to write code or configure complex infrastructure, which is why it makes sense both for technical profiles who are starting out and for people in sales, finance, product or project management who work with teams that use AWS.

If you already deploy applications on AWS every day, you can skip it and go straight to an Associate-level exam. If you are starting out, it gives your study a structure and a shared vocabulary with the rest of the team. At TintoDev we deploy on AWS, and the most common confusion we see in new team members is not technical: it is not knowing which service to use or how much it will cost. This certification targets exactly that.

What it covers, broadly

The official exam guide organises the content into four areas. The weight of each one, the question format and other details change between versions, so download the current guide from the AWS Certification page before you start and use it as a checklist. For price, duration and passing score, do not rely on blogs or videos: always check them at the official source.

Questions usually describe a business scenario and ask for the service or concept that fits best. That is why memorising names is not enough: you need to know what each service is for and how it differs from the ones that look similar. A company that wants to cut the cost of idle servers, another that needs to keep backups for years: behind each case there is a specific concept the exam expects you to recognise.

  • Cloud concepts: benefits, global infrastructure and best-practice frameworks.
  • Security and compliance: shared responsibility, IAM and security services.
  • Technology and services: compute, storage, databases and networking.
  • Billing, pricing and support: payment models, cost tools and support plans.

Cloud concepts and security

Start with what justifies the cloud: paying for usage instead of buying servers, scaling with demand and reaching other regions without building a data centre. Learn the difference between a region, an availability zone and an edge location, and the pillars of the Well-Architected Framework. They are simple ideas, but many questions depend on telling them apart.

In security, the central concept is the shared responsibility model: AWS protects the physical infrastructure and the managed service layer, and you are responsible for your data, your permissions and your configuration. Take your time with IAM: users, groups, roles, policies, the principle of least privilege and why the root user is not used for daily work and must have MFA enabled.

Core services worth knowing

AWS has more than two hundred services, but the exam focuses on the ones that show up in almost any architecture. You do not need to configure them in depth, but you do need to know when to pick each one. A good exercise is to take each service and write one sentence on what problem it solves and which service it is often confused with.

As you study each service, think about shared responsibility: managing an EC2 instance, where you patch the operating system, is not the same as using Lambda or RDS, where AWS takes care of much of the maintenance. That kind of comparison is exactly what the exam scenarios ask about.

  • Compute: EC2, Lambda and container services such as ECS.
  • Storage: S3 with its storage classes, and EBS.
  • Databases: RDS for relational data and DynamoDB for key-value.
  • Networking and content delivery: VPC, Route 53 and CloudFront.
  • Monitoring and auditing: CloudWatch and CloudTrail.

Billing, pricing and support

This area gets underestimated because it looks administrative, and it is the one that helps most later on for anyone working with AWS. Learn the compute purchasing models (on demand, usage commitments such as Savings Plans or Reserved Instances, and Spot Instances) and when each one makes sense. Also understand how data transfer is billed and why outbound traffic to the internet is often what surprises people on the bill.

Get to know the tools: AWS Budgets for alerts, Cost Explorer to analyse spending, the pricing calculator to estimate before building and AWS Organizations for consolidated billing. Also review the support plans and what each one includes in broad terms, without memorising prices, which also change. What matters is knowing which plan a company would choose based on how much it depends on AWS to operate.

Week-by-week study plan

The plan in the table assumes five to eight hours a week and some familiarity with basic technical concepts. If you have never worked in tech, add one or two weeks at the start for general networking and server vocabulary. If you already use AWS, you can compress it by half and focus on billing and support, which is what you see least in daily work.

Use a course as your backbone, the official exam guide as your checklist and AWS Skill Builder for the free material from AWS itself. Write your own notes per service instead of rereading slides: putting into your own words what each thing does is the fastest way to spot what you still do not understand.

Practising on the free tier without surprises

Reading about S3 is not the same as creating a bucket, uploading a file and watching the permissions fail. Create your own AWS account and practise, but before launching any resource, set up a billing alert with AWS Budgets and enable MFA on the root user. The free tier terms have changed over time, so check what your account includes on the official page before assuming something is free.

In the last two weeks, take timed practice exams and review every wrong answer until you understand why the right one is right. Note the topics where you miss the most and go back to them before the next attempt. Avoid so-called dumps with leaked questions: they violate AWS policies and leave you with a certificate you cannot back up in an interview.

  • Create a budget with an email alert on day one.
  • Practise with an IAM user or role, never with the root user.
  • Delete your resources at the end of every session.
  • Check the billing console once a week.

The next step: Solutions Architect Associate

Cloud Practitioner gives you the map; AWS Certified Solutions Architect Associate asks you to design with it. It is the natural next step for anyone building on AWS, and it requires combining services to meet availability, security, performance and cost requirements at the same time, in far more detailed scenarios. What you studied for Cloud Practitioner is not wasted: it is the vocabulary everything else is built on.

Before taking it, deploy something real: a web application with its database, a domain and properly configured permissions. The jump in difficulty between the two levels is significant, and hands-on practice is what bridges it. If your work leans towards data, development or AI, also look at the other certifications AWS offers; the official page lists the current ones.

Six-week plan at five to eight hours per week (adjust it to your time)
WeekFocusSuggested practice
Week 1Cloud concepts, global infrastructure and Well-ArchitectedCreate the account, enable MFA and set up an AWS Budgets alert
Week 2Shared responsibility, IAM and security servicesCreate a user and a role with least-privilege permissions
Week 3Compute, storage and databasesLaunch and terminate an EC2 instance; host a static site on S3
Week 4Networking, monitoring and other servicesCreate a Lambda function and review its metrics in CloudWatch
Week 5Billing, pricing and supportEstimate a simple architecture with the pricing calculator
Week 6Review and practice examsTimed exams and review of every mistake

Where the courses are

Frequently asked questions

Do I need technical experience for Cloud Practitioner?

It is not required. The exam tests concepts and does not ask you to configure or code anything, which is why business profiles take it too. With some background in networking and servers, studying goes faster.

How long should I study for the exam?

At five to eight hours a week, four to six weeks is usually enough if you have some technical background. If you are starting from zero, plan for one or two extra weeks. If you already use AWS at work, half that time may be enough.

How much does the Cloud Practitioner exam cost and how long is it?

Check the official AWS Certification page before booking. Price, duration, number of questions and passing score can change between exam versions and by country. Any figure published elsewhere may be out of date.

Should I go straight to Solutions Architect Associate?

If you already work with AWS every day, yes, you can skip Cloud Practitioner. If you are starting out, the foundational certification gives you the service and billing basics that Associate takes for granted. It also works as a short first goal to build a study habit.

Are practice exams enough to pass?

Not on their own. They help you measure your level and get used to scenario questions, but if you only memorise answers, any question worded differently leaves you stuck. Combine them with a course, the official guide and practice in your own account.

Some links in TintoDev Academy are affiliate links. If you make a purchase through them, TintoDev may earn a commission at no additional cost to you.