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

No documentation on configuring S3 #355

Open
lawik opened this issue Dec 8, 2023 · 2 comments
Open

No documentation on configuring S3 #355

lawik opened this issue Dec 8, 2023 · 2 comments

Comments

@lawik
Copy link

lawik commented Dec 8, 2023

Project seems awesome :)

I assume from digging into old issues and PRs that it will pull my S3 config from the usual suspected places, haven't had a chance to verify yet. But it would be sweet if the docs included more on how to provide that config. The example has a minio profile. Will it pull from minio configs, AWS configs? Does it respect some environment variables? Are there other ways to pass in the config?

@jgraettinger
Copy link
Contributor

It uses Application Default Credentials, so it's using standard AWS environment variable and config file locations: https://aws.amazon.com/blogs/security/a-new-and-standardized-way-to-manage-credentials-in-the-aws-sdks/

There are some overrides that can be passed as URL arguments of the fragment store, which affect the profile it plucks out of your AWS config. You can see an example of this here, where it's used to direct S3 requests to a local Minio instance.

If you don't specify any URL arguments on your fragment URL -- just the bucket and prefix -- it's just going to use your default profile.

Happy to take a PR for doc updates!

@lawik
Copy link
Author

lawik commented Dec 8, 2023

Great. I will give that a look and see if I can contrib some :)

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

No branches or pull requests

2 participants