How does it work?

Step 1 Sign up
Step 2 Once logged in, click to activate the Snapshot product.
Step 3 Give AutoSnappy a user with permission to snapshot EBS Volumes at AWS.
Step 4 Add your first scheduled snapshot, monitoring or retention rule!

Why use Snapshot and Rotate?

Ease of Use
AutoSnappy is easy to setup with powerful cron based schedules for all supported types of tasks.
There are always multiple processes waiting to execute your tasks. You use EC2 and so do we. We're service oriented and ready to scale.
Writing and auditing a snapshot setup is annoying at best and is not likely to be your core business focus. It is our job to make sure your Elastic Block Store snapshot tasks are working correctly.


Snapshot and Rotate has the following features

  • Unlimited Snapshot Schedules
  • Each volume can have its own schedule for snapshots
  • Unlimited Pruning Schedules
  • Each volume can have its own schedule and settings for retention based on number or age of snapshots
  • Unlimited Monitoring Schedules
  • Monitoring Rules can be set up to alert you when a volume has less or more than the specified number of snapshots
  • Rule is triggered once per transition between a valid and invalid number based on when you have the monitoring set.
  • Support for all regions

Generating Appropriate Security Keys

The root access key and secret access key for your main AWS account have full control of your AWS environment. By the prinicple of least privilege, we believe the best way to enable AutoSnappy is to create a user that has just enough rights to do its job. 

The way to accomplish this is the following:

  1. Login to the IAM Control Panel
  2. Create a new user and name it something meaningful like "snapshotuser"
  3. Save the access and secret key for use at AutoSnappy
  4. Attach the policy to the user to give it the rights it needs.

You can also accomplish this with command line tools:

  1. Download and install the IAM Command Line Toolkit
  2. Add a user for AutoSnappy with iam-usercreate, name it something meaningful like "snapshotuser"
  3. Record the access key and secret access key for that user
  4. Save this policy to your computer, and upload it to that user with iam-useruploadpolicy 

Cron Format

Cron format consists of five fields, each delimited by a space.
* * * * *
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of        month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)

A field may be an asterisk (*), which always stands for "first-last".

Ranges of numbers are allowed.  Ranges are two numbers separated with a
hyphen.  The specified range is inclusive.  For example, "8-11" for an
"hours" entry specifies execution at hours 8, 9, 10 and 11.

Lists are allowed.  A list is a set of numbers separated by
commas.  Examples: "1,2,5,9", "0,3,4".

20,40 5-8 20-30 * * 

20,40  Run when the minute is 20 or 40 
5-8    of 5 through 8 am
20-30  during the 20th through 30th day
*      of each month
*      no matter what day of the week it is.

This implementation allows only day-of-week or day-of-month 
to be limited at one time. One or the other (or both) must be *.