AWS Cloud Practitioner Essentials: 13 modules that teach you to talk to a client's IT team
AWS's beginner cloud course will not turn you into an infrastructure architect. It will help you keep up in your first meeting on a client's systems.
In brief
- AWS released a refreshed version on 24 June 2025, with 13 modules and new lessons on AI, machine learning and data analytics.
- The Skill Builder version runs 12 hours 45 minutes; the Coursera version is taught by Rudy Chetty and Morgan Willis.
- The associated exam only certifies a high-level understanding, so pair it with a small project of your own.
Study each module with one question in mind that you need to be able to answer when sitting with the client's IT team.
Graphic: FDE Times
AWS lists the AWS Cloud Practitioner Essentials course on Skill Builder at 12 hours 45 minutes, shorter than a sprint. If you are a developer about to deploy software into a client’s systems, it is time worth putting at the top of next quarter’s learning plan.
Why prioritise this course? For an FDE, code runs on infrastructure that belongs to someone else, and the client controls decisions about networking, access and budget. You need to be ready for those questions before you get to models or prompts. Without the language of the cloud, you can easily end up a spectator in your own project.
So treat the course as a minimum vocabulary. It does not teach you to build complex systems. It helps you understand what the people across the table are saying.
What does the course contain after the 2025 refresh?
On 24 June 2025, AWS announced a refreshed version of the course, with 13 updated modules and new lessons on AI, machine learning and data analytics. The new material matters to FDEs, because many deployments today involve bringing an AI system into a client’s existing infrastructure.
Amazon Web Services has also put the course on Coursera, taught by Rudy Chetty and Morgan Willis, at Beginner level. The modules run from Compute, Networking, Storage and Databases to Security, Pricing, Migration and Well-Architected. A section called “Cloud in Real Life” ties each concept to a business scenario, and the instructors demo directly in the AWS Management Console.
One easily missed detail: AWS aims the course at people new to the cloud, business staff, students and non-technical roles. That means a manager on the client side may have learned exactly this set of concepts. When you share the same vocabulary, meetings move much faster.
Idea one: a client’s infrastructure starts with networking and access
Imagine you are deploying an agent that reads internal documents for an insurance company. The IT team will very likely ask straight away where the data travels, which network zone it sits in, and who is allowed to read it. The Networking and Security modules give you a framework to answer clearly rather than in generalities.
The first thing to do on site is draw a simple diagram: where the data comes in, where it is processed, where the results go, and who grants permission for each arrow. Any step you cannot name is something to ask about before you write a line of code.
Idea two: cost is a design constraint
The Pricing module sounds dry, but one hypothetical figure is enough to show the price of skipping it. Suppose a server costing 2 USD an hour is left running from 8pm on Friday to 8am on Monday. That is 60 hours, or 120 USD, for a demo nobody used.
The sum itself is not large. The bigger loss is trust, because whoever approves the bill on the client side will ask you why. Before every demo, list each resource you have created, estimate its hourly cost and schedule it to shut down.
Idea three: your solution must fit the client’s migration path
The client may be moving gradually from its own servers to the cloud, and any solution that runs against that path will be set aside, however well it works. In customer discovery, ask directly which stage of the transition they are at.
In what order to study, and should you take the exam?
You need to sign in to study on Skill Builder. The platform offers more than 900 free self-paced courses. The Coursera version suggests about 4 weeks at 10 hours a week, on a flexible schedule.
The two figures are far apart: 12 hours 45 minutes is the duration AWS lists for the course, while 4 weeks at 10 hours a week is the pace Coursera suggests. When planning, go with the larger number, because you need extra time to open the Console yourself, redo the demos and note down terminology.
If you have never opened the AWS Management Console, start with the foundational modules, Compute, Networking, Storage and Databases, before moving on to Security, Pricing and Migration. If you have worked with the cloud for a few years, skim quickly and focus on the new AI material and the “Cloud in Real Life” scenarios.
The AWS Certified Cloud Practitioner exam lasts 90 minutes, with 65 multiple-choice or multiple-response questions, and costs 100 USD. AWS says candidates may have up to about 6 months of exposure to the AWS Cloud, but this is not required.
AWS also states plainly that the certification validates a foundational, high-level understanding of the AWS Cloud, its services and terminology.
Because the certificate only proves a high-level understanding, do not let it stand alone on your CV. Pair it with a small project, such as an API you deployed to AWS yourself, with a network diagram, a permissions table and a cost estimate.
When reading FDE job descriptions, if you see phrases such as “customer infrastructure” or “cloud deployment”, review the course material and have that small project ready to talk about in interviews.
Finishing the course will not make you an infrastructure specialist. But next time a client’s IT team starts talking about networking and permissions, you will understand what they mean and be able to ask the questions worth asking.