AWS Builder Center

Builder Center

AWS Cloud Practitioner Domain 1: Cloud Concepts Explained Simply (A Student's View)

A simple, student-friendly guide to Domain 1 of the AWS Cloud Practitioner exam (CLF-C02): why the cloud, how to design well, how to migrate, and how cloud costs work.

This is post 1 of 4 in my series on the AWS Certified Cloud Practitioner exam (CLF-C02). Domain 1 is "Cloud Concepts" and it is 24% of the scored content. It's less about services and more about the big ideas, so I'm using simple pictures to remember them.

1. Why the cloud?

Think of electricity. You could own a generator and pay for it all year, or you could plug into the power grid and pay for what you use. The cloud works like the grid.
The main benefits I need to know:
  • Agility: try ideas quickly, without waiting weeks for hardware
  • Elasticity: use more when you need it and less when you don't
  • High availability: the system keeps running even if something fails
  • Global reach: deploy close to users around the world
  • Economies of scale: AWS serves so many customers that costs per unit go down

2. Designing well: the 6 pillars

The AWS Well-Architected Framework is a set of best practices, organized in six pillars. I picture them as building a house:
  • Operational excellence: running the house smoothly every day
  • Security: the locks and the alarms
  • Reliability: the house recovers after a storm
  • Performance efficiency: the right-sized rooms and appliances
  • Cost optimization: not paying for rooms nobody uses
  • Sustainability: using energy wisely
There is also a free AWS Well-Architected Tool that reviews a workload against these pillars.

3. Moving to the cloud

Organizations move for reasons like less business risk, better efficiency and more revenue. The AWS Cloud Adoption Framework (CAF) helps plan the journey by looking at it from different perspectives, both business and technical.
Common migration strategies are known as the "R"s:
  • Rehost ("lift and shift"): move as-is, the fastest way
  • Replatform: make small changes while moving
  • Refactor: redesign the application to use the cloud better
  • Repurchase: switch to a different product, like a SaaS tool
  • Retire: switch off what you no longer need
  • Retain: leave it where it is for now
To move very large amounts of data when the network would be too slow, AWS has the Snow Family, like AWS Snowball. Think of it as a moving truck for data. Database replication is another option to move databases with little downtime.

4. Cloud economics

  • Fixed costs: you buy hardware upfront and pay whether you use it or not
  • Variable costs: you pay only for what you use
Moving from fixed to variable cost is a core idea. Other ways to save are right-sizing (choosing the correct size of resources), automation and managed services, where AWS handles routine work for you.

My takeaway

Domain 1 is about the language of the cloud. If a question mentions paying only for use, think variable cost. If it asks about good design, think of the six pillars. If it talks about moving, think of the CAF and the "R"s.
The exam content can be updated, so check the official guide:  https://docs.aws.amazon.com/aws-certification/latest/cloud-practitioner-02/cloud-practitioner-02-domain1.html 
If you were building a small student project, which of the six pillars would you care about first?
# aws-certification# cloud-practitioner# cloud-concepts# fundamentals# student-builders
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article