make init
will configure terraform, and ensure that you are using the correct version and have a valid set of terraform scripts.make plan
will run your terraform scripts to decide which infrastructure needs provisioning, the data centres it will use, and the names to give the infrastructure. This stage just creates a plan, no changes will be applied.out-bundle
, this file contains the details and connection information for the Hadean provisioning service to install the Hadean Platform to the newly created cluster. Download the file by clicking Upload/Download files. Save it somewhere accessible, you'll upload it to the Hadean Portal in the next step.make init
will configure terraform, and ensure that you are using the correct version and have a valid set of terraform scripts.make plan
will run your terraform scripts to decide which infrastructure needs provisioning, the data centres it will use, and the names to give the infrastructure. This stage just creates a plan, no changes will be appliedout-bundle
, this file contains the details and connection information for the Hadean provisioning service to install the Hadean Platform to the newly created cluster. Download the file by clicking Actions > Download file. Provide the path to the cluster bundle inside out-bundle
for example: $HOME/hadean-aws-terraform-scripts/out-bundle/hadean-cluster-bundle.zip
, click Download and this will be downloaded to your machine. Save it somewhere accessible, you'll upload it to the Hadean Portal in the next step.terraform.edgeconfig.auto.tfvars.json
. This file dictates where Connect nodes should be deployed, how many, and what machine size they should have. The information required by each cloud provider differs slightly so please refer to the correct tab for the cloud provider you are using. By default the Terraform scripts are configured to create a node in the default simulation location.uksouth
, two in eastus
and one in ukwest
. They all share the same machine size of Standard_D8s_v3
.az account list-locations -o table
for a list of available locations.az vm list-sizes -o table --location uksouth
for a list of available machine sizes in a given location. Note: replace uksouth
with the location you need machine size information from.eu-west-2a
, two Muxers in us-east-2a
, one in eu-west-1a
and one in eu-west-1b
. They all share the same machine size of m5.2xlarge
.aws ec2 describe-regions --query "Regions[].{Name:RegionName}" --output text
for a list of available regions.aws ec2 describe-instance-types --query 'InstanceTypes[].InstanceType | sort(@)' --output text --region eu-west-2
for a list of available machine sizes in a given region. Note: replace eu-west-2
with the region you need machine size information from.aws ec2 describe-availability-zones --query 'AvailabilityZones[*].[ZoneName]' --output text --region eu-west-2
for a list of availablity zones in a given region. Note: replace eu-west-2
with the region you need availability zone information from.tags.tfvars
and fill out accordingly.terraform.tfvars
file. It's recommended that your components are in a close proximity with regards to locale. This will enable components to take advantage of higher bandwidth and lower latency connections.EXTRA_TF_ARGS
. For example: