Private Data services


Private Data Services

EMBL-EBI employs protective mechanisms to prevent excessive downloads from impacting overall service quality. 
If you have significant download demands, please contact us: https://www.ebi.ac.uk/about/contact
Full terms: EMBL-EBI terms of use

Publicly accessible link to this article

Table of Contents

This document focuses solely on private data, which by definition requires authentication and authorisation to be accessed.

Performance and status of Transfer Services

Transfer Announce mailing list

Consider joining our public mailing list for status and change announcements: transfer-announce@ebi.ac.uk.

Standardised data hierarchy and network requirements

The following transfer methods all provide access to the same folder structure, and data uploaded using any of these methods will have the same Unix permissions when the upload finishes.

To access any of these protocols, a Transfer service Account, also known as an ftponly account, is required.

Endpoint Protocol Documentation EBI IPs EBI Network rules External institution network requirements
EMBL-EBI Private Collection (GCS) Globus and HTTP 

Globus How-To

Globus documentation

Client needed (GCP)

193.62.192.146

193.62.192.147

193.62.192.148

  • Ports 50000—​51000 inbound and outbound to/from ANY
  • Port 443 inbound and outbound to/from ANY
 
ftp://ftp-private.ebi.ac.uk FTP - File Transfer Protocol Client recommended (lftp) 193.62.193.162
  • 21 inbound and outbound to/from ANY
  • Passive ports from 40000 to 50000
 
fasp.ebi.ac.uk:~

IBM Aspera 

FASP - Fast Adaptive and Secure Protocol

Aspera Command Line

Aspera Connect

Aspera Firewall considerations

FASP security: Aspera Connect transfer client authorised keys and aspshell

How to transfer files to and from EMBL-EBI using IBM Aspera

193.62.193.164

  • 33001 (TCP) inbound and outbound to/from ANY
  • 33001 (UDP) inbound and outbound to/from ANY
  • Permit TCP outbound to 193.62.193.164 on port 33001
  • Permit UDP outbound to 193.62.193.164 on port 33001
  • Permit UDP inbound from 193.62.193.164 on port 33001

 

How to request assistance or report an issue

Other related documents