Support user-supplied boto3 session for AWS S3 operations

There are 2 places where an AWS S3 `boto3` client is created. In both cases, the default boto3 session is used (implicitly), which means that it is not possible to supply a custom session instance. Being able to supply a custom session instance would allow a user to easily supply a session instance suitably configured for any special use case required.