AWS Cloud Disaster Recovery And Backup Audit

Do you take backup of your data on AWS cloud on a regular basis? Do you have a backup fall-back for your Amazon EBS volumes and Amazon RDS databases?

A gentle reminder, your data is not safe unless you are backing up properly or else you might experience the nightmare of losing all your critical data due to any unexpected disaster event.

Botmetric scans your AWS infrastructure, to check if you have configured backup on RDS and EBS properly.

Here are all the disaster recovery checks that Botmetric performs to make sure that your backups are configured right.

Volume Snapshot

Botmetric provides a list of EBS volumes that either don’t have a snapshot or without the latest snapshot. It is recommended that you take regular snapshots of the required volumes for disaster recovery purpose.

You can use Botmeric’s DevOps Cloud Automation to schedule a job that automatically takes EBS volume snapshotsbased on specified instance or volume tags.

RDS Backup

Botmetric provides a list of RDS instances that either don’t have a backup or the backup retention period are not at the recommended level.

You can use Botmeric’s DevOps Cloud Automation to schedule a job that automatically takes your RDS data backup based on specified instance tags.

ELB Optimization

Botmetric provides a list of ELB either have only one availability zone or instances are distributed unevenly and distributed among different availability zones. For better Fault Tolerance, EC2 instances must be evenly distributed among different availability zones.

RDS Multi Availability Zone

Botmetric provides a list of DB instance is deployed in a single Availability Zone.

Route53 High TTL RR Set

Botmetric identifies a resource record set has a TTL greater than 60 seconds and either have an associated health check or its routing policy is Fail-over.

ELB Connection Draining

Botmetric identifies load balancers do not have connection draining configured and recommend you to enable connection draining to ensure in-flight requests are handled gracefully during auto-scaling termination or unhealthy instance removal events.

ELB Cross Zone

Botmetric identifies load balancers should be configured to use cross-zone load balancing option. This will ensure the requests are evenly distributed across all back-end instances irrespective of availability zones.



Botmetric’s AWS DR & Backup audit

EC2 Availability Zone

Botmetric identifies the region has either all the instances in same availability zones, or has instances in multiple zones, but the distribution is uneven.

Auto Scaling Group

Botmetric recommends you to have the health check type as ‘ELB’ if you use a load balancer with your Auto Scaling group and if you are not using any load balancers with Auto Scaling Group then you should choose the default health check as ‘EC2’

Auto Scaling Group Resources

Botmetric identifies which auto scaling group is associated with a deleted load balancer or a launch configuration is associated with a deleted Amazon Machine Image (AMI).

S3 Access Configuration

Botmetric identifies S3 buckets does not have correct logging configuration. When logging is initially enabled, the configuration is automatically validated,however, future modifications can result in logging failures.

You can take your disaster recovery strategy to a higher level by enabling your data backups to be copied across the AWS regions.

Using Botmetric’s DevOps Cloud Automation you can copy backups from a source AWS region to the destination AWS region.

Below are a couple of jobs scheduled using Cloud Automation for cross region copy :

Copy EBS Volume snapshot (based on volume tags) across regions

Copy RDS snapshot (based on RDS tags) across regions

Make sure your EBS volumes and RDS data gets backed up periodically, and you are ready for any disaster event. Do not wait. Try Botmetric for free.