AWS Builder Center

My AWS Cloud Essential Learning Journey

I went from knowing nothing about cloud computing to completing AWS's 21-hour Cloud Essential badge and building my own AI-powered application. This is my honest account of the learning curve, the frustrations with cost management, the satisfaction of successful labs, and the RAG app I built to prove I could do it.

Completing the AWS Cloud Essential course has been a transformative experience that opened my eyes to the vast possibilities of cloud computing. This journey took me from understanding basic cloud concepts to building practical applications that leverage AWS's powerful infrastructure.

What I Learned

My learning journey began with foundational cloud computing concepts, understanding how AWS's global infrastructure operates through Regions and Availability Zones. I gained deep insights into the AWS Shared Responsibility Model, which clarified the division of security responsibilities between AWS and customers—AWS secures the infrastructure "of" the cloud, while customers secure their resources "in" the cloud.
The compute services section was particularly comprehensive. I explored Amazon EC2 instances and their various types—general purpose, compute optimized, memory optimized, accelerated computing, and storage optimized—each designed for specific workload requirements. Learning about AWS Lambda introduced me to serverless computing, where I could run code without managing servers, paying only for actual compute time consumed. Container orchestration through Amazon ECS, EKS, and Fargate expanded my understanding of modern application deployment.
Storage and database services formed another crucial component of my education. I learned to differentiate between block storage (Amazon EBS), object storage (Amazon S3), and file storage (Amazon EFS), understanding when to use each type. The database module covered both relational databases through Amazon RDS and Aurora, and NoSQL databases through DynamoDB. Amazon ElastiCache taught me about in-memory caching for performance optimization.
Networking concepts became clear as I studied Amazon VPC, subnets, security groups, and various connectivity options including internet gateways, VPN connections, AWS PrivateLink, and AWS Direct Connect. Infrastructure as Code through AWS CloudFormation demonstrated how to automate resource provisioning and management.
The security modules were eye-opening, covering IAM for access management, AWS Shield and WAF for network protection, AWS KMS for encryption, and services like Amazon Inspector, GuardDuty, and Detective for threat detection and response. I also explored AWS's generative AI offerings, particularly Amazon Bedrock and SageMaker JumpStart, which sparked my interest in building AI-powered applications.

What Was Most Challenging

The most challenging aspect was undoubtedly the cloud acquisition and procurement module. As someone new to cloud computing, I found myself drowning in an ocean of considerations that extended far beyond simply "buying" cloud services.
The Procurement Foundations section required a fundamental rethinking of how organizations acquire technology. Traditional IT procurement—where you purchase physical hardware with predictable upfront costs—doesn't apply in the cloud. I had to learn about educating internal stakeholders who might still think in terms of capital expenditures rather than operational expenditures, and understand the critical distinction between separating infrastructure costs from services and labor. This conceptual shift alone was mentally exhausting.
The Key Aspects of Procurement module introduced multiple dimensions that had to be considered simultaneously. Pricing wasn't just about understanding AWS's pay-as-you-go model—it involved navigating On-Demand instances, Reserved Instances, Savings Plans, and Spot Instances while calculating total cost of ownership. Security considerations went beyond technical implementations to contractual obligations and compliance frameworks. Data sovereignty and data residency added legal and regulatory complexity, requiring me to understand where data physically resides and which jurisdictions govern it. Sustainability metrics, governance frameworks, operationalization strategies, and the intricate terms and conditions in cloud contracts created an overwhelming matrix of decision points.
Working with the AWS Partner Network introduced another layer—understanding when to engage partners, how they add value, and navigating the partner ecosystem. The "Making It Real" section, which covered procurement vehicle global examples, migration discussions, and answering common procurement questions, felt like learning an entirely new language of RFPs, SOWs, and procurement vehicles.
The sheer volume of information and the interconnected nature of these considerations made this the most intellectually demanding part of the course. Unlike technical labs where you get immediate feedback, procurement decisions require balancing numerous competing factors with long-term implications.

What Was Most Rewarding

Hands down, the most rewarding part of this course was completing the labs and watching everything work together. There's an indescribable satisfaction in launching your first EC2 instance, configuring security groups correctly, and successfully connecting to it. Building a VPC from scratch with public and private subnets, deploying a database in the private subnet, and hosting a web application in the public subnet felt like assembling pieces of a complex puzzle.
The practical labs transformed abstract concepts into tangible skills. Seeing an Auto Scaling group automatically adjust EC2 instances based on demand, watching CloudFormation spin up entire infrastructure stacks from a template, and successfully implementing IAM policies that secured resources without blocking legitimate access—these moments validated all the theoretical learning and boosted my confidence tremendously.

My Next Steps and Project Showcase

Looking forward, I plan to build a comprehensive web application that leverages AWS AI-tool capabilities, particularly Amazon Bedrock's foundation models for natural language processing and content generation. This project will integrate multiple AWS services—EC2 or Lambda for compute, RDS or DynamoDB for data persistence, S3 for object storage, and Amazon Bedrock for AI functionality.
I've already begun this journey by creating a RAG (Retrieval-Augmented Generation) application available at https://github.com/S1R15H/RAG-app . This project uses Amazon Bedrock services to access various AI models through a universal API, demonstrating how to build intelligent applications that can understand context, retrieve relevant information, and generate human-like responses. The RAG architecture combines the power of information retrieval with generative AI, making it perfect for building chatbots, knowledge bases, and intelligent assistants.
My goal is to expand this foundation into a production-ready application that showcases the full spectrum of AWS capabilities—from secure authentication using IAM and Cognito, to scalable infrastructure using Auto Scaling and Load Balancers, to cost-optimized storage strategies, and cutting-edge AI features through Bedrock. This hands-on approach will solidify my cloud engineering skills and prepare me for real-world cloud architecture challenges.
The AWS Cloud Essential course has been more than just learning about services—it's been about understanding how to architect solutions, think at scale, and leverage cloud-native approaches to solve business problems. I'm excited to continue this journey and contribute to the growing cloud computing community.
credly: https://www.credly.com/badges/8260c4cb-55a7-4948-9714-2a37c138b3f0/public_url
linkedin: https://www.linkedin.com/in/sirish-gurung-tech/
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