hcp-consul
hashicorp/hcp-consul/aws
Terraform module for HCP Consul on AWS
HCP Consul on AWS Module Terraform module for connecting a HashiCorp Cloud Platform (HCP) Consul cluster to AWS. Usage This module connects a HashiCorp Virtual Network (HVN) with an AWS VPC, ensuring that all networking rules are in place to allow a Consul client to communicate with the HCP Consul servers. The module accomplishes this in four steps: 1. Create and accept a peering connection between the HVN and VPC 2. Create HVN routes that will direct HCP traffic to the CIDR ranges of the subnets. 3. Create AWS routes for each AWS route table that will direct traffic to the HVN's own CIDR range. 4. Create AWS ingress rules necessary for HCP Consul to communicate to Consul clients. ``hcl module "aws_hcp_consul" { source = "hashicorp/hcp-consul/aws" hvn = hcp_hvn.main vpc_id = "vpc-0daa4a091
| Name | Type | Description | Default |
|---|---|---|---|
| route_table_ids | list(string) | A list of route table IDs which should route to the the HVN's CIDR | |
| hvn | object({ hvn_id = stri | The HCP HVN to connect to the VPC | |
| vpc_id | string | The ID of your AWS VPC | |
| subnet_ids | list(string) | A list of subnet IDs which should route to/from the the HVN's CIDR | |
| security_group_ids | list(string) | A list of security group IDs which should allow inbound Consul client traffic. I | [] |
security_group_id — Newly created AWS security group that allow Consul client communication, if 'security_group_ids' wasAzure landing zones Terraform module
Terraform supermodule for the Terraform platform engineering for Azure
Terraform module to deploy landing zone subscriptions (and much more) in Azure
Terraform Module to define a consistent naming convention by (namespace, stage,