Add Support for Dynamic "s3_bucket" in data routing based on resource attributes

[jkmdeltek15]

Component(s)

exporter/awss3

Is your feature request related to a problem? Please describe.

We want to separate data storage at the bucket level in S3, based on resource attributes. Currently, this requires us to configure a new exporter each time a new bucket is introduced, which becomes difficult to manage at scale.

Describe the solution you'd like

Since dynamic "s3_prefix" support already exists, it would be great to extend this functionality to also support "s3_bucket", allowing the bucket name to be derived from resource attributes dynamically.

Describe alternatives you've considered

No response

Additional context

I'm not very familiar with Go, so I'm hoping the owners can take this on. I assume this feature would be relatively straightforward to implement, given that similar logic already exists for s3_prefix.

[github-actions]

Pinging code owners:

• exporter/awss3: @atoulme @pdelewski @Erog38

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

[VihasMakwana]

Looking at the code, it looks like we can implement it the same we implemented dynamic s3_prefix. Hence, removing the needs-triage label

[Erog38]

This makes sense to me, it should be a pretty good first issue as well given there's a precedent if anyone wants to take it on 😄

[bogdan-st]

Hi, I would love to work on this