Unable to change certificate authority of a MySQL RDS instance to rds-ca-2019

[lyenliang]

According to #10417, this bug was fixed in AWS Provider v2.37.0. But why do I still encounter it in v2.40?

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.12.17
+ provider.aws v2.40.0

Affected Resource(s)

• aws_db_instance

Terraform Configuration Files

provider "aws" {
  region     = "ap-northeast-1"
  version    = "~> 2.40"    
}

resource "aws_db_instance" "test-ca-db" {
  instance_class       = "db.t3.micro"
  identifier           = "test-ca-db"
  snapshot_identifier  = "arn:aws:rds:ap-northeast-1:123456789123:snapshot:rds:my-snapshot"
  vpc_security_group_ids = ["sg-c98ejaq1","sg-06fue8sa4301cd064"]
  parameter_group_name = "my_group"
  publicly_accessible  = false
  password             = "1234abcd"
  skip_final_snapshot  = true
  storage_encrypted    = true
  ca_cert_identifier   = "rds-ca-2019"
}

Debug Output

Panic Output

Expected Behavior

The RDS instance's certificate authority should be changed to rds-ca-2019.

Actual Behavior

The RDS instance's certificate authority remains in rds-ca-2015.

Steps to Reproduce

1. terraform apply

Important Factoids

References

• Terraform RDS - Does not support updating - ca_cert_identifier #10417, add ca_cert_identifier to rds instance #10490

[huseyinham]

Hopefully this doesn't sound patronising, but someone in the PR you referenced mentioned they needed to set apply_immediately = true for it to actually take effect. Would that solve your issue? Or is this behaviour after you tried that?

Link for reference:
#10417 (comment)

[lyenliang]

Thank you @huseyinham, apply_immediately = true solves my problem.

[ghost]

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!