aws_kms_replica_key fails to create with a provided policy

[rpopovych]

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 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform 1.1.5
AWS Provider 3.74.0
Windows 10 64 bit

Affected Resource(s)

• aws_kms_replica_key

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

data "aws_caller_identity" "current" {}

data "aws_iam_policy_document" "this" {
  statement {
    sid       = "Key Administrators"
    actions   = ["kms:*"]
    resources = ["*"]

    principals {
      type = "AWS"
      identifiers = [
        data.aws_caller_identity.current.arn
      ]
    }
  }
}

resource "aws_kms_key" "this" {
  enable_key_rotation = true
  policy              = data.aws_iam_policy_document.this.json
  multi_region        = true
}

resource "aws_kms_replica_key" "this" {
  provider = aws.replication

  policy          = data.aws_iam_policy_document.this.json
  primary_key_arn = aws_kms_key.this.arn
}

Expected Behavior

terraform apply successfully executed.

Actual Behavior

terraform apply times out after 5 minutes.

Steps to Reproduce

1. terraform apply

Important Factoids

The key is created correctly with the correct policy, it seems like the provider is just thinking that policies are different.

I can successfully create the replica key without policy.
I can even update the policy and the update works correctly.
The issue is only when creating from scratch with policy.

References

• Order is lost for data aws_iam_policy_document when applied to S3 buckets, iam roles, kms keys, etc #11801

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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.