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.
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 contains examples of how to use the submodules.
- test: Automated tests for the submodules and examples.
The general idea is to:
Use the scripts in the install-influxdb modules to create an AMI with InfluxDB Enterprise installed.
Deploy the AMI across one or more Auto Scaling Groups (ASG) using the influxdb-cluster module.
Configure each server in the ASGs to execute the run-influxdb script during boot.
Deploy a load balancer in front of the data node ASG.
See the examples folder for working sample code.
A Module is a canonical, reusable, best-practices definition for how to run a single piece of infrastructure, such as a database or server cluster. Each Module is written using a combination of Terraform and scripts (mostly bash) and include automated tests, documentation, and examples. It is maintained both by the open source community and companies that provide commercial support.
Instead of figuring out the details of how to run a piece of infrastructure from scratch, you can reuse existing code that has been proven in production. And instead of maintaining all that infrastructure code yourself, you can leverage the work of the Module community to pick up infrastructure improvements through a version number bump.
- Setup, customization, and support for this Module.
- Modules for other types of infrastructure, such as VPCs, Docker clusters, databases, and continuous integration.
- Modules that meet compliance requirements, such as HIPAA.
- Consulting & Training on AWS, Terraform, and DevOps.
Contributions are very welcome! Check out the Contribution Guidelines for instructions.
During initial development, the major version will be 0 (e.g.,
0.x.y), which indicates the code does not yet have a
stable API. Once we hit
1.0.0, we will make every effort to maintain a backwards compatible API and use the MAJOR,
MINOR, and PATCH versions on each release to indicate any incompatibilities.
Copyright © 2018 Gruntwork, Inc.