This blog is all about understanding the transfer paths in IBM Aspera on Cloud (AoC) and how AoC intelligently picks the best path for your file transfers. Knowing how these choices are made can help you optimize speed, reliability, and overall workflow efficiency.

When you initiate a transfer in AoC, the platform evaluates your setup and dynamically selects one of three primary transfer paths:

• Tethered Node Transfer Path
• Cloud Storage Transfer Path
• Direct FASP Transfer Path

Its decision is based on factors such as storage location, available bandwidth, node connectivity, and transfer policies. Let’s dive into each path and understand when and why AoC chooses it.

1. Tethered Node Transfer Path

✅ Best for: Organizations using on-premises or private cloud infrastructure.

When it’s used:

• The source or destination is a tethered node (an on-premises or cloud-hosted Aspera High-Speed Transfer Server).
• Files are stored on local disks, NAS, SAN, or private cloud.
• Your organization wants full control over transfer activity.

How it works:

1. AoC sends a control request (HTTPS 443) to the tethered node via the Aspera Node API.
2. The node authenticates and verifies storage access.
3. FASP (UDP 33001) initiates the high-speed transfer.
4. If the node is behind a firewall, it opens an outbound connection to AoC.

Example:

A company links its on-prem Transfer Server to AoC. A 500GB file uploaded from a laptop to an NAS triggers AoC to select the tethered node for a secure, high-speed FASP transfer.

2. Cloud Storage Transfer Path

✅ Best for: Direct cloud-to-cloud transfers without local infrastructure.

When it’s used:

• Files are stored in AWS S3, Azure Blob, IBM COS, or Google Cloud Storage.
• There are no tethered nodes or on-premises servers involved.

How it works:

1. AoC authenticates with the cloud storage provider.
2. It requests pre-signed URLs or access credentials.
3. The transfer occurs directly between cloud storage locations using FASP (if supported) or HTTPS as a fallback.

Example:

A media company needs to move a 4TB video file from AWS S3 to Azure Blob Storage. AoC bypasses tethered nodes and handles the transfer directly in the cloud.

3. Direct FASP Transfer Path

✅ Best for: Peer-to-peer transfers without using cloud storage.

When it’s used:

• Files are exchanged directly between endpoints (e.g., desktop-to-desktop or desktop-to-server).
• Cloud storage isn’t required, but high speed and security are essential.

How it works:

1. Both sender and receiver authenticate with AoC.
2. AoC negotiates the optimal FASP route.
3. FASP (UDP 33001) establishes a direct, high-speed connection.

Example:

A film studio transfers a 2TB raw video file from an editor’s MacBook to a remote production server. AoC sets up a direct FASP connection, avoiding any cloud storage step.

📊 Transfer Paths at a Glance

Summary       

By understanding how AoC chooses transfer paths, you can better align your workflows with its capabilities, ensuring fast, reliable, and secure file transfers.

Stay tuned for more insights in the “Making Life Easier with IBM Aspera on Cloud” series to help you get the most out of your AoC experience!