vpc-peering-multi-account
cloudposse/vpc-peering-multi-account/aws
Terraform module to provision a VPC peering across multiple VPCs in different accounts by using multiple providers
Terraform module to create a peering connection between any two VPCs existing in different AWS accounts. This module supports performing this action from a 3rd account (e.g. a "root" account) by specifying the roles to assume for each member account. IMPORTANT: AWS allows a multi-account VPC Peering Connection to be deleted from either the requester's or accepter's side. However, Terraform only allows the VPC Peering Connection to be deleted from the requester's side by removing the corresponding aws_vpc_peering_connection resource from your configuration. Read more about this on Terraform's documentation portal. Screenshots VPC Peering Connection in the AWS Web Console > [!TIP] > #### 👽 Use Atmos with Terraform > Cloud Posse uses atmos to easily orchestrate multiple environments using Ter
| Name | Type | Description | Default |
|---|---|---|---|
| namespace | string | ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp' | null |
| environment | string | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'st | null |
| accepter_allow_remote_vpc_dns_resolution | bool | Allow accepter VPC to resolve public DNS hostnames to private IP addresses when | true |
| aws_route_create_timeout | string | Time to wait for AWS route creation specifed as a Go Duration, e.g. `2m` | "5m" |
| name | string | ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. Thi | null |
| accepter_enabled | bool | Flag to enable/disable the accepter side of the peering connection | true |
| requester_allow_remote_vpc_dns_resolution | bool | Allow requester VPC to resolve public DNS hostnames to private IP addresses when | true |
| accepter_subnet_tags | map(string) | Only add peer routes to accepter VPC route tables of subnets matching these tags | {} |
| enabled | bool | Set to false to prevent the module from creating any resources | null |
| tenant | string | ID element _(Rarely used, not included by default)_. A customer identifier, indi | null |
| delimiter | string | Delimiter to be used between ID elements. Defaults to `-` (hyphen). Set to `""` | null |
| aws_route_delete_timeout | string | Time to wait for AWS route deletion specifed as a Go Duration, e.g. `5m` | "5m" |
| labels_as_tags | set(string) | Set of labels (ID elements) to include as tags in the `tags` output. Default is | [
"default"
] |
| label_value_case | string | Controls the letter case of ID elements (labels) as included in `id`, set as tag | null |
| accepter_vpc_id | string | Accepter VPC ID filter | "" |
| accepter_vpc_tags | map(string) | Accepter VPC Tags filter | {} |
| add_attribute_tag | bool | If `true` will add additional attribute tag to the requester and accceptor resou | true |
| context | any | Single object for setting entire context at once. See description of individual | {
"additional_tag_map": {},
"attribu |
| requester_subnet_tags | map(string) | Only add peer routes to requester VPC route tables of subnets matching these tag | {} |
| requester_vpc_tags | map(string) | Requester VPC Tags filter | {} |
requester_accept_status — Requester VPC peering connection request statusaccepter_connection_id — Accepter VPC peering connection IDaccepter_accept_status — Accepter VPC peering connection request statusaccepter_subnet_route_table_map — Map of accepter VPC subnet IDs to route table IDsrequester_connection_id — Requester VPC peering connection IDAzure 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,