Aspera

Yes that is correct. The REST API that the customer is using was created for POSTing and GETing small files that provide a symbolic link functionality on object stores.

The proper way to transfer large files with IBM Aspera is through the client applications (ascli, IBM Aspera app, HSTS/HSTE, Transfer SDK, HTTP Gateway, etc..).

If the customer wants to transfer with a REST API , then they will need to install and configure the HTTPGateway component and use the WebSocket based protocol offered by this component. The HTTP Gateway acts as and ascp client, transferring the data from a Transfer Server and then streaming it through the HTTPGateway where it can be consumed by Web Applications or REST type clients.

A little more details on @BEN FORSYTH answer:

Node API answers are limited in size by the value of the parameter: max_request_file_create_size_kb in aspera.conf.

One can get the active value of that parameter with command:

$ asuserdata -a | grep max_request_file_create_size_kb
  max_request_file_create_size_kb: "20000"

Or alternatively:

$ asconfigurator -x "get_server_data"|grep max_request_file_create_size_kb
"server","max_request_file_create_size_kb","20000","4096"

The first value here is the actual value, and the second value is the default value.

If the value is >= 16 MebiBytes (i.e. 2**24), then the value is maxed out to that value.
So, it is possible to increase that value to 16MB with commands:

asconfigurator -x "set_server_data;max_request_file_create_size_kb,20000"

systemctl restart asperanoded

This value also impacts the max size of previews used in AoC.