reference deployment

HashiCorp Nomad on AWS

Cluster manager and deployment scheduler

This Quick Start deploys HashiCorp Nomad to the Amazon Web Services (AWS) Cloud. Nomad is a distributed, highly available, data center-aware cluster manager and scheduler that helps deploy applications on premises or in the cloud. It supports virtualized, containerized, and standalone applications that run on all major operating systems and handles a broad range of workloads.

This Quick Start was developed by HashiCorp in collaboration with AWS. HashiCorp is an AWS Partner.

  •  What you'll build
  • Use this Quick Start to automatically set up the following HashiCorp Nomad environment, which also includes HashiCorp Consul, on AWS:

    • A virtual private cloud (VPC) configured with public and private subnets across three Availability Zones. This provides the network infrastructure for your HashiCorp Nomad deployment.*
    • An internet gateway to provide access to the internet. The bastion hosts use this gateway to send and receive traffic.*
    • In the public subnets, NAT gateways to provide outbound Internet connectivity for your HashiCorp Consul and Nomad instances.*
    • In the public subnets, Linux bastion hosts to allow inbound Secure Shell (SSH) access to your HashiCorp Consul and Nomad instances.*
    • An AWS Identity and Access Management (IAM) instance role with fine-grained permissions for access to AWS services necessary for the deployment process.
    • Security groups to enable communication within the VPC and to restrict access to only necessary protocols and ports.
    • In the private subnets, a user-configurable number of HashiCorp Consul server and client instances within separate Auto Scaling groups. If the number of client nodes is set to 0 (which is the default), the Quick Start won’t create the Consul client Auto Scaling group, and Consul client instances will be co-located on Nomad client and server instances instead.
    • In the private subnets, a user-configurable number of HashiCorp Nomad client and server instances within separate Auto Scaling groups.  

    *  The template that deploys the Quick Start into an existing VPC skips the tasks marked by asterisks and prompts you for your existing VPC configuration.

    To build this architecture on AWS, the Quick Start implements a modular structure that uses and extends three other reference deployments:

  •  How to deploy
  • To deploy this Quick Start, follow the steps in the deployment guide, which includes these steps. The stack takes about 35 minutes to launch.

    1. Sign in to your AWS account. If you don't have an account, sign up at
    2. Launch the Quick Start. (Before you create the stack, choose the AWS Region from the top toolbar.) Choose one of the following options:
    3. Use an SSH agent to access Nomad, and verify the deployment.
    4. Use the sample file provided with the Quick Start to get started using Nomad.

    To customize your deployment, choose different instance types for your resources, and set the number of Nomad and Consul server and client nodes.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy the Quick Start, create  AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information about the report, refer to  What are AWS Cost and Usage Reports?