Use the recommended CA if none are specified #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If var.ca_cert_identifier is not specified, the RDS creation will default to using the CA with id rds-ca-2019
That CA reaches end of life in some months, and AWS has already starting sending emails to database owners that have yet not upgraded.
The new suggested ID is rds-ca-ecc384-g1, and it can be calculated using the data source used in a PR.
PLEASE NOTE: If you already created the database, the certifification change will take place IN THE NEXT MAINTENANCE WINDOW unless you also use var. apply_immediately = true