-
Notifications
You must be signed in to change notification settings - Fork 109
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
Sentinel2 L1C requester pays #52
Comments
Hi @samsammurphy,
but I'm not sure it's the best way to do |
Howdy @vincentsarago I understand the concern that rio tiler uses will be charged by AWS to access L1C now. It has to be really clear to the users (i.e. to avoids nasty surprises). From the front end maybe this could be a one time configuration setting
This could have the effect setting the AWS_REQUEST_PAYER environment variable before running rio tiler, maybe through rasterio as you mentioned, or perhaps as subprocess command? The latter, however, might not work on all machines (?) and would require python2 vs 3 handling, here's what it might look like anyway..
|
FYI |
Cheers! Mojodna suggests a way of setting the environment variable which would handle the reservation I had with my previous subprocess-based suggestion, namely:
edit |
@samsammurphy I'm going to close this, except if it's still a blocker! |
Hi @vincentsarago 👋
It happened, AWS now requires a requester pays header for Sentinel2 L1C 😢 . How do we move forward with
rio tiler
from here?This is the message I get when running the first example in the README
Interestingly when I run the command again I get this
which is more inline with what my (previously working) lambda sentinel2 tiler is now saying..
The text was updated successfully, but these errors were encountered: