Closed mikeshultz closed 3 weeks ago
Found a comment from an AWS engineer that explains this isssue a bit in more detail. I suspect this is due to the recent code added for boto3 auth bypath, rather than a boto3 issue.
Presumably the credentials need to be refreshed occasionally from the metadata provider.
Seen on a running worker earlier today. The worker crashed as this was unhandled.