Cased Documentation
Search…
⌃K

Without an existing cluster

Step-by-step guide on how to deploy Cased Shell on a brand new cluster.

Tested Cloud Providers

  • Microsoft Azure
  • Amazon Web Services (AWS)
Cased recommends using at3.2xlargeinstance if using AWS.

Provision a VM with the following requirements

  • An operating system supported by kurl.sh. (Amazon Linux 2 is strongly encouraged, followed by Ubuntu 20.04 and 18.04)
  • 6 or more CPUs
  • 8GB or more RAM
  • 75GB or more free on the root volume
  • A DNS hostname that resolves to the public IP address of the EC2 instance (setup with Route53, etc). You'll use this DNS hostname to access Cased Shell's web application. (cased-shell.example.com)
  • A separate DNS hostname that points to the same public IP address. You'll use this DNS hostname to access Cased Shell's Admin Portal, which will guide you through the process of configuring and updating Cased Shell. (admin.cased-shell.example.com)
  • Access to ports 22, 80, 443, 8800
  • Network access to the hosts you would like to access

Confirm that you can SSH to the VM using both hostnames you've configured

Run the installer script

curl -sSL https://k8s.kurl.sh/cased-shell | sudo bash
Once the script has completed:
  • Locate the license sent to you by your Cased Shell account rep. You'll need this to proceed.
  • Visit the URL output by the above command.
  • Ignore the TLS warnings and the prompt to upload a certificate - a certificate will automatically be obtained from Let's Encrypt on deploy.
  • Check all the boxes. Use letsencrypt-prod cert-issuer. Enter your email.
  • Wait a few minutes while the install completes. You should see the status changed from Missing to Unavailable to Ready.
  • Once the install reports as Ready, click the "Open Cased Shell" link to visit Cased Shell.