TLS certificates

We strongly recommend deploying DVC Studio with a TLS certificate.

Configuring up the TLS certificate and private key

To configure TLS certificates to DVC Studio, following the instructions below according to your installation method:

If you've deployed DVC Studio with the AMI, you'll need to copy your TLS certificate and private key to the EC2 instance and start an SSH session before continuing. Example:

Transfer your TLS certificate and private key to the EC2 instance

$ scp studio.crt studio.pem ubuntu@my-ec2-instance:.

Connect with SSH to your EC2 instance

$ ssh ubuntu@my-ec2-instance

Store your TLS certificate and private key in an object

$ kubectl create secret tls studio-ingress-tls \
      --namespace studio \
      --cert=studio.crt \
      --key=studio.pem

Update DVC Studio's config file

Merge the values.yaml file with the following contents:

global:
  ingress:
    tlsEnabled: true
    tlsSecretName: studio-ingress-tls

Reload DVC Studio

$ helm upgrade --wait studio iterative/studio --namespace studio -f values.yaml

TLS certificates

Configuring up the TLS certificate and private key

Content