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

Get bucket location without configuring AWS credentials #128

Open
jtherrmann opened this issue Dec 7, 2022 · 0 comments
Open

Get bucket location without configuring AWS credentials #128

jtherrmann opened this issue Dec 7, 2022 · 0 comments

Comments

@jtherrmann
Copy link
Contributor

The STAC item creation scripts have to get the S3 bucket location for inclusion in the URL for each STAC item. It's slightly annoying to have to configure AWS credentials (e.g. when running the creation and ingest scripts on an EC2 instance) just for this operation. We should be able to send an unsigned request since the dataset buckets allow public access to the GetBucketLocation operation, but there seems to be a boto3 bug preventing unsigned requests for this operation: boto/boto3#3522

We could wait until the bug is fixed and then implement unsigned requests, or we could just hard-code the bucket location, though this risks that the location will change at some point and invalidate our STAC item URLs.

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

1 participant