Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamodb use server_side_encryption #18310

Closed
ctippur opened this issue Jun 22, 2018 · 2 comments
Closed

Dynamodb use server_side_encryption #18310

ctippur opened this issue Jun 22, 2018 · 2 comments

Comments

@ctippur
Copy link

ctippur commented Jun 22, 2018

Terraform Version

0.11.7

Terraform Configuration Files

resource "aws_dynamodb_table" "user-table" {
  name           = "Testing"
  read_capacity  = 5
  write_capacity = 5
  hash_key       = "UserId"

  server_side_encryption {
    enabled = true
  }

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

Debug Output

Error: module.ddb.aws_dynamodb_table.user-table: : invalid or unknown key: server_side_encryption

Crash Output

Expected Behavior

Should have gone ahead and created the table.

Actual Behavior

got the error mentioned above

Steps to Reproduce

  1. terraform init
  2. terraform apply

Additional Context

References

https://www.terraform.io/docs/providers/aws/r/dynamodb_table.html#server_side_encryption

@ghost
Copy link

ghost commented Jun 22, 2018

This issue has been automatically migrated to hashicorp/terraform-provider-aws#4949 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#4949.

@ghost ghost closed this as completed Jun 22, 2018
@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants