This project automates the process of listing active AWS resources (e.g., EC2, S3) using a shell script. It helps DevOps teams monitor resource usage and optimize costs.
Automate the process of listing active AWS resources (e.g., EC2, S3) using a shell script.
- DevOps Engineers need such scripts to monitor resource usage for cost optimization.
- Helps in day-to-day operations and automation workflows like cron jobs.
-
Purpose of Shell Scripting in DevOps:
- Automates repetitive tasks.
- Ensures consistency in operations like listing, monitoring, or resource management.
-
What the Script Does:
- Connects to AWS.
- Lists active resources for specified services (e.g., EC2, S3).
- Takes two inputs: region and service.
-
Inputs and Outputs:
- Inputs: AWS region and service name (e.g.,
us-east-1,ec2). - Output: Lists all active resources for the specified service in the given region.
- Inputs: AWS region and service name (e.g.,
- Editor: Use VS Code to write the script.
- Environment: Use an AWS EC2 instance to run and test the script (preferred for Windows users).
-
Start with comments:
- Purpose: "This script lists active AWS resources."
- Author info (e.g., your name, team).
- Versioning for tracking updates (e.g., v0.1).
-
Validations:
- Check if required arguments (region and service) are provided.
- Verify that AWS CLI is installed and configured.
-
Core Logic:
- Use AWS CLI to interact with AWS services.
- Validate supported services (e.g., EC2, S3, EBS) and reject invalid inputs.
- Use
switch-casefor better performance overif-else.
-
Command Execution:
- Example for EC2:
aws ec2 describe-instances. - Example for S3:
aws s3api list-buckets.
- Example for EC2:
-
Security Best Practices:
- Limit script permissions using
chmod(e.g.,chmod 711).
- Limit script permissions using
- Install AWS CLI and configure it using
aws configure. - Execute the script:
./aws_resource_list.sh <region> <service>