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.

from terraform-provider-aws.

Hey @pnjha 👋 Thank you for taking the time to raise this! Can you supply a sample Terraform configuration that can be used to reproduce and, if possible, debug logs (redacted as necessary) this so that whoever looks into this issue has the information they need to get started?

from terraform-provider-aws.

Hi @justinretzolk, we have nothing special in the terraform configuration to perform the PITR. We follow the doc present here https://registry.terraform.io/providers/hashicorp/aws/4.67.0/docs/resources/db_instance. We learned from AWS that from Jan 26, 2024, the default CA will be rds-ca-rsa2048-g1. This may be the problem that during the restore process, the provider is not looking at the CA provided in the template but rather relying on AWS to pick the default. This is further supported by our observation that this issue started appearing after Jan 26, 2024.

Let me know if you still feel the need to provide the terraform template that we are using.

from terraform-provider-aws.