Config file changes
This version changes the way S3 clients are created, just a bit. It is only a breaking change if you were previously relying on an empty set of AWS credentials to prompt credentials = false
in the S3 client. For everyone else this major version is backwards compatible.
For S3 client creation now:
-
If you have credentials specified in your .env file they are used, as always.
-
If you have no credentials specified, no credentials are handed to the S3Client. This means the AWS SDK will attempt to find credentials using the default chain.
-
If you set
AWS_ANONYMOUS=true
in your .env file, this library will setcredentials = false
when creating the client, which explicitly creates an anonymous client.