From 110d4820336f8363f6d2077aeaf6170dc7d25303 Mon Sep 17 00:00:00 2001 From: Peter Mescalchin Date: Wed, 1 Sep 2021 13:59:08 +1000 Subject: [PATCH] Update S3 backend documentation - DynamoDB uses Partition keys, not primary keys --- website/docs/language/settings/backends/s3.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/language/settings/backends/s3.html.md b/website/docs/language/settings/backends/s3.html.md index 73f668e94..f6b9b9b69 100644 --- a/website/docs/language/settings/backends/s3.html.md +++ b/website/docs/language/settings/backends/s3.html.md @@ -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