[Bug]: DynamoDB table on_demand_throughput errors when only one of max_write_request_units or max_read_request_units is specified

[magreenbaum]

Terraform Core Version

1.5.7

AWS Provider Version

5.72.1

Affected Resource(s)

aws_dynamodb_table.on_demand_throughput

Expected Behavior

Be able to specify either max_read_request_units or max_write_request_units but not require both.

Actual Behavior

Specifying only one of max_write_request_units or max_read_request_units in aws_dynamodb_table.on_demand_throughput produces an error.

Relevant Error/Panic Output Snippet

╷
│ Error: creating AWS DynamoDB Table (my-test-table): operation error DynamoDB: CreateTable, https response error StatusCode: 400, RequestID: T60PQN6LMJLJ73DTJ1MCRMMD33VV4KQNSO5AEMVJF66Q9ASUAAJG, api error ValidationException: One or more parameter values were invalid: Requested MaxWriteRequestUnits for OnDemandThroughput for table is outside of valid range
│ 
│   with aws_dynamodb_table.this,
│   on main.tf line 67, in resource "aws_dynamodb_table" "this":
│   67: resource "aws_dynamodb_table" "this" {
│ 
╵

Terraform Configuration Files

resource "aws_dynamodb_table" "this" {
  name = "my-test-table"
  hash_key                    = "id"
  range_key                   = "title"
  table_class                 = "STANDARD"
  deletion_protection_enabled = false
  billing_mode = "PAY_PER_REQUEST"
  attribute {
    name = "id"
    type = "N"
  }
  attribute {
    name = "title"
    type = "S"
  }
  on_demand_throughput {
    max_read_request_units  = 50
  }
}

Steps to Reproduce

Run terraform apply with provided code with only max_read_request_units specified.

Debug Output

No response

Panic Output

No response

Important Factoids

Docs indicate arguments are optional and that you should be able to specify one or both.
https://github.com/hashicorp/terraform-provider-aws/blob/main/website/docs/r/dynamodb_table.html.markdown#on_demand_throughput

You can specify only one if you manually configure this via console or CLI.

References

No response

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]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

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