Why would I change the storage location for uploaded files?
Having media files stored geographically close to your users will mean faster transfer times (uploads and downloads).
For downloads, this means much less issues when playing back media. It also means faster page loads for pages that contain thumbnails.
How can I change where files are uploaded?
Select a new location from the dropdown menu in the 'Storage location for uploaded files' under Site Preferences > Advanced.
What will this change do?
This change will indicate where new files will be uploaded. Existing files will remain in their current storage location.
Which uploaded files are impacted?
All new files (media and others) that are uploaded to Flow Production Tracking will be uploaded to the selected storage location.
Media created by Flow Production Tracking's transcoder (e.g., media files associated with Version entities) will also be uploaded to the selected storage location.
Will my existing files be moved?
No, existing files stay where they are.
Will any of my files be offline during or after the transfer?
No, your storage location can be updated while users are using the site. This change will not cause any files to go offline, not even temporarily.
The only thing to double check is whether or not there are firewall restrictions that need to be modified when making the change. See the Technical Details section below.
Which storage location should I pick?
Typically, selecting a location that is geographically closer to the site users’ location is the best thing to do. In some cases it might be difficult to know.
A web search for “speedtest for AWS” should point you to tools that can help you make the decision.
Can I store files in multiple locations?
You can only choose one current storage location at any time for a given Flow Production Tracking site. However, because existing files will not move locations, Flow Production Tracking will continue to provide access to files that were uploaded before you selected a closer storage location.
Flow Production Tracking uses a different S3 bucket for each region:
| S3 region | URL of Flow Production Tracking S3 bucket | |
|---|---|---|
| Dublin, Ireland | eu-west-1 | S3 region URL: sg-media-ireland.s3-eu-west-1.amazonaws.com Accelerated S3 URL: sg-media-ireland.s3-accelerate.amazonaws.com Regular S3 URL: sg-media-ireland.s3.amazonaws.com |
| Oregon, U.S. | us-west-2 | S3 region URL: sg-media-usor-01.s3-us-west-2.amazonaws.com Accelerated S3 URL: sg-media-usor-01.s3-accelerate.amazonaws.com Regular S3 URL: sg-media-usor-01.s3.amazonaws.com |
| Tokyo, Japan | ap-northeast-1 | S3 region URL: sg-media-tokyo.s3-ap-northeast-1.amazonaws.com Accelerated S3 URL: sg-media-tokyo.s3-accelerate.amazonaws.com Regular S3 URL: sg-media-tokyo.s3.amazonaws.com |
| Sao Paulo, Brazil | sa-east-1 | S3 region URL: sg-media-saopaulo.sa-east-1.amazonaws.com Accelerated S3 URL: sg-media-saopaulo.sa-east-1-accelerate.amazonaws.com Regular S3 URL: sg-media-saopaulo.s3.amazonaws.com |
| Mumbai, India | ap-south-1 | S3 region URL: sg-media-mumbai.ap-south-1.amazonaws.com Accelerated S3 URL: sg-media-mumbai.ap-south-1-accelerate.amazonaws.com Regular S3 URL: sg-media-mumbai.s3.amazonaws.com |
| Sydney, Australia | ap-southeast-2 | S3 region URL: sg-media-sydney.ap-southeast-2.amazonaws.com Accelerated S3 URL: sg-media-sydney.ap-southeast-2-accelerate.amazonaws.com Regular S3 URL: sg-media-sydney.s3.amazonaws.com |