Where to Start on AWS as a Beginner: A First-Week Plan
A beginner asked which AWS services to learn first and in what order. Here is a one-week plan: secure your account, learn S3 and Lambda, connect them, then choose your next direction, with real examples from Edmunds and Square Enix.
Under my last article on Builder Center, a beginner asked which AWS services to learn first and in what order. It is the right question, and it deserves a full answer instead of a one-line reply. This is the plan I would follow if I were starting this week.
The idea is simple: learn two services properly, connect them, and only then widen out. AWS has hundreds of services. You do not need most of them to build something real.
Before any service: protect your account
Do this first, even if you are impatient to build.
- Turn on multi-factor authentication for the root user, then stop using root for daily work.
- Create an IAM user or role for yourself. IAM is how AWS decides who can do what in your account, and working through it from day one saves you from bad habits.
- Set a budget alert in AWS Budgets so a forgotten resource never becomes a surprise bill.
This takes an hour and it is the step most beginners skip.
Days 1 and 2: Amazon S3
S3 stores files in the cloud. You put files, which AWS calls objects, into containers called buckets, and you can get them back from anywhere with the right permissions. Images, documents, backups, website assets: S3 holds all of it.
A real problem S3 solved. Edmunds, the car shopping site, rebuilt its photo handling on a serverless setup that used S3 for object storage. According to AWS’s published case study, the company saved $100,000 in its first year and reduced photo storage from 60 terabytes to 40.
Your hands-on task: create a bucket, keep it private, upload a file, and download it again. Then try one permission change so you see how access control works.
Days 3 and 4: AWS Lambda
Lambda runs your code when something happens, such as a file upload, an API request, or a schedule. You do not set up or manage a server. You write the function, and AWS runs it when the event arrives and charges you for the time it runs.
A real problem Lambda solved. Square Enix, the maker of Dragon Quest and Final Fantasy, had a scaling challenge with the popular in-game screenshot feature in Dragon Quest X. After moving to Lambda, AWS’s case study reports near-instant screenshot processing and about 95 percent lower costs.
Your hands-on task: write a small Python function and test it from the console. Keep it simple. Print a message and return.
Day 5: connect the two
Now combine them, because this is where it starts to feel like building. Set up an S3 trigger so that every time you upload a file to your bucket, your Lambda function runs and prints the file name.
That single pattern, storage that fires off code, is the core of a huge number of real systems, including the Edmunds setup described above. When you see your function log fire after an upload, you will understand serverless better than a week of reading would teach you.
Days 6 and 7: decide what comes next
Once S3 and Lambda feel comfortable, pick one direction based on what you want to build:
- Servers and networks: EC2, with basic VPC ideas like subnets and security groups.
- Data: DynamoDB or RDS for databases.
- Visibility: CloudWatch for logs and monitoring, which you will need for everything else.
- AI features: Amazon Bedrock, once you have a small project to attach it to.
Let a real project pull you into these. It is far easier to learn a service when you need it for something.
Where Builder Center fits
You do not have to do this alone or on your own bill. The free sandbox workshops here give you a pre-provisioned AWS account for the exercise, and the hackathons and community Spaces are where you can ask questions. Badges for publishing articles, commenting, and keeping a streak are a bonus.
My suggestion: write a short article after each service you finish. Explaining what you built is the fastest way to find the parts you did not actually understand, and it helps the next beginner who is stuck where you were.
Your turn
Tell me in the comments what you plan to build first, and I will point you to the part of this plan that fits.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article