S3 Extension 2.0.1.10-SNAPSHOT - Improving S3 region support

[Zackster]

@micstriit has been working away at improving the regions support in the s3 extension in general and with non AWS providers as per this epic S3 regions support

• LDEV-3379 Add a method to the S3 extension to delete objects.
• LDEV-4637 this.s3.defaultLocation doesn’t seem to work
• LDEV-4662 s3 connection pool shutdown
• LDEV-4591 Incorrect Backblaze B2 suffix in S3 PROVIDERS list
• LDEV-4639 directory copy cant rename between s3 buckets in different regions
• LDEV-4511 Regions of Google Cloud Storage are not supported in S3 extension
• LDEV-4595 directoryDelete with a s3 url assumes aws regions

We have been working on the Backblaze support, but please keep in mind, their s3 API is only a subset of the full AWS s3 api and it does behave slightly differently at times, as does minio

Please try it out and let us know if you encounter any problems

[wgold]

Hi,
we are using Lucee with our wholesale application. We’d like to move from on-prem storage (GlusterFS) to AWS S3. We are struggling with the limited region support. We crated our buckets in Frankfurt (eu-central-1) and I created an interface endpoint to access them via our VPN for the upload of static content.
Do you plan to add support for region specific buckets? Moving all data to eu-east-1 doesn’t seem like a viable solution to us, because of GDPR restrictions.

[micstriit]

Lucee does have region support that should cover all needs

lucee/lucee-docs/blob/master/docs/recipes/s3-region.md

let me know if you miss something