It is always advisable to use IAC for spinning up resources but sometimes for ad-hoc testing , I use AWS console for creating resources. There was one particular instance where I had kept my LB in ap-south-1 for couple of months incurring huge bill. I tend to check in us-east-region and skip other regions which led to the huge bill.
I am learning Go and thought to implement a small utility for checking whether there are any running ec2 , unattached EIP or load balancer in regions that are frequently used.
Regions, port are configured in config.json
{
"port": ":8080",
"logLevel": "INFO",
"regions": ["us-east-1","ap-south-1","us-east-2"]
}API Endpoints
GET /api/ec2/details --> Gets all the EC2 instances along with state grouped by regions
GET /api/ec2/start --> Start EC2
GET /api/ec2/stop --> Stop EC2
GET /api/eip/details --> Gets all unattached Elastic IPs
GET /api/eip/release --> Release Elastic IP
GET /api/s3 --> Gets all S3 buckets grouped by regions
GET /api/lb/details --> Gets load balancers grouped by regions
GET /api/lb/delete --> Delete Load Balancer
GET /api/dd/details --> Gets DynamoDB tables
This is a WIP . My future plan is to incorporate endpoints for Azure and develop a single dashboard to view resources across multiple clouds.
References