rds_cluster: Add support for more states (stopped, started, restarted)

[ohmer]

Summary

I am trying to implement a playbook to stop and start an application environment to save money.
The stack includes RDS Aurora clusters and the AWS collection only supports present and absent states.

AWS added support to interrupt RDS clusters temporarily with some caveats:

• https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_StopInstance.html
• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-cluster-stop-start.html

It would be great to have support for these additional states for us and the community. Automated solution exists (example: https://aws.amazon.com/blogs/database/save-costs-by-automating-the-start-and-stop-of-amazon-rds-instances-with-aws-lambda-and-amazon-eventbridge/) but I would like to provide the flexibility to our development team to do it on demand, not on schedule.

Issue Type

Feature Idea

Component Name

rds_cluster

Additional Information

- name: Get database cluster information
  amazon.aws.rds_cluster_info:
    cluster_name: "{{ rds_cluster_name }}"
    region: "{{ aws_region }}"
  register: cluster_info

- name: Stop database cluster (AWS restarts it automatically after 7 days)
  amazon.aws.rds_cluster:
    db_cluster_identifier: "{{ cluster_info.clusters[0].db_cluster_identifier }}"
    state: stopped

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• [plugins/modules/rds_cluster.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/rds_cluster.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @alinabuzachis @jillr @s-hertel @tremble
click here for bot help