AWS Builder Center

Builder Center

From Lab Practical to Live Project: A Student's First Steps With AWS

From Lab Practical to Live Project: A Student's First Steps With AWS

Start with one problem, not hundreds of services. A simple, hands-on path for students to understand AWS, build a first Amazon S3 project, deploy a website, and share it, with cost-safety habits along the way.

Series: Lab-to-Live (1 article)

  1. 1
    From Lab Practical to Live Project: A Student's First Steps With AWS This article

Soham Deshmukh

AWS SBCL | Final Year Student | AWS Certified Solution Architect
Quick question before you read.
Have you ever heard the word AWS and thought, "Sounds important, but what can I actually do with it?"
If yes, you are exactly who I wrote this for. I'm Soham, a final-year B.Tech Information Technology student at Sanjivani College of Engineering. I recently spoke at Cloud Launchpad with AWS SBG, a beginner-friendly session where we started from zero: what AWS is, which service to pick first, and how to turn college practicals into real projects.
This article is the written version of that idea. No 50-service memorising. Just a simple path you can follow this week.

Which one sounds like you?

Pick the one that feels closest. Keep it in mind, we'll come back to it at the end.
  • I've heard of AWS but never opened it
  • I have a cloud or IoT practical coming up
  • I built a website but it only runs on my laptop
  • I want a project for my GitHub or resume

What is AWS, really?

Think of AWS (Amazon Web Services) as a huge toolbox.
You don't need every tool for every job. If you're building an app, you just pick what you need:
  • Compute: somewhere to run your code
  • Storage: somewhere to keep files
  • Database: somewhere to keep information
  • Access control: who is allowed to do what
  • IoT: a way for devices to talk to the cloud
  • Monitoring: a way to see what's happening
Your laptop has limited RAM, limited storage and you have to look after it yourself. With cloud services, you use the resources you need without building all that infrastructure yourself.
So AWS isn't one software. It's a collection of many services that help you build and run applications.

The mistake I see most often

Students open the AWS console, see hundreds of services, and think, "I need to learn all of this first."
You don't.
Don't ask, "Which service should I learn?" Ask, "What problem am I trying to solve?"
Then match the problem to a service:
  • Need to store files? Amazon S3
  • Need to host a website? AWS Amplify or Amazon S3
  • Need a server? Amazon EC2
  • Need to control access? AWS IAM
  • Need to watch what's happening? Amazon CloudWatch
  • Need a database? Amazon DynamoDB
  • Need to run code without managing a server? AWS Lambda
  • Need to connect a device? AWS IoT Core
The problem comes first. The service comes second.

Your lab list is already a roadmap

Here's the idea that changed how I look at academic assignments:
Your assignment is not the destination. It's the starting point.
If you study cloud computing, your practical list probably maps to AWS like this (your syllabus may be numbered differently):
  • Storage practical → Amazon S3 → build a small cloud file storage app
  • Simple web app → AWS Amplify, S3 or EC2 → publish a portfolio or college event site
  • Provisioning and scaling → EC2, Auto Scaling, CloudWatch → understand how apps handle more users
  • IAM practical → users, roles, policies → learn how to secure access
  • IoT temperature monitoring → IoT Core, Lambda, DynamoDB → a live sensor pipeline
  • RFID practical → the same pipeline → a smart attendance record
Next time you get a practical, don't only ask, "How do I finish this?" Also ask, "What can I build from this?"
Let's go through a few of these.

Try this first: Amazon S3 in 15 minutes

S3 is the easiest place to begin because you can see the result right away.
Three words to know:
  • Bucket: a container for your files
  • Object: the actual file inside it
  • Permissions: who can access it
The flow:
1
Create bucket -> Upload a file -> View the object -> Check permissions -> Delete it
In the AWS console:
  1. Sign in and open S3
  2. Choose Create bucket and give it a unique, lowercase name
  3. Keep the default privacy settings (don't make it public just to see what happens)
  4. Upload any small file
  5. Open the object and look at its details
  6. Delete the object, then delete the bucket
If you prefer the terminal and already have the AWS CLI set up with your own credentials, the same thing looks like this:
1
2
3
4
5
aws s3 mb s3://your-unique-bucket-name
aws s3 cp notes.txt s3://your-unique-bucket-name/
aws s3 ls s3://your-unique-bucket-name/
aws s3 rm s3://your-unique-bucket-name/notes.txt
aws s3 rb s3://your-unique-bucket-name
That's it. You've done the core of a storage practical on a real cloud service.
Now grow it. Upload and download first. Then add a web page, login, a file list, delete, sharing, and a database. Small practicals turn into real applications this way.

Stop running your website only on localhost

You build an HTML, CSS and JavaScript site. You open localhost. You show your teacher. Done.
But what if it had a real link?
1
HTML + CSS + JS -> Amplify or S3 -> Live URL
There's a big difference between saying "I made a website" and saying "I deployed a website on AWS, here's the link." One of those you can put on your resume.
Good first candidates: a personal portfolio, a college event page, or a project showcase.

One rule about security (please read this one)

AWS gives you powerful resources, so you need to control who can use them. That's what IAM is for.
Think of college access. Not everyone should walk into every room. The flow looks like this:
1
Identity -> Authentication -> IAM policy -> Authorization -> AWS resource
In plain words: Who are you? Did you sign in? What are you allowed to do? Which resource can you touch?
And the rule:
Never share your AWS credentials. Not with a friend, not in a WhatsApp group, not on GitHub, and never inside your project code.

What happens when 10 users become 10,000?

You don't need to build this to learn from it. Just understand the idea:
  • Users send requests
  • A load balancer spreads them out
  • Several EC2 servers run your app
  • Auto Scaling adds or removes servers as demand changes
  • CloudWatch shows you what's going on
Running many resources can cost money, so for learning, understanding the idea is often more valuable than building the whole thing.

Make your lab experiment a cloud project (IoT)

If you've used Arduino or Raspberry Pi, don't leave the experiment on the device.
1
Sensor -> AWS IoT Core -> AWS Lambda -> Amazon DynamoDB -> Dashboard
Your sensor sends data. Lambda processes it. DynamoDB stores it. A dashboard shows it. Swap the sensor for an RFID reader and you have a cloud attendance record: student ID plus timestamp.
That's the difference between learning a concept and using it to solve a real problem.

Cost safety: Create, Use, Check, Delete

Cloud is exciting. A surprise bill is not.
Before you create anything, ask yourself:
  1. What am I creating?
  2. Is it covered by my current Free Plan or credits?
  3. How long will it run?
  4. What happens if I forget about it?
Habits that help:
  • Check the current AWS Free Tier or Free Plan rules before you start, since they can change
  • Check the price of a service before you create it
  • Set a budget alert in AWS Budgets
  • Stop or delete resources when your experiment is over
  • Don't leave EC2 instances running "just in case"
Free Tier does not mean everything is free. Experiment as much as you like, just keep it controlled.

Your learning path: Learn, Build, Deploy, Improve, Ship

  1. Learn the basics: cloud, AWS, networking, security, databases
  2. Build small: S3, a website, one EC2 instance, IAM or a Lambda function. Not a giant project
  3. Deploy: move from localhost to AWS
  4. Improve: add authentication, a database, monitoring or automation
  5. Ship: put it on GitHub, write a short README, draw an architecture diagram, record a demo, share it on LinkedIn
You don't get good at cloud by watching 100 videos. You get better by building, breaking, fixing and building again.

Where to keep learning (you don't have to do it alone)

  • Your own AWS account: a safe place to practise, as long as you follow the cost habits above
  • AWS Builder Center: a place to learn, build and connect, with learning content, events, workshops and a builder community
  • AWS Skill Builder: for fundamentals, service learning and certification preparation
  • Other students: build together, ask questions, share what you make
Sometimes the fastest way to learn is to build something with another student.

Your challenge: pick ONE

Not five. One.
  • A. Cloud Storage: S3 upload, retrieve, delete
  • B. Live Website: HTML, CSS and JS to a live URL
  • C. IoT Design: sensor, IoT Core, Lambda, database
  • D. Secure It: IAM user, policy, permission, resource
Here's a simple seven-day plan for whichever you choose:
  1. Day 1: Read about the service and write down the problem you're solving
  2. Day 2: Build the smallest version that works
  3. Day 3: Break it on purpose and fix it
  4. Day 4: Add one improvement
  5. Day 5: Write a short README and draw the flow
  6. Day 6: Delete everything you don't need
  7. Day 7: Share it with a friend or on GitHub

Quick check

Try these before you scroll down.
  1. Which AWS service is the simplest place to start for file storage?
  2. What should you do with AWS credentials?
  3. What's the last step of the cost-safety habit?
Answers: 1. Amazon S3. 2. Never share them or put them in code or on GitHub. 3. Delete what you no longer need.

Last thought

Your academic assignment can be the first step toward a real project. You don't need to know everything about AWS. Pick one problem, choose one service, build something small, deploy it, improve it, and share it.
That's how you go from student to builder.
Your turn: which path did you pick, A, B, C or D? Tell me in the comments.
All the best :)
# students# student-builders# aws-community

Series: Lab-to-Live (1 article)

  1. 1
    From Lab Practical to Live Project: A Student's First Steps With AWS This article
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