[Enhancement]: Change TF behavior to complete operation of create / update RDS Clusters and Instances faster

[pthawley]

Description

When creating or adding new clusters or database instances in RDS and Aurora. the instance is available for use during the "Storage-optimization" phase. See the public AWS documentation here and the AWS Knowledge Center article here.

Therefore, the TF operations that create or modify these resources should complete when the target state is either "Available" or "Storage-optimization".

Today, in there cases where the "Storage-optimization" phase is taking a long time, one of several possibilities could occur. Either the operation takes significantly more time than is actually needed or, in some extreme cases, it is possible that operation times out and fails. Neither is a good experience.

I am not really familiar with Terraform or the AWS Provider code but in looking at the wait.go file here, both the waitDBClusterInstanceCreated and waitDBClusterInstanceUpdated functions both view InstanceStatusStorageOptimization as a "Pending" state.

I was originally going to call this a bug and not an enhancement request but I don't have all of the information to create a reproducible test case. In the interest of getting this into the system faster, as well as the recognition that the existing code has been in place for a long time, please consider this hopefully small change.

Affected Resource(s) and/or Data Source(s)

Resource: aws_rds_cluster
Resource: aws_rds_cluster_instance

Potential Terraform Configuration

No response

References

See the public AWS documentation here and the AWS Knowledge Center article here.

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[ewbankkit]

Relates #6455.
Relates #21900.
The equivalent change for aws_db_instance was done (accidentally maybe, but no reported issues) in 763e52f.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.72.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!