influx

gruntwork-io/influx/aws

Terraform Module HCL AWS ⏱ stale 1y 8mo

Reusable infrastructure modules for running TICK stack on AWS

Install

module "influx" {

source = "gruntwork-io/influx/aws"

version = "0.2.0"

}

⭐ Source on GitHub 📦 Registry page

README

![Maintained by Gruntwork.io](https://gruntwork.io/?ref=repo_aws_influx) TICK Stack AWS Module This repo contains the official module for deploying the TICK stack on AWS using Terraform and Packer. !TICK multi-cluster architecture Quick start If you want to quickly spin up an InfluxDB cluster, you can run the simple example that is in the root of this repo. Check out influxdb-cluster-simple example documentation for instructions. What's in this repo This repo has the following folder structure: - root: The root folder contains an example of how to deploy InfluxDB as a single-cluster. See influxdb-cluster-simple for the documentation. - modules: This folder contains the main implementation code for this Module, broken down into multiple standalone submodules. - examples: This folder contain

Inputs (9)

Name	Type	Description	Default
license_key	string	The key of your InfluxDB Enterprise license. This should not be set in plain-tex	required
ami_id	string	The ID of the AMI to run in the cluster. This should be an AMI built from the Pa	required
shared_secret	string	A long pass phrase that will be used to sign tokens for intra-cluster communicat	required
ssh_key_name	string	The name of an EC2 Key Pair that can be used to SSH to the EC2 Instances in this	required
aws_region	string	The AWS region in which all resources will be created	`"us-east-1"`
influxdb_cluster_name	string	What to name the InfluxDB meta nodes cluster and all of its associated resources	`"influxdb-cluster"`
volume_mount_point	string	The mount point (folder path) to use for the EBS Volume used for the meta, data,	`"/influxdb"`
volume_owner	string	The OS user who should be made the owner of mount points.	`"influxdb"`
volume_device_name	string	The device name to use for the EBS Volume used for the meta, data, wal and hh di	`"/dev/xvdh"`