I recently upgraded my opentelemetry collector and ran across an issue with the new v2 aws sdk along with a google cloud storage using S3 compatibility API.

[atoulme]

          I recently upgraded my opentelemetry collector and ran across an issue with the new v2 aws sdk along with a google cloud storage using S3 compatibility API.

The issue is described here: aws/aws-sdk-go-v2#1816 and also here: https://stackoverflow.com/questions/73717477/gcp-cloud-storage-golang-aws-sdk2-upload-file-with-s3-interoperability-creds

It seems the sdk v2 is no longer compatible with GCS at least without injecting some middleware code to mangle some headers.

Would you consider adding this "workaround" or is it out of scope ?

It seems there is no native GCS exporter equivalent to awss3 exporter.

Originally posted by @rslinckx in #36698 (comment)

[github-actions]

Pinging code owners for exporter/awss3: @atoulme @pdelewski. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[atoulme]

@rslinckx we can add the workaround but what would that look like? Would you be willing to contribute it?