AWS Builder Center

My First Steps into AWS: From Local Development to the Cloud

Starting my AWS journey by exploring cloud computing, AWS fundamentals, and DevOps practices. In this article, I share my learning goals, approach, and plan to build and deploy real-world applications on AWS.

CS undergraduate , intersted in devOps.
s a Computer Science undergraduate, I have spent a lot of time learning how to build software. But building an application is only one part of the problem.
A question that became increasingly interesting to me was:
What happens after the application is built?
How is it deployed? Where does it run? How does it communicate with other services? How do developers automate deployments? How can an application remain available when the number of users increases?
These questions led me to start learning cloud computing and AWS.

Why AWS?

AWS provides a large ecosystem of cloud services that can be used to build, deploy, and manage applications.
For me, learning AWS is not simply about learning individual services. My goal is to understand the infrastructure behind modern applications and eventually develop strong DevOps and cloud engineering skills.
I want to move beyond running applications only on my local machine and learn how to deploy and manage them in a real cloud environment.

What I Want to Learn

I am starting with the fundamentals and gradually moving toward more advanced cloud and DevOps concepts.
Some of the areas I plan to explore are:
  • Amazon EC2 for computing and virtual machines
  • Amazon S3 for object storage
  • IAM for authentication and access control
  • Amazon VPC for networking
  • Docker for containerization
  • CI/CD for automated software delivery
  • Terraform for Infrastructure as Code
  • Monitoring, security, and cloud architecture
Rather than trying to learn everything at once, I want to understand each concept by actually using it.

My Learning Approach

My approach is simple:
Learn → Build → Break → Fix → Document
Reading documentation and watching tutorials can provide the theory, but practical experience is where the real understanding comes from.
For example, instead of only learning what an EC2 instance is, I want to actually:
  1. Launch an instance.
  1. Connect to it using SSH.
  1. Configure the Linux environment.
  1. Deploy an application.
  1. Containerize the application using Docker.
  1. Automate deployment using CI/CD.
  1. Monitor and secure the deployment.
Each step introduces another piece of the bigger picture.

My First AWS Goal

My first major goal is to deploy a backend application to AWS.
I want to start with a simple architecture and gradually improve it as I learn more.
The initial workflow will look something like:
Code → GitHub → CI/CD → Docker → AWS → Running Application
Later, I want to explore how this architecture can be improved using additional AWS services and infrastructure automation.
This approach should help me understand not only AWS services individually, but also how they work together as part of a real system.

What I Hope to Gain

Through this journey, I want to develop skills that go beyond simply knowing AWS terminology.
I want to be able to:
  • Deploy applications independently.
  • Understand cloud networking and infrastructure.
  • Automate repetitive deployment tasks.
  • Work with containers.
  • Manage infrastructure using code.
  • Understand security and access control.
  • Troubleshoot real deployment problems.
  • Design better and more scalable systems.
Most importantly, I want to develop the ability to learn and solve unfamiliar infrastructure problems independently.

Starting the Journey

I know that there is a lot to learn in AWS, and trying to learn every service would be unrealistic.
Instead, I am focusing on building a strong foundation and learning through projects.
This is the beginning of my AWS journey, and I plan to document what I build, the problems I encounter, and the lessons I learn along the way.
The goal isn't just to learn the cloud. It's to learn how to build, deploy, automate, and operate software in the cloud.
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