Terraform 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 Terraform 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.

Terraform Sandbox
Experiment with Terraform. This sandbox includes Docker and LocalStack preinstalled to test your Terraform configuration.
Launch Sandbox

Sandbox documentation

This sandbox includes the following preinstalled tools and services:

Terraform
Docker
LocalStack
AWS CLI

For more information, click on the "Architecture" tab.

Use LocalStack

LocalStack is a local AWS emulator that you can run the Terraform and the AWS CLI against to test your configuration and mock the deployment of resources. This sandbox includes a file named localstack_overrides.tf that configures the AWS provider in your configuration to point to LocalStack instead of trying to reach AWS. For the limitations of what APIs you can call using LocalStack, click on the "Limitations" tab.

Use AWS

If you would like you deploy resources to AWS, you can delete the localstack_overrides.tf file and configure the AWS provider using the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

Note

Once the timer on the sandbox expires, this environment will be halted. If you have any resources managed by a local state file, this sandbox will not clean up those resources. Make sure to run `terraform destroy` before leaving the sandbox if you have configured the AWS provider to deploy real resources to your own AWS account.

This sandbox includes the following preinstalled tools and services:

Terraform: The Terraform CLI is installed locally and placed in the environment's PATH. To see which version of Terraform is installed in this sandbox, run the terraform version command.
Docker: Docker is already running with the default configuration. The Docker daemon socket file is located at /var/run/docker.sock.
LocalStack: LocalStack is already running in the local Docker instance. Additionally, the localstack_override.tf file is included to automatically configure your AWS provider to point to LocalStack rather than AWS. You do not need to make any changes to your configuration to connect to LocalStack.
AWS CLI: This sandbox has the aws command aliased to the awslocal CLI, the tool to make AWS CLI calls to LocalStack. You can use this tool just as you would the normal aws CLI. For example, the following command will communicate with LocalStack to get a list of the EC2 instances it currently has mocked.
```
$ aws ec2 describe-instances
```

Other sandboxes

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

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
InteractiveInteractive Sandbox
Nomad Sandbox
Experiment with Nomad. This sandbox contains a Nomad cluster with one server and one client node with TLS and ACLs enabled.
Nomad