S3 bucket migration for Central storage

Support
1

1. What is the issue? Please be detailed.
My S3 storage provider has had some issues [more detail to follow once they have been resolved!] and the recommendation is to create a new S3 bucket and 'migrate my data'. So far I have a duplicate of the bucket, with the same provider but with (obviously) a different URL to the bucket

I am wondering what steps I need to take to 'redirect' Central to use a different bucket.

If I change the .env file and update the entry for S3_BUCKET_NAME then stop and restart Central via the docker commands, is that enough to point to the new bucket - there are no changes to S3_SERVER URL or the keys.

Or, is there a table(s) within the database that has each URL constructed that needs to be updated? If so, is there an SQL statement that I can use (gulp!)

2. What steps can we take to reproduce this issue?

Get someone to degrade your S3 storage pool; create a duplicate S3 Bucket from the original and then look to migrate

3. What have you tried to fix the issue?
The existing Bucket has got a hole in it... So I need to redirect. I may need to use a different S3 provider!

2

Yes, if you clone your bucket and put the new bucket's name/keys into the .env file, Central will look for the old files in the new bucket. There is nothing else you need to do for it to work.

3

Thanks.
Just confirming that this works as expected. Phew.