gbecchio/snapshotalyser-3000

Demo project to manage AWS EC2 instance snapshots

snapshotalyser-3000

Demo project to manage AWS EC2 instance snapshots

About

This project is a demo, and uses boto3 to manage AWS EC2 instance snapshots.

Configuring

shotty uses the configuration file created by the AWS cli. e.g.

aws configure --profile shotty

Runnning

pipenv run "python shotty/shotty.py <command> <subcommand> <--project=PROJECT>"

command is instances, volumes or snapshots subcommand - depends on command project is optional

snapshotalyser-3000's Issues

"reboot" instances

Add the ability to "reboot" instances.

instance argument

Add "instance" argument to tho appropriate commands, so they only target one instance

shotty volumes list --instance=i-0123456789abcdef

don't stop when snapshotting

When snapshotting, don't stop an instance unless the script will snapshot one of its volumes.

optional "age" parameter

Add an optional "age" prameter to the "snapshot" command that takes an age in days and only snapshots volumes whose last successful snapshot is older than that many days.

shotty instances --age 7 --project Valkyrie

last snapshot

After a snapshot, only satrt instances that were running before the snapshot was taken.

Exception for snapshots

Use a try/except block to catch "botocore.exceptions.ClientError" whin creating snapshots, and print an error message.

"region" parameter

Add a "region" parameter to all commands that will let the user override the region set their AWS CLI configuration profile:

shotty --region us-east-1 instances list

"--force" flag

Add a "--force" flag to the this commands for instances:

• "stop"
• "start"
• "snapshot"
• "reboot"

--project not set

if "project" isn't set, exit the command immediately with an error messaghe unless "--force" is set

"--profile" option

Add a "--profile" option to the "cli" group, which let's you specify a different profile.

shotty --profile Greg instances stop --force