[BUG][exporter/awss3] Newer versions path has extra "/" prefix

[portswigger-tim]

Component(s)

exporter/awss3

What happened?

Description

In v0.115.0 the aws s3 exporter uploads files to a path like:
s3://sniffler-l4hsf/year=2025/month=01/day=10/hour=00/minute=05/traces_760872934.json

In v0.117.0 paths have an extra "/" prefix:
s3://sniffler-l4hsf//year=2025/month=01/day=15/hour=14/minute=55/traces_948440739.json

This leads to files not being available in the expected place. I suspecte that this was introduced in: #36698

Steps to Reproduce

Configure exporter to ship to S3 on the two different versions.

Expected Result

Paths do not have an extra "/"

Actual Result

Paths have an extra "/"

Collector version

v0.117.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

Log output

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/awss3: @atoulme @pdelewski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[portswigger-tim]

I suspect that this line is the cause: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36698/files#diff-527f944a938a0dd5e7cab3825a123d2571a44fc3d4158046095070b51cf6390eR61

It does not account for not having a PartitionPrefix.

[portswigger-tim]

Possibly related to a difference between SDK v1 and v2 handling of paths / urls: aws/aws-sdk-go-v2#1701 (comment)

[VihasMakwana]

@portswigger-tim I suspect that the file ends up in an "empty" folder?

[VihasMakwana]

@portswigger-tim can you share your collector configuration?

[KevinThompsonYCRX]

Also seeing this extra path even with a partition prefix

edit: Nevermind, I was providing a leading '/'. Removing it put my other folder in the root

[portswigger-tim]

@VihasMakwana - here is the exporter config I am using:

exporters:
  awss3:
    s3uploader:
      region: ${env:AWS_REGION}
      s3_bucket: ${env:S3_BUCKET_NAME}