Update S3 backend documentation - DynamoDB uses Partition keys, not primary keys
This commit is contained in:
parent
7c02ef6220
commit
110d482033
|
@ -200,7 +200,7 @@ The following configuration is optional:
|
|||
The following configuration is optional:
|
||||
|
||||
* `dynamodb_endpoint` - (Optional) Custom endpoint for the AWS DynamoDB API. This can also be sourced from the `AWS_DYNAMODB_ENDPOINT` environment variable.
|
||||
* `dynamodb_table` - (Optional) Name of DynamoDB Table to use for state locking and consistency. The table must have a primary key named `LockID` with type of `string`. If not configured, state locking will be disabled.
|
||||
* `dynamodb_table` - (Optional) Name of DynamoDB Table to use for state locking and consistency. The table must have a partition key named `LockID` with type of `String`. If not configured, state locking will be disabled.
|
||||
|
||||
## Multi-account AWS Architecture
|
||||
|
||||
|
|
Loading…
Reference in New Issue