My AWS Learning Journey: From Cloud Fundamentals to Real Infrastructure
I’m documenting my AWS learning journey as I move from cloud fundamentals toward designing, deploying, securing, and operating real-world infrastructure.
My AWS Learning Journey: From Cloud Fundamentals to Real Infrastructure
Cloud has become an important part of modern infrastructure, and my AWS learning journey started with a simple question: How do the cloud services I study actually come together to build a secure and reliable infrastructure?
As I continue developing my skills in cloud infrastructure, I am focusing not only on learning individual AWS services, but also on understanding how those services work together in real-world environments.
Starting with Cloud Fundamentals
My first step has been understanding the fundamentals of cloud computing.
Before working with individual services, I wanted to understand the bigger picture:
- Why organizations move workloads to the cloud
- Infrastructure as a Service, Platform as a Service, and Software as a Service
- Regions and Availability Zones
- Scalability and elasticity
- High availability
- Security and shared responsibility
- Cost awareness and resource management
These concepts provide the foundation for making better infrastructure decisions later.
Understanding Identity and Access Management
Security is one of the first areas I focus on when learning cloud infrastructure.
AWS Identity and Access Management (IAM) helps control who can access AWS resources and what actions they can perform.
Some important concepts I am focusing on include:
- Users
- Groups
- Roles
- Policies
- Permissions
- Least-privilege access
One important lesson is that cloud security should not be treated as something added at the end of a project. Identity and access decisions should be considered from the beginning.
Moving from Services to Infrastructure
Learning the name and purpose of a service is only the beginning.
The more interesting part is understanding how services interact.
For example, a typical application environment may involve:
Users → Load Balancer → Application Servers → Database
Around these components, additional services and controls can provide:
- Network isolation
- Identity and access control
- Monitoring
- Logging
- Backup
- Scaling
- Cost management
This helped me shift my thinking from “What does this AWS service do?” to “Why would I use this service in an infrastructure design?”
Learning Networking with VPC
Networking is another major area I am focusing on.
AWS VPC concepts helped me understand how cloud workloads can be isolated and connected.
Some of the important concepts include:
- VPC
- Subnets
- Route tables
- Internet Gateway
- NAT Gateway
- Security Groups
- Network ACLs
Understanding the relationship between a subnet and its route table was especially important for understanding why some workloads can communicate with the internet while others remain isolated.
Compute and Application Infrastructure
AWS compute services provide the foundation for running workloads.
While learning compute infrastructure, I am focusing on concepts such as:
- Virtual machines
- Instance types
- Storage
- Security Groups
- Availability
- Scaling
- Monitoring
The goal is not simply to launch a server, but to understand how that server fits into a secure and scalable architecture.
Monitoring and Operations
Infrastructure is not complete when it is deployed.
It also needs to be monitored and maintained.
I am learning the importance of:
- Metrics
- Logs
- Alerts
- Resource health
- Performance monitoring
- Operational visibility
This is helping me understand the difference between deploying infrastructure and operating infrastructure.
What I Am Learning Along the Way
One of the biggest lessons from my cloud journey is that learning individual services is not enough.
A strong cloud engineer needs to understand the relationships between:
Identity + Networking + Compute + Storage + Security + Monitoring + Cost
When these areas are considered together, cloud architecture becomes much easier to understand.
What I Want to Explore Next
My next focus areas are:
- Building more hands-on AWS infrastructure
- Strengthening AWS networking knowledge
- Improving cloud security practices
- Learning infrastructure automation
- Understanding monitoring and operational best practices
- Designing highly available architectures
- Preparing for AWS certification
I want to continue moving from learning cloud concepts → building infrastructure → troubleshooting real problems → designing better solutions.
Final Thoughts
My AWS journey is still in progress, but every hands-on exercise gives me a better understanding of how modern cloud infrastructure is designed and operated.
For me, the goal is not just to memorize AWS services.
The goal is to understand why a service is needed, how it fits into an architecture, how to secure it, and how to operate it reliably.
I am looking forward to documenting more of my AWS learning journey and sharing the lessons I discover along the way.
Keep learning. Keep building. Keep improving.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article