Skip to content

Researchers: Start Here

This section is for researchers who want to try the federated analytics blueprint of ELIXIR On-Cloud: run analyses on compute that stays at the ELIXIR Nodes, and keep sensitive data under the control of its owner.

What these docs cover

These docs cover the ELIXIR On-Cloud sandbox/demo deployment, how to integrate with it, and tutorials, for architects and operators, partners and developers, and researchers. Generic instructions for installing and using the individual products are in each product's own docs, linked from here.

What you can try

Page What you do What you need
Use Krini Run TES tasks and WES workflows in your browser, on services from the Cloud Registry, and follow your runs. Describes the new version of the portal, which is being rewritten. A web browser and an LS Login account.
Use the Command Line Find services in the Cloud Registry, send tasks to a TES service such as proTES, run workflows on a WES service, find workflows in WorkflowHub and look up DRS objects from your terminal with ga4gh-cli. Git and Rust on your computer, and an LS Login access token for services that need a login.
Tutorial: Your First Run in Krini Log in to Krini, run a task and a workflow on demo data, and read the results, step by step. A web browser, an LS Login account, and access to a TES and a WES service.
Tutorial: Your First Run from the Command Line Install ga4gh-cli, find services, log in with a token, run a task and a workflow on demo data, and read the results, step by step. Git and Rust on your computer, an LS Login account, and access to a TES and a WES service.
Run Workflows Across Nodes Run a Snakemake workflow on the TES services of several Nodes, through the proTES gateway. A Python environment on your computer, and access to proTES or other TES services.
Crypt4GH with proTES Process Crypt4GH-encrypted files in a secure container. Needs an unreleased proTES branch until the Crypt4GH plugin for current proTES is released. Docker and three virtual machines.
Run Interactive Services on TES Run RStudio, JupyterLab or Atlas with OMOP demo data as TES tasks, and open them in your browser. Synthetic data only. A virtual machine with a public host name and an open HTTPS port, and a TES service.

Before you start

  1. Get an LS Login account. It is the identity provider of the deployment.
  2. Become a member of the LS Login group ECP_CLN:EOC-Compute, which gives access to the compute services of the deployment. An application form is coming (generic-issues#49); until then, write to cloud-service@elixir-europe.org.
  3. Choose a page above and follow its steps.

Which TES services you can use

Send your tasks to the TES gateway of the deployment, proTES, at its TES API https://protes.rahtiapp.fi/ga4gh/tes/v1, with an LS Login access token. proTES forwards each task to one of the TES services of the Nodes. Get the token from Krini: proTES accepts tokens that LS Login issued to Krini.

You can also send tasks directly to the TES services of the Nodes that require LS Login tokens. Find them, and their addresses, in the Cloud Registry (see Using the APIs).

Send your token only to services that you trust

Anyone who runs a service that receives your token can act as you until the token expires. Before you send it to a TES service, check that the service is verified in the Cloud Registry (see Verified services) and that you trust its operator.

Where to go next