Create Rotating Instance AMIs Backups

With serverless!

Found at: https://github.com/AndrewFarley/AWSAutomatedDailyInstanceAMISnapshots

Author

Farley - farley at neonsurge dot com

Purpose

A nearly idiot-proof way to begin doing automated daily snapshots of instances across your entire AWS account.
To promote people to back-things-up, by giving them an easy way to begin doing so.
To try to save them money in regards to backups by deleting them after a while (7 days by default)

What does this do...?

This uses the serverless framework, which generates a CloudFormation stack and deploys it to your AWS account in the eu-west-1 region (adjustable)
This CloudFormation stack deploys a Lambda and a role for this lambda to allow it to do what it needs to do.
Finally this CloudFormation stack configures that Lambda to be executed once a day automatically via CloudWatch Events.
When this lambda runs, it scans through EVERY AWS region for any instances with the tag Key of "backup". If it finds any, it will create a snapshot of them, preserving all the tags
After its done taking snapshots, it will then scan through all the AMIs that this script created, and will evaluate if it's time to delete those AMIs if they are old enough
THAT's IT! You don't have to do anything, just install this, and start backing up your servers.

Prerequisites

Setup

# Make sure your CLI has a default AWS credentials setup, if not run this...
aws configure

# Clone this repository with...
git clone git@github.com:AndrewFarley/AWSAutomatedDailyInstanceAMISnapshots.git
cd AWSAutomatedDailyInstanceAMISnapshots

# Deploy it with...
serverless deploy

# Run it manually with...
serverless invoke --function daily_snapshot --log

That's IT! Now go tag your instances (manually, or automatically if you have an automated infrastructure) with the Key "backup" which will trigger this script to back it up. After tagging some servers, try to run it manually again and check the output to see if it detected your server. To make sure your tag works, go run the lambda yourself manually and check the log output. If you tagged some instances and it ran successfully, your output will look something like this...

bash-3.2$ serverless invoke --function daily_snapshot --log
--------------------------------------------------------------------
Scanning region: eu-central-1
Scanning for instances with tags (backup,Backup)
  Found 2 instances to backup...
  Instance: i-00001111222233334
      Name: jenkins-build-server
      Time: 7 days
       AMI: ami-00112233445566778
  Instance: i-55556666777788889
      Name: primary-webserver
      Time: 7 days
       AMI: ami-11223344556677889
Scanning for AMIs with tags (FarleysBackupInstanceRotater)
  Found AMI to consider: ami-008e6cb79f78f1469
           Delete After: 06-12-2018
This item is too new, skipping...
Scanning region: eu-west-1
Scanning for instances with tags (backup,Backup)
  Found 0 instances to backup...
Scanning for AMIs with tags (FarleysBackupInstanceRotater)
Scanning region: eu-west-2

Removal

Simple remove with the serverless remove command

serverless remove

Changelog / Recent Features

June 6, 2018 - Initial public release

Support, Feedback & Questions

Please feel free to file Github bugs if you find any. It's probably easier if you fork my repo to make your own modifications detailed above and commit them. If you make any fixed/changes that are awesome, please send me pull requests or patches.

If you have any questions/problems beyond that, feel free to email me at one of the emails in author above.

ErnestOrt/AWSAutomatedDailyInstanceAMISnapshots