๐ My AWS Learning Journey: From Cloud Basics to Building Real Projects
By Ambati Eswar Reddy
Cloud computing initially felt like a huge and complicated field to me. There were so many services, concepts, and new terminologies to understand. But after starting my AWS journey, I realized that learning cloud computing becomes much easier when we combine theory with hands-on practice.
As a student, my goal has been to understand not only what AWS services are, but also why and when we should use them.
โ๏ธ Starting with AWS Fundamentals
I started my AWS journey by learning the fundamentals of cloud computing and exploring the major AWS services.
Some of the concepts I focused on were:
- AWS Global Infrastructure
- Regions and Availability Zones
- Amazon EC2
- Amazon S3
- IAM
- VPC
- Elastic Load Balancing
- CloudWatch
- AWS Billing and Cost Management
Understanding these foundational concepts helped me build a strong base before moving toward more practical implementations.
๐ฅ๏ธ My First EC2 Experience
One of the most exciting parts of my AWS learning journey was launching my first Amazon EC2 instance.
I learned how to:
- Launch an EC2 instance.
- Configure a Security Group.
- Connect to the instance.
- Install and configure an Apache web server.
- Host a simple web page.
- Access the application through the instance's public IP address.
This experience taught me an important lesson:
Cloud computing is best learned by actually using the cloud.
Reading about EC2 is useful, but launching an instance, configuring it, troubleshooting connectivity, and seeing your webpage running makes the concept much clearer.
๐ชฃ Exploring Amazon S3
I also explored Amazon S3 and learned how object storage works.
I practiced concepts such as:
- Creating S3 buckets
- Uploading objects
- Understanding bucket policies
- Managing access permissions
- Hosting static website content
- Understanding the difference between public and private access
S3 helped me understand how applications can store and serve files without depending on traditional server storage.
๐ Learning the Importance of IAM
Another important part of my AWS journey has been Identity and Access Management (IAM).
I learned that security should not be something we think about after building an application. It should be considered from the beginning.
I explored:
- Users
- Groups
- Policies
- Permissions
- Administrator access
- Read-only access
- Multi-factor authentication (MFA)
The principle of least privilege is one of the most important lessons I took from IAM: users and applications should receive only the permissions they actually need.
โ๏ธ Connecting EC2 with Load Balancing
I also experimented with multiple EC2 instances and a Load Balancer.
This helped me understand how traffic can be distributed across multiple servers.
The basic architecture looks like:
Users | v Application Load Balancer | ----------------- | | v v EC2 #1 EC2 #2 | | ----------------- | v ApplicationThis introduced me to important cloud concepts such as scalability, availability, and traffic distribution.
It also taught me that cloud architectures often involve connecting multiple services together rather than using a single service in isolation.
๐ Monitoring with CloudWatch
I also explored Amazon CloudWatch and learned how monitoring is an essential part of cloud operations.
CloudWatch can help us monitor resources, collect metrics, create alarms, and understand application behavior.
This made me realize that:
Building an application is only one part of the job. Monitoring and maintaining it is equally important.
๐ค Combining AWS with AI
One area that particularly interests me is the combination of Cloud Computing and Generative AI.
I have been exploring how AWS services can be used as the infrastructure and platform layer for AI-powered applications.
This includes understanding concepts such as:
- Generative AI
- Large Language Models
- Retrieval-Augmented Generation (RAG)
- AI-powered applications
- Amazon Bedrock
- Cloud deployment
- Security and scalability
I believe the combination of AWS + AI + Automation will create many exciting opportunities for students and developers.
๐งช Learning Through Troubleshooting
One of the most valuable parts of my AWS journey hasn't been when everything worked perfectly.
It has been when something didn't work.
For example, while working with EC2 and web servers, I encountered issues where my application wasn't accessible.
Troubleshooting made me check things such as:
- Is the instance running?
- Is the web server running?
- Is the Security Group configured correctly?
- Is the correct port open?
- Is the application listening on the expected port?
- Is the correct public address being used?
These experiences taught me that cloud engineering isn't just about memorizing services. It is about understanding systems and solving problems.
๐ฏ What I Learned as a Student
My AWS journey has taught me several important lessons:
1. Start with fundamentals
Don't try to learn 50 AWS services at once.
Start with:
Cloud Basics โ IAM โ EC2 โ S3 โ VPC โ Load Balancing โ Monitoring
2. Practice is more powerful than memorization
Instead of simply remembering what EC2 does, launch an instance.
Instead of only reading about S3, create a bucket and upload objects.
Instead of only studying Security Groups, configure one and understand what happens when a port is blocked.
3. Learn troubleshooting
Errors are part of the learning process.
Every error gives us an opportunity to understand how the system actually works.
4. Think about security from the beginning
AWS gives us powerful tools, but those tools need to be configured responsibly.
IAM, permissions, MFA, Security Groups, and least-privilege access should become part of our normal development mindset.
5. Build projects
Projects are where different AWS concepts start connecting together.
A simple project can teach us much more than hours of passive learning.
๐ฑ What's Next?
My AWS journey is still in progress.
My next goals are to go deeper into:
- AWS networking
- Cloud Security
- Serverless architecture
- Infrastructure as Code
- DevOps
- Monitoring and automation
- Generative AI on AWS
- Production-ready cloud architectures
I also want to continue building projects that combine AWS, AI, automation, and software development.
๐ A Message to Fellow Student Builders
If you're a student who is just starting with AWS, don't feel overwhelmed by the huge number of services.
Start small.
Launch your first EC2 instance.
Create your first S3 bucket.
Configure IAM.
Deploy a small application.
Break something.
Troubleshoot it.
Then build something better.
The most important thing is to keep building.
AWS is not just something to learn for an exam or certification. It is a platform where we can turn our ideas into real applications.
I'm excited to continue this journey as a student builder, learn from the AWS community, share what I learn, and build solutions that create real impact.
Keep learning. Keep building. Keep experimenting. ๐โ๏ธ
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article