AWS Builder Center

Stop Collecting AWS Services. Start Building Receipts

Learning AWS often becomes a race to complete courses, earn badges, and memorize services. A Build Receipt is a simple way to document every project you create, the services you used, the problem you solved, the challenges you faced, and what you learned. Over time, these records become a practical portfolio of your real AWS experience.

Why "services learned" is the wrong metric

Most people learning AWS follow the same loop: read about EC2, move to S3, then Lambda, then DynamoDB, and so on. After a while you can define what each service does. That's not the same as knowing when to reach for it.
Ask yourself this, could you talk through a real project where you used S3? Not "it stores objects," but why you picked it over the alternatives, what broke along the way, and how it talked to the rest of your stack. If the honest answer is no, that's the gap a Build Receipt is meant to close.

What a Build Receipt actually is

It's a short note you write right after finishing a project, while the details are still in your head. Nothing formal, no template you have to fight with. Five things, answered honestly:
  1. What did you build? One or two sentences, no fluff.
  1. Which services did you actually touch? Not what the docs say the service can do — what you used.
  1. What problem was it solving? Even a small, made-up problem counts.
  1. Where did it go wrong? This is usually the part worth keeping.
  1. What do you understand now that you didn't before?

Example

Say you built a small serverless app that lets users upload a photo and get a thumbnail back.
  • Services: S3, Lambda, API Gateway, DynamoDB
  • Problem: Needed image uploads without standing up a server
  • Challenge: Lambda kept getting  AccessDenied  hitting the S3 bucket — turned out to be a missing resource-level permission in the IAM role, not the bucket policy
  • Takeaway: IAM debugging is mostly about reading the error message literally instead of assuming you know what it means
That whole thing takes five minutes to write down. It also tells you more than "finished the Lambda module."

Why bother

Certifications tell people you sat through material. They don't tell anyone (including you) what you can actually do with it. A stack of Build Receipts does something different: after ten or fifteen projects, you have a running log of the services you've genuinely worked with, the mistakes that taught you the most, and roughly how your skills have moved. That's the raw material for a portfolio page, a GitHub README, or just something concrete to say in an interview instead of listing service names.

The actual shift

You don't need to know every AWS service that exists. Nobody does. What matters is being able to combine two or three of them to solve something real.
So the useful question isn't "how many services have I learned this month?" It's closer to "what did I build with them, and what went sideways?"
Write the receipt. Keep it short. Do it every time.
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