You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some buckets it is desirable to not sign request (e.g. noaa-nexrad-level2). On the command line this can be done using --no-sign-request. aws.s3 does a good attempt to retrieve credentials, meaning if I have credentials in the .aws directory it tries to sign the request, resulting in a failure to retrieve data. Is there a way in the package to explicitly not sign requests?
On the command line for me this fails: aws s3 ls --recursive s3://noaa-nexrad-level2/2010/01/01/TJUA/
While this works: aws s3 ls --no-sign-request --recursive s3://noaa-nexrad-level2/2010/01/01/TJUA/
The text was updated successfully, but these errors were encountered:
Thinking a bit more about this might be resolved by adding an argument anonymous = TRUE/FALSE/no_sign_request=TRUE/FALSE to aws.signature::locate_credentials (s3HTTP passes arguments to that function). This also seems to relate to this issue: cloudyr/aws.signature#61
For some buckets it is desirable to not sign request (e.g.
noaa-nexrad-level2
). On the command line this can be done using--no-sign-request
.aws.s3
does a good attempt to retrieve credentials, meaning if I have credentials in the.aws
directory it tries to sign the request, resulting in a failure to retrieve data. Is there a way in the package to explicitly not sign requests?On the command line for me this fails:
aws s3 ls --recursive s3://noaa-nexrad-level2/2010/01/01/TJUA/
While this works:
aws s3 ls --no-sign-request --recursive s3://noaa-nexrad-level2/2010/01/01/TJUA/
The text was updated successfully, but these errors were encountered: