Skeddly Adds New Report Showing Health of EBS Snapshots

Skeddly has added a new report that gives users visibility into their disaster recovery efforts and helps them check they are meeting their backup requirements.

The new report helps users gauge the state of their disaster recovery plans by reporting on the state of their EBS snapshots. While companies can implement policies that require EBS snapshots to be taken to ensure EBS volumes can be recovered in the event of a disaster, policies may not always be put into practice. EBS volumes may be missed, snapshots may fail, and it is highly beneficial to know in advance that if disaster strikes, a quick recovery will be possible with minimal – or preferably no – data loss.

The new report helps in this regard. The EBS volume snapshot report details EBS volumes, the date of the most recent snapshot, the number of snapshots with warnings, and the number of snapshots with alerts. The current status of each EBS volume is shown along with the instance ID of the attached EC2 instance.

Users can configure the reports and specify the criteria for both warnings and alerts. For instance, a warning could be when there is less than one snapshot for the past 30 days and an alert if there is less than one snapshot for the past 7 days or vice versa. Users have two configuration options for alerts and two for warnings, and can set the snapshot number trigger for each and the time-period in days.

The reports will be sent to either the primary account holder or any alternative email address to ensure that the person responsible for investigating and fixing issues receives the alerts and warnings expediently.

Skeddly offers three options for viewing the reports – in an inline table in the email, as an HTML file attachment or an attached CSV file.

In the subject line of the email the recipient will be able to view the number of volumes in the report, the number of warnings and the number of alerts without having to open the email.

The new EBS volume snapshot report has been made available to users today.

Author: Richard Anderson

Richard Anderson is the Editor-in-Chief of