Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3-compatible storage: support S3ForcePathStyle and expanded configs #431

Closed
tonychoe opened this issue Dec 25, 2020 · 3 comments · Fixed by #498
Closed

S3-compatible storage: support S3ForcePathStyle and expanded configs #431

tonychoe opened this issue Dec 25, 2020 · 3 comments · Fixed by #498

Comments

@tonychoe
Copy link

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

S3-compatible storages require s3ForcePathStyle. Additionally Oracle Object Storage requires a region identifier to use other than a home region.

Currently, Tempo doesn't allow these configurations, therefore we cannot use some S3-compatible storages as Tempo's storage.

Describe the solution you'd like

Allow passing s3forcepathstyle and region to the S3 SDK used in Tempo, as the following example config:

    s3:
      s3forcepathstyle: true
      bucket: tempo 
      region: us-phoenix-1
      endpoint: endpoint1234.compat.objectstorage.us-phoenix-1.oraclecloud.com      access_key: tempo
      secret_key: supersecret
      insecure: false

As you may know, Loki has been supporting the S3-compatible storage, a region identifier and more. Perhaps Loki's code could be re-used to implement this feature.

Describe alternatives you've considered
N/A

Additional context
N/A

@annanay25
Copy link
Contributor

Thanks for reporting @tonychoe, agree that we need this. Would you be interested in PR'ing the enhancement?

@mdisibio
Copy link
Contributor

mdisibio commented Feb 2, 2021

Some findings:
Region is straightforward to readd. MinIO automatically detects the region from the endpoint so we thought it was no longer needed.

s3forcepathstyle:

In summary, I believe we can support these 2 features (region and path style) using the MinIO client. The cortex client has additional functionality which may be useful, if we want to go that route.

@joe-elliott
Copy link
Member

Yes, please add these options. I'd say anything that doesn't unnecessarily complicate the code or config is welcome.

There's a reason all the Cortex options are there and we'll probably need them sooner or later anyway :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants