@grzm I'm looking at switching from the Cognitect AWS API to awyeah so we can get around the Jetty 9 issue. Your docs say: > The awyeah-api client does not auto-refresh AWS credentials. The aws-api behavior relies on features that aren't present in babashka, and I haven't figured out an alternative implementation of the behavior. My use case is short-lived scripts, where JVM start-up time can dwarf script execution time: credentials don't have much time to get stale. Does that mean if I create a basic-credentials-provider and a client based on it at startup in a long-lived process and use it for uploading stuff to S3, after some period of time, it will fail because the credentials have gone stale?