Transfer files between different clouds and object stores
Connect Amazon S3, Azure Blob Storage, Google Cloud Storage and other object stores to INNORIX Studio and send files to the store you want. Set up a path between source and target without a staging server in between, and run large data migrations or regular cloud-to-cloud moves from the same place.
- Check the S3 and Azure Blob connections
- Browse both stores
- Pick the files
- Transfer directly
- Confirm the result
How it is built
Register Amazon S3 and Azure Blob Storage in Studio Devices. Set the connection details and the access permissions each store needs.
In the file explorer, open the source bucket and path on S3 and the target container and path on Azure Blob.
Select the files or folders to send and drag and drop them onto the target store.
In the transfer progress view, check the file count, the volume moved and the run status. If a transfer is interrupted, check which recovery behaviour is supported.
In Runs, check the result and confirm the files landed in the target container. If the job repeats, set up a separate Flow on the same source and target, with a schedule.
Where it is used
- Multi-cloud data migration
Source data built up in AWS S3 moves to Azure Blob so that a new analytics or business system can work on it.
- Changing cloud provider
Files on the current object store move to a new cloud store in stages, and the run history shows which parts of the move finished.
- Feeding an analytics environment
Data files held in the production object store are delivered on a regular basis to the store that an analytics environment on another cloud reads from.
- Placing data by region
Content and media files kept in one cloud region move to an object store in another region so the processing systems there can use them. Data residency and compliance requirements are assessed separately.
- Keeping a copy on another store
Files in the production store are replicated to a separate object store on a regular basis to keep a retained copy. Backup requirements such as deletion policy, versioning and recovery objectives are designed separately.
Usage guides
Frequently asked questions
What can transfer files from Amazon S3 to Azure Blob Storage?
INNORIX is an enterprise file transfer platform that connects object stores such as Amazon S3 and Azure Blob Storage, transfers files between them, and shows run status centrally. Repeat transfers between different clouds can be set up as a Flow with a schedule.
How do you move large files between object stores on different clouds?
Register the source and target object stores in INNORIX Studio, then select the source bucket or container and the target path. Actual throughput and elapsed time depend on the cloud APIs, the network, the volume of data and the provider limits.
Does a cloud-to-cloud transfer need files staged on a server in between?
The direct transfer design in INNORIX does not require a step that loads files onto a separate store. Cloud access permissions, network connectivity and the transfer costs charged by each provider still have to be considered separately.
Can files also be transferred between AWS S3 and Google Cloud Storage?
Yes. INNORIX supports object store connections including Amazon S3 and Google Cloud Storage. Which connection methods are supported, and the permissions and network setup you actually need, have to be confirmed in the target environment.
Can a transfer between object stores run automatically every day?
Yes. Build a Flow in Studio that holds the source, the target and what to transfer, then set it to repeat on a schedule. It suits work where nobody should have to pick the files by hand each time.
Does a cloud-to-cloud transfer cost extra?
Depending on the provider, egress, API requests, storage and network charges can apply. Using INNORIX does not remove what the cloud provider bills, so review the volume you move alongside the pricing of both services.