The following Ciphers are supported in TLS v1.2 

  • ECDHE-ECDSA-AES128-GCM-SHA256
  • ECDHE-RSA-AES128-GCM-SHA256
  • ECDHE-ECDSA-AES128-SHA256
  • ECDHE-RSA-AES128-SHA256
  • ECDHE-ECDSA-AES256-GCM-SHA384
  • ECDHE-RSA-AES256-GCM-SHA384
  • ECDHE-ECDSA-AES256-SHA384
  • ECDHE-RSA-AES256-SHA384
  • AES128-GCM-SHA256
  • AES128-SHA256
  • AES256-GCM-SHA384
  • AES256-SHA256

Some of the most common reasons are 

  • Insufficient space at the location where the file is being downloaded to.
  • Some SFTP client libraries are unable to handle packets out of order and the file download stops after a certain size. As a workaround, you can set the QueueDepth/queue_size to 1 which will force the packets to arrive in order. This may slowdown the overall file download operation when downloading very large files.

It is recommended to connect to the hostname referenced in Section 3: Environment and Connectivity

Yes, files uploaded through any of the supported access methods, SFTP, HTTPS, S3 Direct, and FINRA Gateway Upload application gets archived for 30 days.

Yes, a user with right entitlement can download file available in the archive sub-space

Yes. You can find the latest AWS documentation here - https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html

You have to call the S3TransferToken API from fileX again to get the new access token.

Tracking API from fileX is only supported for upload requests made through HTTP REST APIs.

It is a standard HTTP Response Code you get when the tracking ID provided in the API request is either invalid or older than 90 days

Yes. fileX service experience will be consistent across all the supported methods. Same files will be available in all the supported methods.

Subscribe to