Configuring your Cased Shell instance

A quick guide to make your Cased Shell instance ready for your production environment.

Basic configuration

Configuration happens in the Cased app. You don't need to worry about storing data with your Cased Shell instance. You can destroy and create the instance as often as you like. It only a couple of simple steps to configure your instance.

1. Create a new Cased Shell

On the Cased app dashboard, click "Set up a web shell instance".

Then, simply enter the hostname or IP address the Web Shell will be running on and click "Create Shell".

Once created, you can access your Web Shell instance via the URL you assigned it to, or in the Cased app dashboard which will list all of your instances.

2. Go to the settings page

Visit your settings page for this Shell instance by clicking the "Settings" tab on the Cased Shell dashboard.

The first item that appears on the Settings page is your Cased Shell Secret key. Here you are given the option to roll your key which will cause your current key to expire and generate a new key for you to use. Users may be able to customize how long the new key generated will last as well as add a reason for rolling the key for logging purposes.

The second setting that pops up is configuring your SSH key. By default, users are enabled with SSH certificate authentication, the best practice for SSH. However, if desired, users are able to turn it off to revert back to SSH key authentication.

3. Add/remove hosts

On the configure hosts section, users are able to add/remove hosts to their instance as a static list of hosts. Your Cased Shell instance will then automatically pick up those hosts and make them available for you. Alternatively, enable Cased's host and container auto-detection to where users won't have to manually configure their prompts - they'll be listed on the dashboard automatically.

4. Other Settings

The settings page also shows a listing of the custom snippets a user has created in their shell instance. There are also three options a user can enable for more customization: reason required, block new sessions if Cased can't be reached, and recording an output for each session. These options are mainly used for more visibility and oversight into one's organization. And lastly, users have the option to add notifications for SSH sessions directly into Slack where users can approve and deny access to sessions.

Questions? Contact us.

Did this page help you?