-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_s3_bucket server_side_encryption_configuration key is not recognized #2704
Comments
You are using a very old version of |
That does appear to be the case, so it's still a bug as the behavior is that it's supposed to be automatically upgraded if it wasn't explicitly defined, right? I had to pin it to that version for it to download.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Nguyen Kien Trung <notifications@github.com>
Sent: Monday, December 18, 2017 6:19:18 PM
To: terraform-providers/terraform-provider-aws
Cc: Ian Cornett; Author
Subject: Re: [terraform-providers/terraform-provider-aws] aws_s3_bucket server_side_encryption_configuration key is not recognized (#2704)
You are using a very old version of terraform-provider-aws: terraform-provider-aws_v1.3.1_x4
Please take the latest 1.6.0 which supports server_side_encryption_configuration
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#2704 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AfOtFHEqAZyKXVExaOCdDaA9XQVi-dgeks5tBx0mgaJpZM4RGSNS>.
|
By design it won't perform auto upgrade unless being asked. |
I am using
When running
But I still get the same error that was reported here:
UPDATE: Sorry! I was specifying this on a aws_s3_bucket_policy, not aws_s3_bucket. I moved it, and now it works fine. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Run
terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.Terraform v0.11.1
Affected Resource(s)
Please list the resources as a list, for example:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
https://gist.github.com/icornett/2873038776bcf9be8211f4047e587e8c
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Expected Behavior
What should have happened?
S3 bucket should be created with encryption, per documentation
Actual Behavior
What actually happened?
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: