I’m currently diving into AWS (Amazon Web Services) in my software engineering degree. Honestly, it’s pretty cool how much there is to learn about cloud computing.
I just finished Module 1. It focused on cloud computing basics. These include what it is, why companies are moving to the cloud, and what AWS actually offers. The advantages of cloud computing over traditional on-premises setups are pretty compelling. It offers scalability and flexibility. You also do not have to maintain your own physical servers. We also covered the AWS Cloud Adoption Framework. It serves as a guide for how organizations can successfully migrate to the cloud.
Now I’m in Module 2, diving into the business side of things: cloud economics and billing. It’s all about understanding AWS pricing models. You need to grasp the Total Cost of Ownership when moving to the cloud. Additionally, learn how to manage and monitor your costs. Turns out there’s a whole art to not accidentally spending a fortune on cloud services. This is definitely good to know before I start spinning up resources!
The course I’m working through covers everything from these basics. It also includes more complex topics. These include setting up virtual private clouds and managing databases. I’ll get to those later. One interesting aspect I’m looking forward to is the “shared responsibility model” for security. It splits the work between AWS and the user. AWS handles the security of the cloud (the infrastructure), while customers handle security in the cloud (their data and applications).
Eventually I’ll be learning about all these different services. EC2 is for virtual servers. S3 provides storage. Lambda handles serverless functions. There are also a bunch of database options like RDS and DynamoDB. I can already tell the hardest part will be keeping track of when to use which service. There are just so many options for doing similar things in different ways.
I’m looking forward to the practical side too. I’ll get to actually build VPCs (Virtual Private Clouds), configure networks, and play around with the AWS Management Console. It’s one thing to read about cloud architecture, but another to actually set it up yourself.
Next up: AWS Global Infrastructure. More to come!
Leave a Reply