Description

The Restore RDS Cluster action can be used to restore an RDS Aurora cluster from an RDS cluster snapshot. Later, it can (optionally) be deleted.

For example, at 8am, a small RDS Aurora cluster can be restored from the latest snapshot of a production Aurora cluster for development purposes, then 8 hours later, it can be deleted.

Settings

Please see Common Action Settings for a description of settings common to all action types.

Snapshot Identification Method

Indicates how the source snapshot will be selected. Valid values are:

  • All Snapshots - Selects all cluster snapshots
  • By Snapshot ID - Selects snapshots by their unique snapshot ID
  • By RDS Cluster - Selects snapshots by their originating cluster
  • By Resource Tag - Selects snapshots by matching a resource tag on the snapshot

In all cases, if more than one snapshot is found, the most recent snapshot will be used to restore the RDS cluster.

Snapshot ID

Indicates the RDS snapshot ID comparison to use when finding snapshots.

Cluster ID

Indicates the RDS cluster ID comparison to use when finding snapshots.

Resource Tag Name

Indicates the name of a resource tag to use when matching snapshots.

Resource Tag Value

Indicates the resource tag value comparison to use when finding snapshots.

New RDS Cluster ID

Indicates the cluster identifier of the new RDS cluster. Macros can be used in the cluster ID to include run-time data.

Duplicate Cluster Resolution Method

Specifies how Skeddly should recover if a cluster already exists with the desired new cluster ID. Possible values include:

  • None - No resolution will be used. Skeddly will stop with an error.
  • Use existing cluster - The existing cluster will be used for the remainder of the action. If the action is configured to delete the cluster, the existing cluster will be deleted at that time.

DB Subnet Group Name

Optional. By default, new clusters will restore into the default VPC. To restore into a different VPC, specify the name of the RDS DB subnet group to use instead.

Cluster Parameter Group

Optional. Specify the name of a cluster parameter group to assign to the new cluster.

Security Groups

Optional. Specify the VPC security groups to assign to the new cluster. Security group names or IDs can be specified. Separate multiple security groups by commas, spaces, or new lines. The security groups must reside in the VPC into which the cluster is being restored.

Change Backup Retention

Specify whether the backup retention period should be changed for the new RDS cluster.

Resource Tags

Optional. Extra resource tags can be assigned to the new instance. Click "Add Tag" to add a tag and fill the tag data. Any number of tags can be set, although Amazon RDS has a limit of 10 (including the Name tag). Macros can be used in the tag values to include run-time data. See below.

New RDS Instance ID

An RDS instance will be attached to the new RDS cluster. Specify the ID of the new RDS cluster.

Instance Class

Specify the instance class (machine size) that the new RDS instance will be created as.

Change Publicly Accessible

Use this field to override the default publicly accessible value and explicitly set the new RDS instance as publicly accessible or not.

Delete the New Cluster

Indicate whether the new RDS cluster should be automatically deleted later. The running time of the cluster must also be specified if this is enabled.

Running Duration

Indicate the length of time the RDS cluster should remain running before it is deleted. This value is only required if "Delete the Instance" is enabled.

Create a Final Snapshot

Indicates whether a final snapshot should be created of the new RDS cluster when it is deleted. This value is only available if "Delete the new Cluster" is enabled.

Final Snapshot ID

Indicates the snapshot ID of the final snapshot when the cluster is deleted. This value is only required if "Create a Final Snapshot" is enabled. Macros can be used in the snapshot ID to include run-time data.

Amazon Commands Used

The following Amazon AWS commands are used. The access key should have permission to execute all of them.

  • ec2:DescribeAccountAttributes
  • ec2:DescribeSecurityGroups
  • rds:CreateDBInstance
  • rds:DeleteDBCluster
  • rds:DeleteDBInstance
  • rds:DescribeDBClusterSnapshots
  • rds:DescribeDBClusters
  • rds:DescribeDBInstances
  • rds:DescribeDBSubnetGroups
  • rds:ListTagsForResource
  • rds:ModifyDBCluster
  • rds:RebootDBInstance
  • rds:RestoreDBClusterFromDBSnapshot
Did this answer your question?