Nomad Interactive Sandboxes

Experiment with HashiCorp products in a safe, pre-configured environment.

HashiCorp Sandboxes provide interactive environments where you can experiment with HashiCorp products without any installation or setup. They're perfect for:

Learning how products work in a real environment
Testing configurations and commands without affecting your systems
Exploring product features in a safe sandbox
Following along with tutorials and documentation

Each sandbox comes pre-configured with everything you need to start using the product immediately. Just click on a sandbox below to launch it in your browser.

Available Nomad sandboxes

When you launch a sandbox, you'll be presented with a terminal interface where you can interact with the pre-configured environment. The sandbox runs in your browser and doesn't require any downloads or installations.

Each sandbox session lasts for up to 1 hour, giving you plenty of time to experiment. Your work isn't saved between sessions, so be sure to copy any important configurations before your session ends.

Nomad Sandbox
Experiment with Nomad. This sandbox contains a Nomad cluster with one server and one client node with TLS and ACLs enabled.
Launch Sandbox

Sandbox documentation

Warning

This sandbox is not a production-ready environment. It is a development and testing environment with security configurations for gossip encryption, TLS, and ACLs enabled. For more information about deploying Nomad in production, refer to Installing Nomad for Production.

This sandbox provides a Nomad cluster that consists of one server node and one client node. Each node runs a Nomad agent and a Consul agent. Both agents are configured with ACLs, gossip encryption, and TLS encryption. The server node also runs a single-node Vault cluster that has been initialized and unsealed. The client node has access to a scoped token for reading secrets from Vault. You can also read Vault secrets from a Nomad jobspec.

To interact with the Nomad, Consul, and Vault CLIs, you must load the necessary tokens.

$ env | grep "NOMAD\|CONSUL\|VAULT"

Nomad and Consul ACL management tokens are located in /ops/configs/tokens. You can use them to log in to the web UIs.

$ cat /ops/configs/tokens/nomad_mgmt.token
$ cat /ops/configs/tokens/consul_mgmt.token

You can find the Vault's unseal key, certificates, and root token in /ops/configs/vault.

$ cat /ops/configs/vault/vault_root.token

This sandbox includes sample Nomad jobspecs that you can use to run jobs. Use the following commands to submit the jobs to Nomad:

$ nomad job run /ops/configs/jobspecs/2048.hcl
$ nomad job run /ops/configs/jobspecs/terramino.hcl
$ nomad job run /ops/configs/jobspecs/hashicups.hcl

Infrastructure

Server node (node-01-server)
- n1-standard-2 VM (2 vCPU, 7.5GB RAM, 128GB disk)
  - Nomad agent configured and running
    - Access pre-configured with environment variables (NOMAD_*)
    - Management token saved to NOMAD_TOKEN
  - Consul agent configured and running
    - Access pre-configured with environment variables (CONSUL_*)
      - Management token saved to CONSUL_TOKEN
  - Vault agent configured and running
    - Access pre-configured with environment variables (VAULT_*)
      - Root token saved to VAULT_TOKEN
Client node (node-02-client)
- n1-standard-2 VM (2 vCPU, 7.5GB RAM, 128GB disk)
  - Nomad agent configured and running
  - Consul agent configured and running
- Vault access pre-configured with environment variables (VAULT_*)
- Nomad drivers: docker, exec, java, raw_exec

Directory structure

Environment related files are in the /ops directory.

/ops
└── configs
    ├── agentfiles
    │   ├── consul_server.hcl
    │   └── nomad_server.hcl
    ├── env-info
    │   ├── ARCHITECTURE
    │   ├── LIMITATIONS
    │   └── README
    ├── jobspecs
    │   ├── 2048.hcl
    │   ├── hashicups.hcl
    │   └── terramino.hcl
    ├── tokens
    │   ├── consul_agent_server.token
    │   ├── consul_dns.token
    │   ├── consul_gossip_key
    │   ├── consul_mgmt.token
    │   ├── nomad_gossip_key
    │   ├── nomad_mgmt.token
    │   └── nomad_node_join.token
    └── vault
        ├── data
        ├── dev-app-secrets.token
        ├── unseal.key
        ├── vault-cert.pem
        ├── vault-key.pem
        ├── vault-server.hcl
        └── vault_root.token

Logs are output to the /tmp directory.

$ ls /tmp
├── consul.log
├── nomad.log
└── vault.log

HashiCorp applications

The sandbox includes the following HashiCorp applications:

Nomad
- One server node and one client node
- ACLs enabled
- Gossip encryption enabled
- TLS encryption enabled
Consul
- One server node and one client node
- ACLs enabled
- Gossip encryption enabled
- TLS encryption enabled
- DNS configured (.consul domain)
Vault
- TLS encryption enabled
- Initialized and unsealed

The agent files for Nomad and Consul exist in the /ops/configs/agentfiles directory. If you make changes to the agent configuration files, you must restart the agent for the changes to take effect. Use the following commands to restart the agents.

$ pkill nomad
$ nomad agent \
  -config=/ops/configs/agentfiles/nomad_server.hcl \
  >> /tmp/nomad.log 2>&1 &

$ pkill consul
$ consul agent \
  -config-file=/ops/configs/agentfiles/consul_server.hcl \
  >> /tmp/consul.log 2>&1 &

Other sandboxes

Explore sandboxes for other HashiCorp products that you might find useful.

InteractiveInteractive Sandbox
Terraform Sandbox
Experiment with Terraform. This sandbox includes Docker and LocalStack preinstalled to test your Terraform configuration.
Terraform
InteractiveInteractive Sandbox
Vault Sandbox
Experiment with Vault. This sandbox contains five Vault Docker containers and a reverse proxy container.
Vault
InteractiveInteractive Sandbox
Boundary Sandbox
Experiment with Boundary. This sandbox contains a Boundary cluster (one controller server and one worker) configured with a Boundary target (Ubuntu 24.04) and a Postgres database.
Boundary
InteractiveInteractive Sandbox
Consul Sandbox (Service discovery)
Experiment with Consul. This sandbox contains a Consul cluster (3 servers and 4 clients) and a Bastion host. It also runs HashiCups, a demo web application.
Consul
InteractiveInteractive Sandbox
Consul Sandbox (Service mesh)
Experiment with Consul. This sandbox contains a Consul cluster (3 servers and 4 clients) and a Bastion host. It also runs HashiCups, a demo web application.
Consul