AWS Config Rule: EC2 Last Backup Recovery Point Created

Description: Checks if a recovery point was created for Amazon Elastic Compute Cloud (Amazon EC2) instances. The rule is NON_COMPLIANT if the Amazon EC2 instance does not have a corresponding recovery point created within the specified time period.

Trigger type: Periodic

AWS Region: All supported AWS regions except China (Beijing), Asia Pacific (Jakarta), Middle East (UAE), Asia Pacific (Hyderabad), Asia Pacific (Osaka), Asia Pacific (Melbourne), AWS GovCloud (US-East), AWS GovCloud (US-West), Europe (Spain), China (Ningxia), Europe (Zurich) Region

This AWS Config Rule will check each EC2 instance in your account, within each region too.

This AWS Config Rule takes two parameters when calculating wether or not you have a backup recovery point created within your time period, they are;

• recoveryPointAgeValue
• recoveryPointAgeUnit

By default, StackZone sets these to equate to one day - which means if you have a backup recovery point for your EC2 instance which is within the last day - you will show as COMPLIANT for this particular AWS Config Rule. If a backup recovery point does not exist within that timeframe, it will show as NON_COMPLIANT

To get to this point, you will need to incorporate AWS Backup. This StackZone article shows how you can use the Backup feature offered by StackZone, which may help you get Backup Standards up to scratch.

StackZone can automatically resolve your non-compliant EC2 Instances by running an automation script to enable enhanced monitoring for you.

To enable this remediation, within the StackZone console head on over to Baseline Services -> AWS Config Rules Regional -> Amazon EC2 and enable EC2 Instance Last Backup Recovery Point Created Remediation

Want to know more about StackZone and how to make your cloud management simple and secure?

Check our how it works section with easy to follow videos or just create your own StackZone Account here