Patrick Decat

Submitted https://github.com/turbot/steampipe-plugin-aws/pull/2082, PTAL :pray:

Test results: ``` # node tint.js tests/aws_s3_bucket/ No env file present for the current environment: staging Falling back to .env config No env file present for the current environment: staging...

Rebased on main following merge of https://github.com/turbot/steampipe-plugin-aws/pull/2080

Hi @cbruno10, > @pdecat Cross-posting here for better visibility - Did you notice any performance improvements, or other benefits? We had originally opened [that issue](https://github.com/turbot/steampipe-plugin-aws/issues/1586) because [AWS API docs](https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLocation.html) said...

Found my comment investigating the errors with `GetBucketLocation` that happen when hitting the wrong region with the AWS Go SDK that the Steampipe AWS plugin is using: https://github.com/turbot/steampipe-plugin-aws/issues/1586#issuecomment-1954154456 With Steampipe,...

Here's a related issue mentioning the error I'm facing https://github.com/turbot/steampipe-plugin-aws/issues/1713

Hi @vpartington, > FYI, instead of using `http.Head` you can also use [the `manager.GetBucketRegion` function](https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/feature/s3/manager#GetBucketRegion) in AWS SDK for Go v2. Interesting, this helper function does seem to do an...

Anyway, I've not faced any issue yet since I've switched to using HTTP HEAD two months ago. And it works even if the bucket is not yours: ``` # curl...

Hi @cbruno10, I've implemented the requested changes. PTAL :)

Can confirm everything also works fine with the use of `manager.GetBucketRegion()` instead of plain HTTP HEAD requests.