The name forms of CLC URLs are listed below, along with the types of locations the refer to and an example.
- clc://server or clc://host:port Used to refer to data elements or directories in a CLC Server persistence model. The first entry after the URL is the name of the persistence, followed by the path to the data element within the persistence. For example, with a persistence called
CLC_Server_Project, the CLC URL to a data element called
myAlignmentwithin a folder called
Note that for CLC data in a persistence model, you need the name of the data element, as seen via the Navigation Area of a Workbench, not the name of the file itself, at the filesystem level.
- clc://local Used to refer to files on the local filesystem. To use this form, direct transfer from client systems must be allowed by the CLC Server. The full path to the file should be given after the URL. E.g.
- clc://serverfile Used to refer to files in an Import/Export area for the CLC Server. The full path to the file should be given after the URL. E.g.
- clc://cloudfile Used to refer to files in an AWS S3 bucket. The full S3 address for the file should be given after the CLC URL, e.g. clc://cloudfile/s3://mys3location/subfoldername/mysequence.fastq
NGS data can be imported from Amazon S3 locations, either directly or using on-the-fly import in workflows. Data can also be exported to Amazon S3 locations. Working with data on S3 is of particular relevance when submitting jobs to run on a CLC Genomics Cloud Engine, where execution takes place on AWS, close to the data. When launching analyses to run on a CLC Genomics Server using data from S3, files selected for import are first downloaded to a temporary folder and are subsequently imported.