Terraform + DynamoDB: All attributes must be indexed

46
votes

I want to create a Terraform configuration for DynamoDB table with multiple (> 10) attributes. And I have no need to add all attributes as an index to global_secondary_index or local_secondary_index. But when I run terraform plan command I have next error:

All attributes must be indexed. Unused attributes: ...

I found the validation check in the Terraform repository in validateDynamoDbTableAttributes function.

But also as I know the best practice is that each table in DynamoDB is limited to a maximum of five global secondary indexes and five local secondary indexes from General Guidelines for Secondary Indexes in DynamoDB.

And since I have more than 10 attributes it looks like a problem to me.

What I would like to understand why all attributes must be indexed and what to do in case if you have a big number of attributes.

Thanks!

2
amazon-dynamodbterraform

2 Answers

76
votes

You do not have to define every attribute you want to use up front when creating your table.

attribute blocks inside aws_dynamodb_table resources are not defining which attributes you can use in your application. They are defining the key schema for the table and indexes.

For example, the following Terraform defines a table with only a hash key:

resource "aws_dynamodb_table" "test" {
  name           = "test-table-name"
  read_capacity  = 10
  write_capacity = 10
  hash_key       = "Attribute1"

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

Every item in this table has Attribute1, but you can create additional attributes with your application Two items, both have Attribute1, but differing custom attributes

This means that you can have your 10+ attributes as long as you don't need to define them in an AttributeDefinition, and since you say you don't need them to be indexed, you'll be fine.

For some discussion of the confusion (attribute is confusing and doesn't match the DynamoDB API), see this pull request.

0
votes

I was adding a projected field to an LSI and put an attribute entry in for the projected field. This was causing the error. You can just list the projected field in the non_key_attributes as shown below, it doesn't have to be defined as an attribute since it's not a key:

local_secondary_index {
  name = "allocated_plus_created-lsi"
  range_key = "allocated_plus_created"
  projection_type = "INCLUDE"
  non_key_attributes = ["allocated"]
}

Allocated shouldn't be defined as an attribute for TF.