(rds): scheduling modifications in the next scheduled maintenance window

[Tietew]

Describe the feature

CloudFormation has added applyImmediately feature to RDS instance.
This allows to schedule modifications in the next scheduled maintenance window.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbinstance.html#cfn-rds-dbinstance-applyimmediately
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ModifyInstance.ApplyImmediately.html

Use Case

We can avoid rebooting database instances during update.

Proposed Solution

Add applyImmediately in instance props.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.178.2

Environment details (OS name and version, etc.)

Linux

[Tietew]

This seems to be applied to database instances only (including instances under Aurora cluster), not cluster.
When I try to upgrade Aurora engine version via CloudFormation, it's applied immediately even if instances have applyImmediately: false. Modifying instance size is scheduled expectedly.

To modify cluster configurations such as Aurora engine version in the next scheduled maintenance window, we must use CLI or management console currently.

rds:ModifyDBCluster API has ApplyImmediately:
https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBCluster.html

AWS::RDS::DBCluster resource doesn't have:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html

[Tietew]

Note Aurora supports zero-downtime patching
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html

[pahud]

Thank you. Let's keep this moving forward from your PR.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.