The Aspera Direct-to-Cloud transport is a one-of-a-kind fundamental high-speed transfer solution for moving large files and data sets to, from, and between cloud storage, currently certified and supported on the following cloud and CDN platforms:

How it works

Typical file transfer acceleration "gateways" upload data to cloud object storage in 2 phases. First to data is uploaded over the wide area network and written to the local vm attached storage. In a second phase, the data gets copied from the local storage to the target object storage. The result is a significant delay from when the transfer is started to when the data is readily available for use, and increases in local storage costs and machine compute time and costs.

Aspera on Demand with Direct-to-Cloud is built on the FASP transport technology, which has been deeply integrated with the underlying object storage APIs. Transferred data is written directly to object storage and available immediately when the transfer completes.

   
 2 Step Upload  Aspera Direct-to-Cloud

As a result, Aspera On Demand with Direct-to-Cloud transport platform is enabled to provide high-performance secure WAN transport of files, directories, and other large data sets to, from and between cloud storage preserving all of the core FASP performance benefits:

  • Performance at any distance – Maximum speed single stream transfer, independent of round-trip delay and packet loss (500ms / 30% packet loss+), up to the I/O limits of the platform.
  • Large file sizes – Support for files and directory sizes in a single transfer session up to the largest object size supported by the particular platform at a default 64 MB multipart chunk size.
  • Large directories of small files – Support for directories containing any number of individual files with high-speed, even for very large numbers of very small files.
  • Adaptive bandwidth control – Network and disk based congestion control providing automatic adaptation of transmission speed to available network bandwidth and available I/O throughput to/from storage platform, to avoid congestion and overdrive.
  • Automatic resume – Automatic retry and checkpoint resume of any transfer (single files and directories) from point of interruption
  • Built-in encryption and encryption at rest – Built in over-the-wire encryption and encryption-at-rest (AES 128)
  • Secure authentication and access control – Built in support for authenticated Aspera docroots implemented using private cloud credentials. Support for configurable read, write, and listing access per user account. Support for platform-specific role based access control including Amazon IAMS and Microsoft Secure SaaS URLs.
  • Seamless, full featured HTTP fallback – Seamless fallback to HTTP(s) in restricted network environments with full support for encryption, encryption-at-rest and automatic retry and resume.
  • Concurrent transfer support – Concurrent transfer support scaling up to ~50 concurrent transfers per VM instance on the environment. (Cloud storage platforms vary in their ability to support concurrent sessions depending on the capacity of the particular VM host-to-cloud file system architecture).
  • Preservation of file attributes – Transfers can be configured to preserve file creation and  modification times.
  • Complete interoperability with Aspera Clients – Fully interoperable transfer support with all core Aspera products acting as transfer peers with the cloud storage, including Enterprise Server, Connect Server, Connect browser plug-in, Desktop client, Point-to-point, Cargo, Mobile, Outlook Plug-in and Drive.
  • Full-featured transfer modes – Fully interoperable transfer support for all modes of transfer in these products including command line (CLI), interactive GUI point-and-click, browser, hot folder automation, and SDK automation.
  • Comprehensive server capabilities – Full support for all Aspera server-side features including secure docroots, Console configuration of BW, security and file handling policies and reporting to Console.
  • Support for forward and reverse proxy – Transfers to/from cloud environments support Aspera proxy on the client side in forward or reverse mode.
  • Comprehensive SDK capabilities – The server side software supports all of the core Aspera transfer and management SDKs including the Connect JavaScript API, faspmanager, SOAP and REST web services for job initiation, reliable query, aggregate reporting through stats collector, and automatic post-processing scripts.

What's New with Direct-to-Cloud 3.7

With Aspera Core version 3.7, asperatrapd officially supports IBM - SoftLayer Swift and Cleversafe; AWS - S3, GovCloud, Reduced Redundancy, Infrequent Access; Microsoft Azure - File Storage, Blob and Cool Storage; Akamai NetStorage; Limelight Orchestrate Cloud Storage; Google Cloud Storage; HDFS; Ceph, and over 14 object storage vendors have validated basic compatibility with Aspera Direct-to-Cloud transfer including NetApp Cloud Storage, HGST Active Archive, Scality RING and EMC ECS.

The latest asperatrapd 3.7 release includes the following major new technology features:

  • New configurable options to better support high speed small file transfers and streaming transfers via ascp4
  • Support for all major second-tier storage options - AWS Infrequent Access, Reduced Redundancy, and Azure Cool Storage
  • Kerberos support for Direct-to-Hadoop transfers - Kerberos authentication is now supported in Trapd for transfers to the Hadoop HDFS storage
  • MS Azure - Support for large BLOCK Blobs - Microsoft Azure has enhanced Blobs of type 'BLOCK' to be up to 5TB in size. This capability is now supported in asperatrapd
  • Support for Bluemix object storage - asperatrapd has now support for the Bluemix 'swift' object storage through Node generated access keys. These access keys use connection and credentials information (Keystone v3) for the storage that the user can retrieve from the Bluemix portal
  • Support for Bluemix s3 storage - asperatrapd has now full support for Bluemix s3 storage through Node generated access keys
  • Enhanced support for S3 Versioning - S3 versioning is now supported. When configured in Trapd overwritten objects won't generate a delete marker anymore. Additional options in /opt/aspera/etc/trapd/s3.properties let the user choose between auto-detection of versioned buckets or force the behavior