Skip to content

Latest commit

 

History

History
 
 

rds_backup

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

AWS RDS Backup

What it does

This Policy Template will check your account for Amazon RDS Instances with non-compliant backup settings.

Input Parameters

This policy has the following input parameters required when launching the policy.

  • Allowed Regions - A list of allowed regions for an AWS account. Please enter the allowed regions code if SCP is enabled, see Available Regions in AWS; otherwise, the policy may fail on regions that are disabled via SCP. Leave blank to consider all the regions.
  • Email addresses of the recipients you wish to notify - Email to alert when it finds S3 buckets that meet the criteria.
  • Backup Retention Period - Example value: 7
  • Preferred Backup Window - Example value: 08:00-08:30

Policy Actions

The following policy actions are taken on any resources found to be out of compliance.

  • Send an email report

Prerequisites

This policy uses credentials for connecting to the cloud -- in order to apply this policy you must have a credential registered in the system that is compatible with this policy. If there are no credentials listed when you apply the policy, please contact your cloud admin and ask them to register a credential that is compatible with this policy. The information below should be consulted when creating the credential.

Credential configuration

For administrators creating and managing credentials to use with this policy, the following information is needed:

Provider tag value to match this policy: aws , aws_sts

Required permissions in the provider:

{
  "Version":"2012-10-17",
  "Statement":[
    {
        "Sid":"AllowRDSDescribe",
        "Effect":"Allow",
        "Action":"rds:DescribeDBInstances",
        "Resource":"*"
    },
    {
      "Effect":"Allow",
      "Action":["ec2:DescribeRegions"],
      "Resource":"*"
    }
  ]
}

Supported Clouds

  • AWS

Cost

This Policy Template does not launch any instances, and so does not incur any cloud costs.