This article explains how to create a sandbox from scratch.
You can also create a sandbox directly from a blueprint in the Blueprints tab. For details, see Launching a Sandbox From a Blueprint.
To launch a sandbox from Torque's UI:
- In the Sandbox Environments page, click New Sandbox.
- The Select a Blueprint page is displayed.
- Enter the Sandbox Name and click Next.
- In the Select a Blueprint page, click the suitable blueprint.
Optionally, use the filters above the blueprints to find your blueprint by type. Supported types are:
- Torque: Blueprints defined in YAML files.
- Terraform: Blueprints based on Terraform modules
- Helm: Blueprints based on Helm charts
- In the Set Duration page, set the sandbox duration.
Optionally select Run Indefinitely to run the sandbox without an end time. This is useful if you have a sandbox that must be online at all times, like a sandbox that contains a resource shared by different teams in your company, such as a DB server.
Note how the sandbox cost changes as you set the duration. The cost is based on the blueprint’s past executions.
An indefinitely running sandbox is not a production environment, which provides blue/green functionality for staging development cycles and promoting them to production.
- At the bottom of the screen click Next.
- Enter the sandbox’s parameters and artifacts details. These include:
- Parameters / Artifacts: Each sandbox may require different parameters and artifact details. These are provided by the blueprint used to launch this sandbox. The parameters are typically used by an application's Initialization script when configuring the application. For example, database credentials, log location, etc. The artifact is a binary file used by the Initialization script to install the application. The artifact details are used to specify the location in which the application's artifacts will be installed.
- Tags: Set the blueprint tags. There are two types of tags:
- activity_type: Select the type of activity you are doing in the sandbox.
- (If applicable) Custom tags to be applied to the environment’s cloud resources.
- Click Launch Sandbox.
Once the deployment of your sandbox begins, the sandbox details screen is displayed, showing the sandbox’s details and deployment progress. Note the sandbox’s Current Cost, indicating the real-time cloud cost of your sandbox.
When the sandbox environment is ready, the sandbox state changes to Active and you should receive a notification email.
NOTE: In AWS environments, the applications may be inaccessible immediately after the environment becomes Active. This issue should resolve itself within a few moments when the AWS DNS propagation process completes.
You can launch a sandbox based on an earlier version of an environment. To learn more, see Launching a Sandbox Based on an Earlier Environment.