-
Notifications
You must be signed in to change notification settings - Fork 3
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
InvalidSignatureException #3
Comments
Hmmm...this seems related to auth, not CWL directly. But I'll try to figure it out. It kind of seems like maybe AWSCore signed the message but then continued retrying it after the signature expired. But I'm not sure. |
I'll note I got this exception during running an AWS Batch for around 30 minutes. |
I will have it refresh credentials |
Turns out that's hard: JuliaCloud/AWSCore.jl#44 |
Searches say that this is likely clock skew, and indeed the instance running this did not have Amazon Time Sync enabled. |
Looks like credential refresh is automatic (it's assumed that the refresh will use the default credentials). Expired signatures (this error) are also retried by AWSCore. |
This is probably fixed by fixing clock skew on the machine or by handling clock skew in AWSCore.jl (issue here: JuliaCloud/AWSCore.jl#45) |
Not sure if anything needs to be done about this:
The text was updated successfully, but these errors were encountered: