My Journey to DevOps: Building an AWS Resource Tracker with Shell Scripting and AWS CLI

I am excited to share that I have learned how to create a real-time shell script project for DevOps on AWS. This project involves creating a shell script to track AWS resources such as EC2 instances, S3 buckets, Lambda functions, and IAM users using the technologies like Shell scripting, AWS CLI, AWS Instances, Cron jobs, JQ (JSON parser). This can be an essential tool for efficient resource management, maintaining cost-effectiveness and generating daily reports in any cloud infrastructure.

Firstly I learned How to efficiently create and connect to virtual machines (VMs) using AWS services. After logging into an AWS EC2 instance through the AWS console and terminal, connect it to an EC2 instance. Should know that using the console is not efficient for DevOps engineers who frequently manage multiple VMs. Instead using terminal tools such as iTerm for Mac or alternatives like Putty, MobaXterm, and NoMachine for Windows. Next, logging into an EC2 instance using the terminal, knowing the importance of using the correct public IP and key pair for authentication, configure the terminal to secure the pem file permissions before successfully logging into the instance. Next, AWS CLI installation, configure, and use it to interact with AWS services. Then leveraged AWS documentation extensively to understand commands and their usage.

This project not only honed my skills in AWS and DevOps but also demonstrated the power of effective learning resources and documentation. A big shoutout to the community and the tutorial creator: Abhishek Veeramalla on YT for making this learning experience possible!