Still unable to disable TTL on DynamoDB table

[carschandler]

Terraform and AWS Provider Version

Terraform v1.13.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/archive v2.7.1
+ provider registry.terraform.io/hashicorp/aws v6.17.0

Affected Resource(s) or Data Source(s)

• aws_dynamodb_table

Expected Behavior

ttl.enable = false with an empty ttl.attribute_name should disable TTL for the table

Actual Behavior

Getting an API error due to having an attribute name with 0 length.

Relevant Error/Panic Output

aws_dynamodb_table.sessions: Modifying... [id=ConversationSessions]
╷
│ Error: updating AWS DynamoDB Table (ConversationSessions): updating Time To Live: operation error DynamoDB: UpdateTimeToLive, https response error StatusCode: 400, RequestID: F5TVSR1QR3RGHDSTJS7R0G9R13VV4KQNSO5AEMVJF66Q9ASUAAJG, api error ValidationException: 1 validation error detected: Value '' at 'timeToLiveSpecification.attributeName' failed to satisfy constraint: Member must have length greater than or equal to 1
│
│   with aws_dynamodb_table.sessions,
│   on main.tf line 248, in resource "aws_dynamodb_table" "sessions":
│  248: resource "aws_dynamodb_table" "sessions" {
│
╵

Sample Terraform Configuration

Click to expand configuration

resource "aws_dynamodb_table" "sessions" {
  name         = local.session_table_name
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "sessionId"

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

  ttl {
    enabled = false
  }
}

Steps to Reproduce

1. Create a table with TTL enabled using a valid attribute name
2. Wait an hour (sorry; AWS restriction on how frequently you can modify TTL)
3. Comment out the attribute name from tf spec and switch to enabled = false
4. terraform apply

Debug Logging

No response

GenAI / LLM Assisted Development

n/a

Important Facts and References

This was supposedly fixed in #39195 but still observing the same behavior.

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue 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.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[JanSolo1]

The AWS API requires attribute name if you are trying to disable ttl of an existing table with ttl enabled.
Basically just a quirk of the API : )

[carschandler]

The AWS API requires attribute name if you are trying to disable ttl of an existing table with ttl enabled.
Basically just a quirk of the API : )

Okay so I initially had left the attribute name and just flipped enabled to false but I noticed that when I would apply after some period of time that disabling TTL would be part of the proposed changes again, as though it was never actually applied the first time. This led me to revisit the docs for the resource, which states the following for ttl.attribute_name at the bottom:

"Name of the table attribute to store the TTL timestamp in. Required if enabled is true, must not be set otherwise."

This would seem to contradict what you're saying about the AWS API; does it need to be fixed?