Set_s3_config() only supports the default region

It appears that set_s3_config() expects the S3 bucket doesn’t exist and will create it. It also doesn’t allow specifying the AWS region to create the new bucket. Ideally one or both of the following would be supported:

  1. Support using an S3 bucket if it already exists.
  2. Take the AWS region as a parameter so the bucket can be created in a non-default region.


Currently only the default us-east-1 region is supported. But we could probably add support for other regions in the next release.

Version 2.3.0 introduces an option to specify the region: