Best Practices for CloudShell Production Environment

This article discusses an assortment of best practices and recommendations for CloudShell production environments. In this article:

CloudShell Deployments

Start small and grow as you go: It is possible to install CloudShell suite components on a single machine and later redistribute different components to different servers as appropriate.
Back up all custom configuration files to a central location whenever a change is made, including the customer.config, webconfig.xml and language override files.
For high workloads, we may recommend certain CloudShell configurations. Contact Customer Success for guidance.

Do not use Windows client versions for CloudShell Server machines (Quali Server, Portal, Execution Servers, DB). For details, see Servers.
L1 resource automation is managed by Quali Server, unlike shells and scripts which are handled by the Execution Servers. So, make sure Quali Server has access to your Layer 1 devices.
If you're using CloudShell's RabbitMQ, change its default user's credentials, as explained in Update the RabbitMQ Credentials on Quali Server.

Use Elasti Stack (Filebeat) for additional logging and log visualization capabilities. For details, see https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-getting-started.html.

Execution Servers must have access to the respective non-L1 devices and cloud providers.
Execution Server redundancy: it is recommended to provision different parts of your lab to specific Execution Servers both for security purposes and performance. For details, see Setting Up Execution Servers to Run Commands.

Use full IIS and not IIS Express.
Do not turn off logging.
Use HTTPS with a signed certificate.
Set the value of the ASP Threads Per Processor Limit property: The default value is 25. The maximum recommended value is 100.
Enable IIS HTTP compression, as explained in Enable dynamic compression on your IIS settings.

Set Kubernetes-based CloudShell services to use static IPs. For details, see Set the Mongo, Rabbit and Sandbox Services to Use Static IPs.
It is recommended to use Kubernetes secrets to store sensitive information like user details and passwords instead of plain text. For details, see Customize the Deployment Configuration Parameters.
If you're using the CloudShell-deployed RabbitMQ, change its default user's credentials, as explained in Update the RabbitMQ Credentials in Kubernetes Environment

Set a password on the PyPi Server repository (in the Quali Server configuration wizard) to avoid breaking shell and script executions. Python package versions in the Quali Server’s pypi server repository will constrict sandbox automation to use those packages, even if a newer version exists on public PyPi.

Use Full MSSQL and not SQL Express.
Perform a daily backup of your CloudShell databases. For details, see Back Up and Restore CloudShell.
- Use backup compression
Use RAID 10 configuration for user binaries, data, log files, and TempDB for best performance and availability.
Allocate the right memory for MSSQL. More..
Avoid using the SA account. Use Windows Authorization instead.
Do not compress files/databases.
Create an SQL Server Database Alert for all events with a severity of 19 [fatal] and higher. For details, see https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/create-a-sql-server-database-alert?view=sql-server-ver15
For SQL Server Standard Edition hosted on a VM: SQL Server Standard Editions are limited to four sockets, or 24 physical cores, whichever is lower. So if you are using a VM, make sure that it is set to a maximum of 4 sockets, and '2 or more' cores per socket.

Not following these suggestions may result in performance issues. For example, if the VM is set to use 8 sockets and 1 core per socket, since SQL Standard Edition only supports 4 sockets, only 50% of CPU is utilized.

Schedule the daily ElastiCube build to start after it syncs with the CloudShell Insight DB. For details, see Synchronization.

Key management: CloudShell admin configuration keys provide many customization options. Applying keys requires restarting certain CloudShell services. During this time, certain CloudShell functionality may be unavailable. We therefore recommend to set a Maintenance Window in which to set the keys. For details about configuration keys, see Advanced CloudShell Customizations.
Before migrating to your Production environment, make sure to test the staging environment against actual resources/Apps and traffic.