Upload to s3 failing in v0.22.0

[jchanam]

Describe the bug
Popeye fails to upload the report to s3. It tries to create a bucket and fails. When doing some digging, the upgrade of the client loos like the issue, as now it forces to set the region of the bucket.

Until now, when running inside k8s, it reads automatically the region it's in and worked without issues. v0.21.7 works without this problem.

To Reproduce
Steps to reproduce the behavior:

1. Run popeye inside an EKS cluster
2. Run with options as provided in the screnshot
3. Don't provide s3 region

Expected behavior
Popeye to upload the file without issues, discovering the region itself.

Screenshots

Options given:

Versions (please complete the following information):

• Popeye v0.22.0
• K8s v1.30.8

Additional context
I've run locally adding the region and it works but it does not concatenate the file name to the upload, so it results (in my case) to a file called "27" being uploaded to s3.

I've tested running:

AWS_PROFILE=prod go run main.go --lint=warn --file=../../popeye/popeye.yaml --out=html --cluster-name=my-cluster --s3-bucket=my-bucket/popeye/my-cluster/2025/01/27/ --logs=none --log-level=4 --s3-region=eu-central-1

[derailed]

@jchanam Thanks for the report! You are correct the region need to be set with the new update aws sdk.
I will fix the bucket path bug in the next drop.

[derailed]

Fixed v0.22.1