DynamoDB Global Table Version 2 Replicas don't propagate tags to replica

[whume]

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

Description

A switch should be added to the dynamodb replica to propagate tags over to the replica table. Currently the tagging option is available in the UI but tags are empty after creation of a replica.

New or Affected Resource(s)

"aws_dynamodb_table"

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
resource "aws_dynamodb_table" "dynamodb_table" {
  replica {
    region_name = "us-east-2"
    propagate_tags = true
  }
}

References

• #0000

[ewbankkit]

This can be achieved using the aws_dynamodb_tag resource:

• Unable to tag DynamoDB global table replicas #13725
• provider: Introduce tag resource generator, new aws_dynamodb_tag and aws_ecs_tag resources #13783

For example, something like:

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

provider "awsalternate" {
  region = "us-west-2"
}

data "aws_region" "alternate" {
  provider = "awsalternate"
}

data "aws_region" "current" {}

resource "aws_dynamodb_table" "test" {
  provider = "awsalternate"

  billing_mode     = "PAY_PER_REQUEST"
  hash_key         = "TestTableHashKey"
  name             = %[1]q
  stream_enabled   = true
  stream_view_type = "NEW_AND_OLD_IMAGES"

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

  replica {
    region_name = data.aws_region.current.name
  }
}

# Set the tag on the replica.
resource "aws_dynamodb_tag" "test" {
  resource_arn = replace(aws_dynamodb_table.test.arn, data.aws_region.alternate.name, data.aws_region.current.name)
  key          = "testkey"
  value        = "testvalue"
}

[ewbankkit]

Use of the aws_dynamodb_tag may not be a suitable solution if the AWS Regions are dynamically determined (and so would use the for_each syntax to configure the replica blocks) and Terraform modules are used.

We could add a tags argument into the replica block, e.g.

resource "aws_dynamodb_table" "test" {
  ...

  replica {
    region_name = "us-east-1"

    tags = {
      Usage = "Primary"
    }
  }

  replica {
    region_name = "us-east-2"

    tags = {
      Usage = "Secondary"
    }
  }
}

and document carefully that this would conflict with use of the aws_dynamodb_tags resource.

[github-actions]

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