Edit on GitHub

TLS certificates

We strongly recommend deploying Studio with a TLS certificate.

Configuring up the TLS certificate and private key

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

If you've deployed 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:

  1. Transfer your TLS certificate and private key to the EC2 instance
$ scp studio.crt studio.pem ubuntu@my-ec2-instance:.
  1. Connect with SSH to your EC2 instance
$ ssh ubuntu@my-ec2-instance
  1. 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
  1. Update Studio's config file

Merge the values.yaml file with the following contents:

global:
  ingress:
    tlsEnabled: true
    tlsSecretName: studio-ingress-tls
  1. Reload Studio
$ helm upgrade --wait studio iterative/studio --namespace studio -f values.yaml
Content

🐛 Found an issue? Let us know! Or fix it:

Edit on GitHub

Have a question? Join our chat, we will help you:

Discord Chat