Ever-larger scientific datasets may be a goldmine for discovery, but analysing them has become a bottleneck in life-science research.

Embassy Cloud users have direct access to the EMBL-EBI data, services and compute. This is a practical and cost-effective alternative to replicating services and downloading vast, public datasets locally. Tenants can access their workspace from anywhere in the world, reducing the need for capital investments in hardware and related operational costs. Resilient and flexible.

Welcome to Embassy Cloud

• 1. About Embassy Cloud
  • 1.1. What is the Embassy Cloud?
  • 1.2. Why should I use EMBL-EBI’s Embassy Cloud?
  • 1.3. What support can EMBL-EBI provide to help me get started?
  • 1.4. Who will manage my virtual machine?
  • 1.5. Service Announcements
  • 1.6. Best Practices
  • 1.7. Technologies used in Embassy Cloud
• 2. Embassy Cloud Version 4
  • 2.1. About Version 4
  • 2.2. Service Status
  • 2.3. Requesting Embassy Resources (including Embassy Hosted Kubernetes)
  • 2.4. Retiring Embassy Projects
  • 2.5. Useful Links
  • 2.6. How to Login
  • 2.7. Quick Start
  • 2.8. Selecting An Appropriate Deployment Zone
  • 2.9. Using the OpenStack CLI
    • 2.9.1. Retrieving Credentials
    • 2.9.2. Installing the Client
    • 2.9.3. Terraform
  • 2.10. Images
  • 2.11. Storage
    • 2.11.1. Root Disks
    • 2.11.2. S3 Object Store
    • 2.11.3. Volume Issues
  • 2.12. EBI Data Access
    • 2.12.1. EBI internal databases
    • 2.12.2. EGA dataset
    • 2.12.3. FiRe Archive
  • 2.13. Security Best Practices
    • 2.13.1. The Shared Model
    • 2.13.2. Infrastructure Security
    • 2.13.3. Security Groups
    • 2.13.4. Protect your VMs
• 3. Embassy Hosted Kubernetes v3.0 - Magnum
  • 3.1. What is Magnum?
  • 3.2. How Does EHK v3.0 differ from EHK 2.0?
  • 3.3. Security
  • 3.4. Quick Start
  • 3.5. How to Size Your Cluster
  • 3.6. Creating an EHK v3.0 Cluster
    • 3.6.1. Cluster Templates
    • 3.6.2. Horizon GUI Cluster Creation
    • 3.6.3. Command Line Cluster Creation
    • 3.6.4. Terraform Cluster Creation
    • 3.6.5. Fetch Kubernetes Credentials
  • 3.7. Securing your Cluster
    • 3.7.1. Securing Load Balancers that are created by services in Kubernetes
    • 3.7.2. Securing API Server on port 6443
  • 3.8. Storage
    • 3.8.1. ReadWriteOnce
    • 3.8.2. ReadWriteMany
  • 3.9. External Cluster Access Methods
    • 3.9.1. LoadBalancer Type
    • 3.9.2. Ingress
    • 3.9.3. NodePort
    • 3.9.4. SSH access to Kubernetes Nodes
  • 3.10. Monitoring
    • 3.10.1. Monitoring your own application
  • 3.11. Exposing type: NodePort
    • 3.11.1. Nodeport Workflow
  • 3.12. Resizing Your Cluster
  • 3.13. Bulk Copying Data to a Persistent Volume
    • 3.13.1. Workflow
  • 3.14. cert-manager
  • 3.15. Organizing cluster access using Kubeconfig files
    • 3.15.1. Create user credentials and a new kubeconfig file
    • 3.15.2. Use case 1: Create an user with cluster-admin privileges
    • 3.15.3. Use case 2: User with admin priviledges at the namespace level
    • 3.15.4. Use case 3: Create an user with a limited privileges within the namespace
  • 3.16. Troubleshooting Magnum Cluster Access
  • 3.17. Changing Cluster Template Versions
    • 3.17.1. Automation and the Ephemeral Nature of Kubernetes Clusters
    • 3.17.2. Cluster Migration
    • 3.17.3. Reusing Floating IP Addresses
    • 3.17.4. Reusing Persistent Volumes
    • 3.17.5. Reusing Networks

Indices and tables

• Index
• Module Index
• Search Page

Embassy Cloud is part of the ELIXIR infrastructure