-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Acceleration NotImplemented error with third party S3 implementation #13726
Comments
I didn't see a |
A skip parameter would be perfect. I could also do with this for Wasabi S3 since it doesn't support replication. |
@dr4Ke @hongkongkiwi @jbuchhammer - I've opened up a pull request with the skip_* features implemented at #17564 - hopefully it goes through :) - you can have a look, see if it |
@mflorin Thanks for your PR, we are looking for similar change with even more options. Hope your PR will be approved. |
There are also providers, which do not support versioning e.g. Strato HiDrive S3. |
According to the FAQ I can speed up the PR#17564 merge by describing bad UX.
It is slower, multiple commands instead of one increases possibility the bucket creation to fail, hard to debug what went wrong. |
Third party S3 might reply `NotImplemented` error when creating a bucket. This error prevent the successful apply of the plan. Example when checking policy: ``` ╷ │ Error: error getting S3 bucket ([redacted]) policy: NotImplemented: The requested resource is not implemented │ status code: 501, request id: [redacted], host id: [redacted] │ │ with aws_s3_bucket.lts, │ on main.tf line 22, in resource "aws_s3_bucket" "lts": │ 22: resource "aws_s3_bucket" "lts" { │ ╵ ``` Example when checking for payment: ``` ╷ │ Error: error getting S3 Bucket request payment: NotImplemented: The requested resource is not implemented │ status code: 501, request id: txc25b2f0fe509409081b8b-00620fcb0c, host id: txc25b2f0fe509409081b8b-00620fcb0c │ │ with aws_s3_bucket.lts, │ on main.tf line 23, in resource "aws_s3_bucket" "lts": │ 23: resource "aws_s3_bucket" "lts" { │ ╵ ``` Closes: hashicorp#14645, hashicorp#13726 Signed-off-by: Wilfried Roset <[email protected]>
This functionality has been released in v4.2.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
When using a different S3 implementation (here Cloudian), the bucket gets created but the terraform states still fails, due to Acceleration not being implemented server side.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/dr4Ke/b27bdf40fa54dbe9da92a9085380cdeb
Panic Output
N/A
Expected Behavior
The bucket gets created and
terraform apply
succeeds.Actual Behavior
The bucket gets created but the
terraform apply
fails with error:It is due to the Acceleration not being implemented. Subsequents run of
terraform plan
gives the same error.Detailed output:
Steps to Reproduce
terraform apply
Important Factoids
Please note this is happening on a S3 implementation that's not Amazon's.
References
acceleration_status = null
parameterThe text was updated successfully, but these errors were encountered: