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

Using configure_s3_access and configure_rio still requires setting the AWS_NO_SIGN_REQUEST environment variable #159

Open
alexgleith opened this issue Jun 24, 2024 · 2 comments

Comments

@alexgleith
Copy link
Contributor

alexgleith commented Jun 24, 2024

I expect either of odc.stac.configure_s3_access(aws_unsigned=True) or configure_rio(cloud_defaults=True, aws=dict(aws_unsigned=True)) to set up the environment so that I don't need AWS credentials for public read S3 objects.

In testing, neither of those functions works, and loading data from S3 URIs throws the error:

RasterioIOError: AWS_SECRET_ACCESS_KEY and AWS_NO_SIGN_REQUEST configuration options not defined, and /Users/username/.aws/credentials not filled

If I do:

import os
os.environ["AWS_NO_SIGN_REQUEST"] = "YES"

then the error goes away, and data can be loaded.

Versions:

  • rasterio==1.3.10
  • odc-stac==0.3.9

I tried with and without Dask and both failed the same way.

@Kirill888
Copy link
Member

@alexgleith needs more info, in particular version of rasterio, version of odc-stac, whether this is a problem for dask, non-dask or both. There has been a handful of times in the past in rasterio that AWSSession had issues around that.

@Kirill888
Copy link
Member

this one worth checking out for example:

rasterio/rasterio#2866

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