CDN bucket name setting introduced

Added the ability for stores to configure their own S3 bucket (with access and secret keys) for media uploads, instead of being forced to use the shared global default bucket.

This includes:

• Configurable per-store S3 bucket for media uploads

• Custom access and secret keys support

• No longer forced to use the shared global default bucket

How it benefits the Merchant

This gives merchants more control over where their media assets are stored, which can help with data governance, performance, or cost management specific to their own infrastructure.

Potential FAQs

Q: Do I have to set up my own S3 bucket, or is the default still available?

A: It's optional — you can configure your own bucket, but the shared global default remains available if you don't.

Q: Is my media automatically migrated to my new bucket if I set one up?

A: Check with your account manager for details on migrating existing media to a newly configured bucket.