Open gwaybio opened 1 year ago
Thank you for opening this @gwaybio ! Sorry to hear this is happening. I'm working on trying to reproduce this error and wanted to follow up with a message in the meantime. Based on the log and error messages, my understanding so far is that there may be something occurring with how Boto3 (which cloudpathlib
uses to access remote files on AWS S3) is interpreting the client configuration. An initial glance here makes me wonder if all the configurations are truly gone or if there are partial remnants that could be overriding the no_sign_request
parameter and causing a challenge.
Boto3 credentials documentation mention a cascade of configuration locations including various files and environment variables. Could I verify with you that these are removed or non-existent on the device you attempted this on?
Specifically, I believe we need to check the following:
AWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY
, or AWS_SESSION_TOKEN
)
export | grep "AWS_ACCESS_KEY_ID\|AWS_SECRET_ACCESS_KEY\|AWS_SESSION_TOKEN"
~/.aws/credentials
)~/.aws/config
)/etc/boto.cfg and ~/.boto
)Could I verify with you that these are removed or non-existent on the device you attempted this on?
Sorry for not following up on this. I see how knowing these credentials and config checks as you list can help with documentation in #62 - I unfortunately cannot verify if these checks.
Are you able to reproduce the error? If not, then those four checks is a good place to start for future troubleshooting.
I'm receiving an
InvalidAccessKeyID
error after deleting my AWS configure ID frommaple
. I wanted to try theno_sign_request=True
option before adding credentials back to maple, but received an error that I outline below.As specified here, https://github.com/cytomining/CytoTable/issues/52#issuecomment-1553125402, I ran
cytotable.convert(..., no_sign_request=True)
(full command below)But I received the following error:
parsl.log