[PYTHON] [AWS] EBS creation status check tool

EBS creation status check tool

Recently, repeated instance start / stop and backup A lot of Volumes when I noticed by snapping for AMI creation. ..

Many EBSs are made (available) even though they are not "in-use", If you check the billing status with Account Activity, this is increasing soberly.

Amazon EC2 EBS $0.12 per GB-month of provisioned storage .....

About volume operation and billing

Try it and feel it on your skin! From an instance with 3 EBS volumes attached From creating an AMI.

• [a] If you delete the AMI

1. Create AMI
2. SNAP, Volume confirmation SNAP is possible. (And now I notice that Progress is a bar display.)

• Of course, Volume is not possible.

3. Delete AMI Disappear beautifully
4. SNAP, Volume confirmation SNAP remains

• If this is left as it is, it will be charged below, so delete it for the time being.

Amazon EC2 EBS $0.1 per GB-Month of snapshot data stored

• [b] If you remove SNAP

1. Create AMI
2. SNAP, Volume confirmation Like [a], SNAP can be done, but Volume cannot. ..
3. Remove SNAP Yes, I can't erase it! !! Sorry! That's right, SNAP cannot be erased because it is one element of the image storage configuration.

• [c] When Volume is deleted

1. Launch an instance from the AMI created in [b] Please turn off "Delete on Termination". (People who are familiar with this area are likely to be spoiled ...)
2. SNAP, Volume confirmation SNAP cannot be newly created (naturally), but Volume is newly expanded from SNAP and is an instance.
3. Terminate the instance and delete Volume
4. Neither SNAP nor AMI disappears! (Of course!!)

I made a tool

• Purpose

• I want to reduce waste

• Overview

• As you can see from the above, when you create an AMI, SNAP is created, and when you start an instance, a new Volume is created.

• If you know only what you made yesterday, you can erase unnecessary things while your memory is hot the next day!

• I want to automate it eventually. .. .. The automatic deletion is a little scary, so I'll come back later.

• Operating environment

• CentOS6.3

• Python 2.6.6

• boto-2.6.0

• aws-cli/0.12.0

daily_check_ebs_created.py

#!/usr/bin/python
#-*- coding: utf-8 -*-

import commands
import sys,getopt
import json
import datetime

from datetime import datetime as dt

# Set standard date
aday = datetime.timedelta(days=1)
std_day = datetime.datetime.today() - aday

# Exec command
aws_cmd='aws ec2 describe-volumes'
out=commands.getoutput(aws_cmd)

# Parse JSON
ebs_data = json.loads(out)

print "===================================================================="
print "The following refers to the volume that is created after this time. "
print  unicode(std_day)
print "===================================================================="

for vols in ebs_data["Volumes"]:
   cretime = dt.strptime(vols["CreateTime"], '%Y-%m-%dT%H:%M:%S.000Z')
   ## Volume only newly created
   if cretime > std_day:
     print  "AZ=" + vols["AvailabilityZone"] + ", volId=" + vols["VolumeId"] + ", CreateTime=" + unicode(cretime) + ", State=" + vols["State"]

• If it does not work as it is, execute the following command.

export AWS_DEFAULT_REGION=ap-northeast-1

See below

It's not such a big code w However, the ones that can be used soberly are up.

However, "usable" and "unusable" are also subjective, so Start by writing something that is simple and "usable" by yourself.