Enable deletion protection for RDS Aurora DB clusters

This workflow enables the deletion protection feature for Aurora DB clusters. Deletion protection prevents any existing or new Aurora database cluster, regardless of its type - provisioned or serverless, from being terminated by a root or IAM user using the AWS Management Console, AWS CLI or AWS API calls, unless the feature is explicitly disabled

Adopt Template

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Resource

Select resources on which you want to work on.

Gets D B Clusters in a specific AWS Region for RDS service.

Filter

Enter parameters to filter resources in the workflow.

Filters the data

User Approval

Use this to get approval from stakeholder to continue the workflow.

Fulfils organizational obligation(if any) before taking any action on an AWS resource.

Action

Select action to be done on resources in the workflow.

Modify D B Cluster in a specific AWS Region for RDS service.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.
Gets D B Clusters in a specific AWS Region for RDS service.

Resource

Select resources on which you want to work on.

Filter

Enter parameters to filter resources in the workflow.

Filters the data

User Approval

Use this to get approval from stakeholder to continue the workflow.

Fulfils organizational obligation(if any) before taking any action on an AWS resource.

Action

Select action to be done on resources in the workflow.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.
Adopt Template

Workflow Template

Trigger

Use this to initiate a workflow based on time, events or call.

Runs everyday.

Resource

Select resources on which you want to work on.

Gets D B Clusters in a specific AWS Region for RDS service.

Filter

Enter parameters to filter resources in the workflow.

Filters the data

User Approval

Use this to get approval from stakeholder to continue the workflow.

Fulfils organizational obligation(if any) before taking any action on an AWS resource.

Action

Select action to be done on resources in the workflow.

Modify D B Cluster in a specific AWS Region for RDS service.

Create A Template

Thank you! Your submission has been received!
Oops! Something went wrong while submitting. Please Try Again.

Request for a template

You can publish templates created by you on this platform.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Similar Templates

Remove entries in Security Group which allow https access on public ip

It is AWS best practice to remove entries in security group which allows HTTPS access from public IP to reduce possibility of breach. Allowing unrestricted HTTPS access can increase threats like hacking, denial-of-service (DoS) attacks and loss of data

Reboot RDS DB instances if DB connections goes high ( Triggered by JIRA ).

Jira ticket with required summary will trigger this workflow. RDS DB Instances having the same tag that are mentioned in the description of jira ticket will get rebooted. This will reduce the CPUUtilization of the DB instance.

RDS DB instances MultiAZ alteration.

This workflow enables the MultiAZ for RDS DB instances and then after a delay of 1 hour it forces it to fail over. Again after 1 hour of delay it disables the MultiAZ feature for the RDS DB instances and then sends a report