Use this repo to easily provision a Nomad sandbox environment on AWS, Azure, or GCP with Packer and Terraform. Consul and Vault are also installed (colocated for convenience). The intention is to allow easy exploration of Nomad and its integrations with the HashiCorp stack. This is not meant to be a production ready environment.
Clone the repo and optionally use Vagrant to bootstrap a local staging environment:
$ git clone [email protected]:hashicorp/nomad.git
$ cd nomad/terraform
$ vagrant up && vagrant sshThe Vagrant staging environment pre-installs Packer, Terraform, Docker and the Azure CLI.
- Follow the steps here to provision a cluster on AWS.
- Follow the steps here to provision a cluster on Azure.
- Follow the steps here to provision a cluster on GCP.
Continue with the steps below after a cluster has been provisioned.
Run a few basic status commands to verify that Consul and Nomad are up and running properly:
$ consul members
$ nomad server members
$ nomad node statusTo initialize and unseal Vault, run:
$ vault operator init -key-shares=1 -key-threshold=1
$ vault operator unseal
$ export VAULT_TOKEN=[INITIAL_ROOT_TOKEN]The vault init command above creates a single
Vault unseal key for
convenience. For a production environment, it is recommended that you create at
least five unseal key shares and securely distribute them to independent
operators. The vault init command defaults to five key shares and a key
threshold of three. If you provisioned more than one server, the others will
become standby nodes but should still be unsealed. You can query the active
and standby nodes independently:
$ dig active.vault.service.consul
$ dig active.vault.service.consul SRV
$ dig standby.vault.service.consulSee the Getting Started guide for an introduction to Vault.
Use the following links to get started with Nomad and its HashiCorp integrations: