Justification:
More and more modules uses S3 integration for their needs.

With current folio-s3-client implementation it requires to create separate S3 bucket for each module. It’s ok when we talk about production set up and want to isolate buckets, but for dev environments it’s causes the issue with buckets managment and AWS limits.

So we propose to add possibility to specify subPath in backet that will allow to point all modules that uses S3 integration to single bucket with different folders.

For example:
Current:

s3:

• mod-data-export-worker (bucket)

• mod-entities-links (bucket)

• mod-lists (bucket)

• mod-oai-pmh (bucket)

Proposal:

s3:

• folio-s3 (bucket)

  • mod-data-export-worker (folder)

  • mod-entities-links (folder)

  • mod-lists (folder)

  • mod-oai-pmh (folder)