All Projects → hashicorp → Best Practices

hashicorp / Best Practices

Licence: mpl-2.0
No description, website, or topics provided.

Programming Languages

HCL
1544 projects
shell
77523 projects
powershell
5483 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Best Practices

Terraform Example
Terraform, Ansible, sticky tape and magic
Stars: ✭ 98 (-93.37%)
Mutual labels:  hcl
Solutions Terraform Cloudbuild Gitops
Stars: ✭ 106 (-92.83%)
Mutual labels:  hcl
Terraform Aws Ecr
Terraform Module to manage Docker Container Registries on AWS ECR
Stars: ✭ 110 (-92.56%)
Mutual labels:  hcl
Aws Minikube
Single node Kubernetes instance implemented using Terraform and kubeadm
Stars: ✭ 101 (-93.17%)
Mutual labels:  hcl
Spinnaker Terraform
A set of terraform scripts to create an environment from scratch with a Bastion Host, Jenkins, and Spinnaker
Stars: ✭ 106 (-92.83%)
Mutual labels:  hcl
Aws Ecs Airflow
Run Airflow in AWS ECS(Elastic Container Service) using Fargate tasks
Stars: ✭ 107 (-92.76%)
Mutual labels:  hcl
Vaultron
🤖 Vault clusters Terraformed onto Docker for great fun and learning!
Stars: ✭ 96 (-93.5%)
Mutual labels:  hcl
Aws Lambda Es Cleanup
AWS Elasticsearch Lambda Curator
Stars: ✭ 112 (-92.42%)
Mutual labels:  hcl
Libvirt K8s Provisioner
Automate your k8s installation
Stars: ✭ 106 (-92.83%)
Mutual labels:  hcl
Terraform Aws Vpc
An example of Terraform which brings up a VPC with Public/Private Subnets
Stars: ✭ 109 (-92.63%)
Mutual labels:  hcl
Typhoon
Minimal and free Kubernetes distribution with Terraform
Stars: ✭ 1,397 (-5.48%)
Mutual labels:  hcl
Terraform Aws Dynamic Subnets
Terraform module for public and private subnets provisioning in existing VPC
Stars: ✭ 106 (-92.83%)
Mutual labels:  hcl
Terraform Aws Config
Enables AWS Config and adds managed config rules with good defaults.
Stars: ✭ 107 (-92.76%)
Mutual labels:  hcl
Example Pragmatic Terraform
『実践Terraform』のサンプルコード
Stars: ✭ 99 (-93.3%)
Mutual labels:  hcl
Terraform Config
Terraform bits and bytes
Stars: ✭ 111 (-92.49%)
Mutual labels:  hcl
Cobalt
Infrastructure turn-key solution for app service workloads
Stars: ✭ 97 (-93.44%)
Mutual labels:  hcl
Aws Accounts Terraform
Stars: ✭ 108 (-92.69%)
Mutual labels:  hcl
Awesome Codepipeline Ci
an AWS CodePipeline, AWS CodeBuild, AWS APIGateway & AWS Lambda CI
Stars: ✭ 112 (-92.42%)
Mutual labels:  hcl
Terraform Up And Running Code
Code samples for the book "Terraform: Up & Running" by Yevgeniy Brikman
Stars: ✭ 1,739 (+17.66%)
Mutual labels:  hcl
Terraform Google Vault
A Terraform Module for how to run Vault on Google Cloud using Terraform and Packer
Stars: ✭ 108 (-92.69%)
Mutual labels:  hcl

Deprecated

This repository is deprecated. Please checkout the official Terraform Module Registry instead.

Best Practices Ops

Below are the infrastructures we currently have best practices for. Navigate to each provider to see what will be provisioned.

Getting Started

This repository contains best-practice infrastructures across different cloud providers, regions, environments, and operating systems.

You can think of this as a library of Packer templates and Terraform modules that allow you to provision unique infrastructures by referencing the different templates and modules. We've tried to set this repository up in a way that we don't have to duplicate code, allowing templates and modules to be used across multiple environments.

Each environment is a best practices guide for how to use HashiCorp tooling to provision that specific type of infrastructure. Use each as a reference when building your own infrastructure. The best way to get started is to pick an environment that resembles an infrastructure you are looking to build, get it up and running, then configure and modify it to meet your specific needs.

No example will be exactly what you need, but it should provide you with enough examples to get you headed in the right direction.

A couple things to keep in mind...

  • Each environment's README will reference different sections in General Setup to get your environment properly setup to build the infrastructure at hand.
  • Each environment will assume you're using Atlas. If you plan on doing anything locally, there are portions of environments that may not work due to the extra features Atlas provides that we are taking advantage of.
  • Each environment's instructional documentation is based off of the assumption that certain information will be saved as environment variables. If you do not wish to use environment variables, there are different ways to pass this information, but you may have to take extra undocumented steps to get commands to work properly.
  • Any packer push commands must be performed in the base packer/. directory.
  • Any terraform push commands must be performed in the appropriate Terraform environment directory (e.g. terraform/providers/aws/us_east_1_staging).
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].