GetBucketAccelerateConfiguration Details - NotImplemented error with third party S3 implementation #23291
Comments
github-actions
bot
added
the
needs-triage
|
Looking at
I wonder if there's a quick way to test their availability on this third party S3 implementation without having to open a new issue for each as we work through them. Thoughts? |
|
same error here. Would be in general a good Idea, that these additional config options were optionally |
anGie44
added
service/s3
|
Hi @command-tab , thank you for creating this issue! This looks like a great place to aggregate all the S3 methods that are facing this issue so it may help create 1 uniform solution. |
anGie44
added
the
technical-debt
|
Hi! We are interested in this improvement too! Check our last commits on this topic: |
|
On this topic, would it be an option to improve the documentation here as to include how to use this provider with non-default S3 solutions? |
|
I was hoping that 4.9.0's inclusion of the resource "aws_s3_bucket_accelerate_configuration" "uploads" {
bucket = "mybucket"
status = "Suspended"
}
resource "aws_s3_bucket" "uploads" {
bucket = "mybucket"
}And still got this error while TF state was being refreshed: |
|
Checking in. It seems like the attempted read of bucket accelerate config is still present in version 4.18.0 of this provider and it is not safely ignoring the XNotImplemented response. Using the following Terraform config... provider "aws" {
region = "us-east-1"
access_key = "REDACTED"
secret_key = "REDACTED"
skip_credentials_validation = true
skip_get_ec2_platforms = true
skip_metadata_api_check = true
skip_region_validation = true
skip_requesting_account_id = true
endpoints {
s3 = "https://storagegrid.mycompany.com"
}
}
resource "aws_s3_bucket" "mybucket" {
bucket = "mybucket"
}I see (by increasing the <?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>XNotImplemented</Code>
<Message>The request you provided implies functionality that is not implemented.</Message>
<Resource>/mybucket?accelerate</Resource>
</Error>...and Terraform reports... And just to verify: |
|
Adding more support for this...facing a similar issue with another 3rd party S3 storage appliance Debug Output |
…ation To better support 3rd party S3 storage systems which may not implement these capabilities (such as EMC ECS). Potentially resolves GitHub Issues: hashicorp#23291 (comment)
…ation To better support 3rd party S3 storage systems which may not implement these capabilities (such as EMC ECS). Potentially resolves GitHub Issues: #23291 (comment)
…plication_configuration` reads (#29348) * Ignore errors for GetBucketLifecycleConfiguration and GetBucketReplication To better support 3rd party S3 storage systems which may not implement these capabilities (such as EMC ECS). Potentially resolves GitHub Issues: #23291 (comment) * chore: changelog --------- Co-authored-by: absa-rsuarez <[email protected]>
|
This functionality has been released in v5.32.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. |
Following hot on the heels of the resolution of #14645 (thank you!), the
aws4.2.0 provider is erroring when my NetApp StorageGRID S3 emulation returns 501 Not Implemented with anXNotImplementederror code (in the XML) when the provider performs a GET onmybucket.storagegrid.mycompany.com/?accelerate=. Apparently fetching bucket transfer acceleration is also not implemented, just like fetching a bucket's static website configuration was not supported. Would it be possible to ignoreXNotImplementedin this call in a similar way to how it was handled for #14645?Here's the Terraform log:
I'm not sure how many calls like this there are beyond this one. I thought static website configuration would be the only one, but then this cropped up, and I'm not sure if there are others beyond this that will encounter the same issue. I'd be curious what other calls there are that might be problematic.
The text was updated successfully, but these errors were encountered: