AUTOMATING THE USAGE OF AWS SERVICES WITH SHELL SCRIPTS: A Comprehensive Guide for Beginners

Introduction:

In the fast-paced world of DevOps, automation is key to managing and scaling cloud infrastructure efficiently. AWS, a leading cloud service provider, offers powerful CLI tools to manage resources, but manually executing commands can be time-consuming. This article walks you through automating AWS resource tracking using a shell script, enhancing productivity and operational efficiency.

Prerequisites:

Before diving into the script, ensure you have:

• AWS CLI installed and configured with the necessary credentials.
• Basic knowledge of shell scripting.
• "jq" tool installed for parsing JSON data from AWS CLI outputs.

Step-by-Step Guide:

1. Setting Up Your Environment:

First, make sure your environment is set up correctly. Install the AWS CLI and configure your AWS credentials:

During the aws configure step, you'll need to provide the following details:

1. AWS Access Key ID: Your AWS access key.
2. AWS Secret Access Key: Your AWS secret key.
3. Default region name: The region you want to interact with (e.g., us-west-2).
4. Default output format: Set to json for this script.

Install "jq" for parsing JSON:

2. Writing the Shell Script:

Let's break down the script that automates the tracking of AWS resources.

Explanation:

1. Shebang (#!/bin/bash): Indicates that the script should be run in the Bash shell.
2. Author and Date: Contains the metadata.
3. Set -x: Enables debugging, showing each command before execution.
4. List S3 Buckets: Uses "aws s3 ls" to list all S3 buckets, outputting to AWS-usage.txt.
5. List EC2 Instances: Uses "aws ec2 describe-instances" and "jq" to list EC2 instance IDs.
6. List AWS Lambda Functions: Uses "aws lambda list-functions" to list all Lambda functions.
7. List IAM Users: Uses "aws iam list-users" and "jq" to list IAM user names.
8. -e: It is used with the "echo" command to enable the interpretation of backslash escapes.

3. Executing the Script:

To make the script executable and run it:

1. chmod 777 aws_resource_tracker.sh: Changes the file permissions to make the script executable by anyone.
2. ./aws_resource_tracker.sh : Runs the script.

The output will be saved in AWS-usage.txt, containing the lists of S3 buckets, EC2 instances, Lambda functions, and IAM users.

4. Benefits for DevOps Engineers:

This script simplifies the monitoring of AWS resources, providing a single command to gather essential information. It:

• Saves Time: Automates repetitive tasks, freeing up time for other critical activities.
• Reduces Errors: Minimizes human error by standardizing the process of gathering resource information.
• Enhances Reporting: Generates consistent and up-to-date reports on AWS resource usage, useful for audits and performance tracking.
• Improves Efficiency: Allows for quick assessment of cloud resources, aiding in better decision-making and resource management.

Conclusion:

Automating AWS resource tracking with a shell script is a powerful way to improve efficiency and accuracy in managing cloud infrastructure. By following this guide, you can easily implement this automation and reap the benefits in your DevOps practices. Whether you are managing a few instances or a complex multi-region setup, this script will help you keep track of your resources, making your workflow smoother and more efficient.

Images for Reference:

• Shell Script:

• Script Execution:

• Output File