Free AWS Study Guides & Cloud Resources

Use these free AWS study guides to build cloud knowledge through learning paths, architecture notes, practical examples and original exercises. Choose the area that matches your goal, then explore the relevant Premium PDFs for additional preparation material.

Browse All AWS Premium PDFs →

Want free reference PDFs? Email freelearning@ciscoforall.com with your exam code and name. We will send an available older reference file free of charge. Availability varies; see the request section below.

AWS Exam-Specific Study Guides

Choose your exam code below to open its free study post, explore preparation topics and find the matching Premium PDF. These guides cover several exam versions, including older reference material; check the exact code against your intended exam before using a guide.

Choose a learning path that matches your goals

Learning path	Topics to develop	Practical activity	Premium resource
Cloud fundamentals	Cloud value, responsibility, basic architecture and resource costs	Explain which tasks remain with the customer in a fictional application deployment.	Cloud Practitioner CLF-C02
Solutions architecture	Reliability, performance, access, storage choices and cost trade-offs	Compare two designs for a small business application and explain the failure cases.	Solutions Architect SAA-C03
Application development	Application identity, deployment, data access and operational evidence	Write a workflow showing how an application reads information and handles a failed request.	Browse the AWS Premium directory for your target.
Cloud operations	Monitoring, configuration, recovery and controlled changes	Create a troubleshooting timeline and a recovery test for an example workload.	Browse the AWS Premium directory for your target.
Data and specialist learning	The services and constraints relevant to your chosen role	Document a data flow, its access boundaries and the questions that need specialist verification.	Match your intended exam with a listed resource.

Turn an exam guide into a useful study checklist

Choose your target certification and check its current exam guide before deciding what to study. The learning paths above organise broad skills. They do not replace the objectives for your exact exam. Record the intended exam code, your experience and the tasks you want to perform. If an older PDF uses earlier terminology, map its concepts to the current scope rather than assuming every detail is still assessed.

Use one row per topic in your study tracker. Add columns for a plain-language explanation, a diagram or activity, evidence of understanding and the next review date. A topic is ready for review when you can apply it to a new scenario and explain why your solution fits. Being familiar with a service name is an early step, not a complete measure of readiness.

Cloud architecture notes: start with requirements

Imagine a small business moving an application into the cloud. Before selecting a service, write down its traffic pattern, data sensitivity, recovery expectations and administration needs. An application used only during office hours has different requirements from a public service that must remain available throughout the day. Explain the requirement first, then compare designs.

Distinguish durable storage from application availability. Keeping data safely stored does not guarantee that an application can serve users during a failure. Similarly, having several application instances does not recover a document that someone accidentally deleted. Treat backup, recovery and availability as separate questions in your design notes.

Security, identity and responsibility

Create a responsibility table for every scenario: provider responsibilities, customer responsibilities and shared tasks. The division changes with the service being used. Access permissions, application configuration and data handling still require deliberate decisions. Avoid assuming that using a managed service removes all customer security work.

Practise least privilege with fictional roles. Describe what an application needs to read or write, then explain why unrelated permissions should be excluded. Separate the identity of a person from the identity of an application. Your goal is to understand the purpose of a permission, not simply recognise a policy name.

A practical AWS study routine

Session 1: review one topic from your checklist and write a brief explanation in your own words. Session 2: compare two possible solutions to a small business requirement. Session 3: draw the architecture and trace how users, applications and data interact. Session 4: review an original exercise and record the reasoning behind your answer.

Repeat this cycle across your target topics. Keep a notebook with a scenario, your chosen approach, an alternative and the trade-off. When using a cloud account for practice, check the applicable charges and remove resources after the exercise. You can begin with diagrams and offline design exercises before creating services.

Original AWS learning exercises

Exercise: a team needs to recover accidentally deleted business records. Would adding more application instances solve the problem? Discussion: additional instances may help availability, but data recovery needs an appropriate recovery mechanism.

Exercise: a workload runs only occasionally. What would you compare before choosing its deployment design? Discussion: consider usage pattern, operational work, performance requirements and total cost rather than selecting a familiar service automatically.

Exercise: an application needs access to one dataset. Should it receive broad administrative permissions? Discussion: identify the required actions and resources and design the narrowest practical access. These exercises are original learning scenarios, not questions copied from a live exam.

Compute and storage: select around the workload

Start with the application requirement. Describe when it runs, how demand changes, where information is stored and how much administration the team can manage. Compare an approach that gives the team more control with one that transfers more operational work to a managed service. Your notes should explain the trade-off rather than simply name the option you remember.

Separate temporary application state from information that must survive a failure. Imagine that an application instance stops unexpectedly. Which data can be recreated, and which data needs durable storage and recovery protection? Then consider accidental deletion. A reliable storage system and a useful recovery strategy address different problems, so write a test for each.

For a document-sharing application, identify the data owner, permitted readers, update process and retention needs. Describe how you would prevent unnecessary access and recover a previous document. This small example connects storage, identity and operations without requiring a large list of services.

Networking and access: trace a single request

Draw the path from a user to an application and from the application to its data. Identify which parts should be reachable externally and which should remain restricted. Record the expected source, destination and purpose of every connection. Public reachability should follow an application requirement, not an assumption that every component needs it.

When a request fails, investigate one stage at a time. Check the intended name, destination, route, access conditions and application behaviour. Record what a successful test demonstrates and what remains unknown. A working front-end connection does not prove that the application can read its data or complete the user task.

Give the application a fictional identity with the smallest useful access scope. Compare it with a human administrator identity. Explain why the application should not automatically receive the administrator’s permissions. Your diagram should show the resource and actions needed, with unrelated access excluded.

Reliability and recovery: define what success means

Write down the business impact of an unavailable application and lost information. Decide how much interruption and data loss the example business can tolerate, then compare designs against those expectations. An application used for occasional internal reporting may have different needs from a customer-facing ordering service.

Use three separate scenarios: an application component fails, a user deletes a record and a configuration change causes an error. For each, describe detection, recovery action and a test proving the outcome. Do not use the same vague statement, such as “add redundancy”, as the answer to every problem.

A recovery plan needs a tested process. In an offline exercise, write the order of restoration, required permissions, dependencies and checks. A backup that exists but has never been restored leaves unanswered questions. Explain how the team would know that recovered information is complete and that the application works with it.

Cloud concepts that are easy to confuse

Concept	Useful distinction	Question to practise
Availability and recovery	Keeping a service accessible differs from restoring lost information.	Can the design handle both a component outage and accidental deletion?
Authentication and authorisation	Establishing identity differs from granting resource access.	What can this identity actually read or change?
Scaling and efficiency	Adding resources differs from using appropriate resources well.	Does extra capacity address the actual bottleneck?
Monitoring and diagnosis	Observing a symptom differs from explaining its cause.	Which evidence narrows the failure location?
Managed service and customer responsibility	Provider management does not remove every customer decision.	Who owns access, configuration and data protection in this scenario?

A six-week AWS practice plan

Stage	Learning focus	Exercise	Expected output
Week 1	Scope and cloud foundations	Build a topic checklist and a responsibility example.	A resource index and a glossary explained in your own words.
Week 2	Compute and storage decisions	Compare two deployments for a small application.	A diagram and written reasons for the choice.
Week 3	Networking and identity	Trace a request and specify narrow application access.	An access matrix and a connection path.
Week 4	Reliability and recovery	Work through component failure and accidental deletion.	Separate availability and recovery tests.
Week 5	Monitoring and cost awareness	Investigate a fictional failed request and resource usage.	An evidence timeline and a list of cost drivers.
Week 6	Mixed review	Apply earlier concepts to an unfamiliar business scenario.	A justified design and an updated error log.

AWS troubleshooting study checklist

Symptom	Evidence to collect	Next learning question
Users cannot reach the application	Destination, name resolution, expected route and application status	At which stage does the observed result first differ from the intended path?
Application cannot read its data	Application identity, requested action, resource scope and error details	Is access appropriate for the actual task?
Performance degrades during busy periods	Demand pattern, response times and constrained component	Would capacity, configuration or application design address the bottleneck?
Resource spending exceeds expectations	Usage, active resources, data transfer and operational needs	Which resource is necessary, and which can be removed or redesigned?
Backup is present but restoration fails	Dependencies, permissions, restoration sequence and verification result	What was missing from the recovery test?

Build an AWS learning portfolio from three small projects

Project one is a static architecture proposal for a small business application. Include the user journey, stored information and access boundaries. Describe an alternative and why you did not select it for this scenario. The quality of the explanation matters more than the number of services in the diagram.

Project two is a recovery worksheet. Describe the failure, information at risk, restoration sequence and acceptance tests. Include accidental deletion as well as an unavailable component. Project three is an operations note containing a symptom, collected evidence, a supported explanation and the proposed corrective action.

Keep these projects together with your topic tracker. Return to them after learning a new concept and revise the reasoning. If you use a live cloud account, check costs before creating resources and clean up the lab afterwards. Diagrams and written exercises provide a useful starting point when a live account is unavailable.

A simple review routine that turns reading into practice

Choose one topic and explain it without reading your notes. Complete a small activity, then record the evidence and the reason for the result. If you cannot explain the outcome, return to the principle behind it before repeating the same task. This makes review active rather than a second reading of familiar paragraphs.

Use an error log with the scenario, incorrect assumption, supporting evidence and lesson learned. Create a fresh example with different details to check that the principle is understood. Review the log every week and use it to choose the next topic that needs attention.

The six-week plan is a flexible example. Extend a stage when your experience or available practice time requires it. Readiness depends on what you can explain and apply, not simply the number of days spent studying. Keep matching your plan to the current objectives for your intended exam.

Request free AWS reference PDFs by email

Email freelearning@ciscoforall.com with the certification name, exam code and topics you need. Use “AWS Free Reference PDF Request” as the subject. We will reply with an available older reference PDF free of charge. Not every exam has a free file. Older resources may cover previous versions, so use them for background learning and compare their scope with your intended exam. We share only resources we are permitted to distribute. You can read the original notes and exercises on this page without requesting a file.

Explore AWS Premium PDFs

Browse the AWS Premium PDF directory and select your exam code. Explore the product details and question count to find a resource that matches your learning goals.

Related Premium PDFs: Cloud Practitioner CLF-C02 · Solutions Architect SAA-C03. Select your exam to explore the Premium PDF.

Frequently asked questions

Where should a beginner start?

Begin with cloud terminology and a learning goal. Follow the objectives for your selected certification and practise explaining common business scenarios.

Can these notes support SAA-C03 study?

They provide background learning about architecture decisions. Match all additional material to the scope and version of your intended exam.

Is the content on this page free?

Yes. The original study notes, exercises and preparation advice are free to read. Premium PDFs are available separately through our product pages.

Can I request a free PDF for every exam?

You can ask about your exam, but files depend on availability. Include the exam code and name so we can identify the reference material you need.

Does this page guarantee an exam result?

No. Results depend on your knowledge, practical skills and preparation.

Ready to explore more AWS study material?

Browse all AWS Premium PDFs, choose your exam and explore the available preparation material.