[Bug]: Enabling PITR on DynamoDB replica should not cause recreation

[szesch]

Terraform Core Version

1.3.7

AWS Provider Version

4.52.0

Affected Resource(s)

• aws_dynamodb_table

Expected Behavior

When enabling PITR on a dynamodb replica it should update the PITR setting without deleting and recreating a replica. An in-place update is the behavior of the AWS CLI. Example of achieving this with the CLI aws dynamodb update-continuous-backups --region us-west-2 --table-name replica-pitr-test --point-in-time-recovery-specification PointInTimeRecoveryEnabled=true.

Actual Behavior

The replica is deleted and then a new one is created.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

provider "aws" {
  region  = "us-east-2"
}

provider "aws" {
  region  = "us-west-2"
  alias   = "uswest2"
}

provider "aws" {
  region  = "eu-west-2"
  alias   = "euwest2"
}

resource "aws_kms_key" "us_east_2" {
  description = "CMK for us-east-2"
}

resource "aws_kms_key" "us_west_2" {
  description = "CMK for us-west-2"
  provider    = aws.uswest2
}

resource "aws_kms_key" "eu_west_2" {
  description = "CMK for eu-west-2"
  provider    = aws.euwest2
}

resource "aws_dynamodb_table" "test" {
  name           = "replica-pitr-test"
  billing_mode   = "PAY_PER_REQUEST"
  hash_key       = "id"
  stream_enabled = true

  point_in_time_recovery {
    enabled = true
  }

  server_side_encryption {
    enabled     = true
    kms_key_arn = aws_kms_key.us_east_2.arn
  }

  attribute {
    name = "id"
    type = "S"
  }

  replica {
    region_name = "us-west-2"
    kms_key_arn = aws_kms_key.us_west_2.arn
    point_in_time_recovery = true
  }

  replica {
    region_name = "eu-west-2"
    kms_key_arn = aws_kms_key.eu_west_2.arn
    point_in_time_recovery = true
  }
}

Steps to Reproduce

• terraform init
• terraform plan -out plan
• terraform apply
• Set point_in_time_recovery = true on a replica
• terraform plan -out plan
• terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

I believe this issue was caused by #29102

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.

[github-actions]

This functionality has been released in v4.54.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!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.