-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Resource]: aws rds modify-certificates #33196
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hi, I have PR opened for this new resource here : #35003 |
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. |
This functionality has been released in v5.59.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! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
As of this writing on August 27, 2023, the default RDS CA certificate is
rds-ca-2019
, which expires 2024-08-22. If a user creates a new RDS instance anytime prior to 2024-08-22, and they don't explicitly request a different CA certificate via theaws_rds_instance.foo.ca_cert_identifier
attribute, then presumably their instance will get thisrds-ca-2019
certificate.AWS has an API for
aws rds modify-certificates
, which lets you override the account-level default for new RDS instances. It would be useful if Terraform had a resource which supported this API.If such a resource existed, a person could upgrade all their existing RDS instances to a newer and longer-duration certificate (using the
aws_rds_instance.foo.ca_cert_identifier
attribute), and then use this resource to set the account-level default for new instances so that they no longer have to worry about the old certificate ever being used again.Requested Resource(s) and/or Data Source(s)
aws_rds_account_default_ca_certficate
(or something along those lines)Potential Terraform Configuration
References
https://docs.aws.amazon.com/cli/latest/reference/rds/modify-certificates.html
https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyCertificates.html
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: