From 159e6e5b74343d15c7998d65e3b62e122e95492c Mon Sep 17 00:00:00 2001 From: "docs-sourcer[bot]" <99042413+docs-sourcer[bot]@users.noreply.github.com> Date: Fri, 3 Apr 2026 09:01:51 +0000 Subject: [PATCH] Updated with the [latest changes](https://github.com/gruntwork-io/terraform-aws-vpc/pull/558) from the `terraform-aws-vpc@deprecatedattr` source branch. --- .../network-acl-inbound.md | 18 +- .../network-acl-outbound.md | 18 +- .../network-firewall/network-firewall.md | 18 +- .../port-range-calculator.md | 16 +- .../modules/terraform-aws-vpc/route/route.md | 18 +- .../transit-gateway-attachment.md | 20 +- ...sit-gateway-peering-attachment-accepter.md | 20 +- .../transit-gateway-peering-attachment.md | 20 +- .../transit-gateway-route.md | 20 +- .../transit-gateway/transit-gateway.md | 22 +- .../vpc-app-lookup/vpc-app-lookup.md | 18 +- .../vpc-app-network-acls.md | 18 +- .../terraform-aws-vpc/vpc-app/vpc-app.md | 36 +-- .../vpc-dns-forwarder-rules.md | 20 +- .../vpc-dns-forwarder/vpc-dns-forwarder.md | 18 +- .../vpc-flow-logs/vpc-flow-logs.md | 16 +- .../vpc-interface-endpoint.md | 18 +- .../vpc-mgmt-network-acls.md | 18 +- .../terraform-aws-vpc/vpc-mgmt/vpc-mgmt.md | 38 +-- .../vpc-peering-cross-accounts-accepter.md | 68 +++-- .../vpc-peering-cross-accounts-requester.md | 68 +++-- .../vpc-peering-external.md | 100 ++++--- .../vpc-peering/vpc-peering.md | 280 +++++++++++++++--- 23 files changed, 571 insertions(+), 335 deletions(-) diff --git a/docs/reference/modules/terraform-aws-vpc/network-acl-inbound/network-acl-inbound.md b/docs/reference/modules/terraform-aws-vpc/network-acl-inbound/network-acl-inbound.md index 244740351..749712122 100644 --- a/docs/reference/modules/terraform-aws-vpc/network-acl-inbound/network-acl-inbound.md +++ b/docs/reference/modules/terraform-aws-vpc/network-acl-inbound/network-acl-inbound.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Network ACL Inbound Terraform Module -View Source +View Source Release Notes @@ -24,7 +24,7 @@ with because they are stateless, which means that opening an inbound port is oft which your services use to respond. This can be very easy to forget, so this module adds not only the inbound ports to an ACL, but also the ephemeral outbound ports for return traffic. -See the [network-acl-outbound](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/network-acl-outbound) module for the analogous version of this module, but for opening +See the [network-acl-outbound](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/network-acl-outbound) module for the analogous version of this module, but for opening outbound ports. ## What's a Network ACL? @@ -47,7 +47,7 @@ EC2 instance), a network ACL controls what inbound and outbound traffic is allow module "network_acl_inbound" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -134,7 +134,7 @@ module "network_acl_inbound" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.28.12" } inputs = { @@ -220,11 +220,11 @@ inputs = { diff --git a/docs/reference/modules/terraform-aws-vpc/network-acl-outbound/network-acl-outbound.md b/docs/reference/modules/terraform-aws-vpc/network-acl-outbound/network-acl-outbound.md index 1ae2dbc68..ac36ccca9 100644 --- a/docs/reference/modules/terraform-aws-vpc/network-acl-outbound/network-acl-outbound.md +++ b/docs/reference/modules/terraform-aws-vpc/network-acl-outbound/network-acl-outbound.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Network ACL Outbound Terraform Module -View Source +View Source Release Notes @@ -24,7 +24,7 @@ because they are stateless, which means that opening an outbound port is often n which the remote services can use to respond. This can be very easy to forget, so this module adds not only the outbound to an ACL, but also the ephemeral inbound ports for return traffic. -See the [network-acl-inbound](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/network-acl-inbound) module for the analogous version of this module, but for opening +See the [network-acl-inbound](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/network-acl-inbound) module for the analogous version of this module, but for opening inbound ports. ## What's a Network ACL? @@ -47,7 +47,7 @@ EC2 instance), a network ACL controls what inbound and outbound traffic is allow module "network_acl_outbound" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -134,7 +134,7 @@ module "network_acl_outbound" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.28.12" } inputs = { @@ -220,11 +220,11 @@ inputs = { diff --git a/docs/reference/modules/terraform-aws-vpc/network-firewall/network-firewall.md b/docs/reference/modules/terraform-aws-vpc/network-firewall/network-firewall.md index 3018da8d2..d0a48c4b6 100644 --- a/docs/reference/modules/terraform-aws-vpc/network-firewall/network-firewall.md +++ b/docs/reference/modules/terraform-aws-vpc/network-firewall/network-firewall.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Network Firewall Terraform Module - Beta -View Source +View Source Release Notes @@ -41,7 +41,7 @@ AWS Technical Support has confirmed their internal service team's awareness of t ## Usage -For usage examples, check out the [One VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/vpc-app-with-network-firewall/) and [Multi-VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/vpc-app-with-network-firewall-and-transit-gateway/) deployment. +For usage examples, check out the [One VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/vpc-app-with-network-firewall/) and [Multi-VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/vpc-app-with-network-firewall-and-transit-gateway/) deployment. ## Deployment models for AWS Network Firewall @@ -152,7 +152,7 @@ No modules. module "network_firewall" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-firewall?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-firewall?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # OPTIONAL VARIABLES @@ -219,7 +219,7 @@ module "network_firewall" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-firewall?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-firewall?ref=v0.28.12" } inputs = { @@ -976,11 +976,11 @@ The ID of the Network Firewall. diff --git a/docs/reference/modules/terraform-aws-vpc/port-range-calculator/port-range-calculator.md b/docs/reference/modules/terraform-aws-vpc/port-range-calculator/port-range-calculator.md index 5701c86b1..2d6562fdf 100644 --- a/docs/reference/modules/terraform-aws-vpc/port-range-calculator/port-range-calculator.md +++ b/docs/reference/modules/terraform-aws-vpc/port-range-calculator/port-range-calculator.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Port Calculator Module -View Source +View Source Release Notes @@ -50,7 +50,7 @@ just those ports: module "port_range_calculator" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -84,7 +84,7 @@ module "port_range_calculator" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.28.12" } inputs = { @@ -177,11 +177,11 @@ Map of port ranges to the ranges to allow. This is provided as a convenience out diff --git a/docs/reference/modules/terraform-aws-vpc/route/route.md b/docs/reference/modules/terraform-aws-vpc/route/route.md index b191c5bd1..2f880c188 100644 --- a/docs/reference/modules/terraform-aws-vpc/route/route.md +++ b/docs/reference/modules/terraform-aws-vpc/route/route.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Route Module -View Source +View Source Release Notes @@ -30,7 +30,7 @@ This Terraform module creates a route resource. A route is a rule that specifies ## Usage -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/route/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/route/). ## What is a route? @@ -104,7 +104,7 @@ No modules. module "route" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -193,7 +193,7 @@ module "route" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.28.12" } inputs = { @@ -447,11 +447,11 @@ A map of states of the route resources. diff --git a/docs/reference/modules/terraform-aws-vpc/transit-gateway-attachment/transit-gateway-attachment.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway-attachment/transit-gateway-attachment.md index 48de7b0e0..33bf63414 100644 --- a/docs/reference/modules/terraform-aws-vpc/transit-gateway-attachment/transit-gateway-attachment.md +++ b/docs/reference/modules/terraform-aws-vpc/transit-gateway-attachment/transit-gateway-attachment.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Transit Gateway Attachment Terraform Module -View Source +View Source Release Notes @@ -21,7 +21,7 @@ This module creates a transit gateway attachment resource. A transit gateway att The module accepts a map of VPCs for attachment to the transit gateway. See the examples below for the structure of the map. -See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. +See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. ## What is a Transit Gateway Attachment? @@ -29,7 +29,7 @@ A transit gateway attachment is a way to connect a transit gateway (virtual rout ## Usage -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/transit-gateway-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/transit-gateway-attachment/). @@ -90,7 +90,7 @@ No modules. module "transit_gateway_attachment" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -161,7 +161,7 @@ module "transit_gateway_attachment" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.28.12" } inputs = { @@ -388,11 +388,11 @@ The IDs of the Transit Gateway Route Tables. diff --git a/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment-accepter/transit-gateway-peering-attachment-accepter.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment-accepter/transit-gateway-peering-attachment-accepter.md index bb0198c8b..2a5c8c124 100644 --- a/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment-accepter/transit-gateway-peering-attachment-accepter.md +++ b/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment-accepter/transit-gateway-peering-attachment-accepter.md @@ -9,23 +9,23 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Transit Gateway Peering Attachment Accepter Accepter Terraform Module -View Source +View Source Release Notes This Terraform Module creates Transit Gateway peering resources for the `accepter` side of the connection. This allows for connectivity between multiple regions or multiple AWS accounts. Transit Gateway peering is a one-to-one relationship between two transit gateways. If you need to peer multiple transit gateways, you will need to create multiple transit gateway peering attachments. -See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. +See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. ## What is a Transit Gateway Peering Attachment Accepter? A transit gateway peering attachment accepter is a way to connect two transit gateways to each other. Much like the VPC attachment, this can be thought of as a network cable. By attaching them, you 'plug' the two transit gateways together. This allows you to route traffic between the two transit gateways. Unlike VPC attachments, peering attachments have two components to the attachment a `requester` and an `accepter`. This is important because each attachment must be accepted prior to the attachment being completed. This is a security measure to ensure a malicious attachment from a random account does not gain network access to your environment. The `accepter` is the side of the peering attachment that accepts the request from the `requester`. -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/transit-gateway-peering-attachment). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/transit-gateway-peering-attachment). @@ -86,7 +86,7 @@ No modules. module "transit_gateway_peering_attachment_accepter" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -130,7 +130,7 @@ module "transit_gateway_peering_attachment_accepter" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.28.12" } inputs = { @@ -258,11 +258,11 @@ The identifer of the transit gateway for the accepter resources. diff --git a/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment/transit-gateway-peering-attachment.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment/transit-gateway-peering-attachment.md index 82ab4fa6e..3b0e1ac4a 100644 --- a/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment/transit-gateway-peering-attachment.md +++ b/docs/reference/modules/terraform-aws-vpc/transit-gateway-peering-attachment/transit-gateway-peering-attachment.md @@ -9,17 +9,17 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Transit Gateway Peering Attachment Module -View Source +View Source Release Notes This Terraform Module creates transit gateway peering resources for the `requester` side of the connection to another transit gateway. The transit gateway can be in this account or in another account. Transit gateway peering is a one-to-one relationship between two transit gateways. If you need to peer multiple transit gateways, you will need to create multiple transit gateway peering attachments. -See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. +See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. ## What is a Transit Gateway Peering Attachment? @@ -27,7 +27,7 @@ A transit gateway peering attachment is a way to connect two transit gateways to ## Usage -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/transit-gateway-peering-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/transit-gateway-peering-attachment/). @@ -86,7 +86,7 @@ No modules. module "transit_gateway_peering_attachment" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -135,7 +135,7 @@ module "transit_gateway_peering_attachment" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.28.12" } inputs = { @@ -260,11 +260,11 @@ Transit Gateway Peering Attachment identifier diff --git a/docs/reference/modules/terraform-aws-vpc/transit-gateway-route/transit-gateway-route.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway-route/transit-gateway-route.md index a05c43f2d..d59a2e5b0 100644 --- a/docs/reference/modules/terraform-aws-vpc/transit-gateway-route/transit-gateway-route.md +++ b/docs/reference/modules/terraform-aws-vpc/transit-gateway-route/transit-gateway-route.md @@ -9,17 +9,17 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Transit Gateway Route Module -View Source +View Source Release Notes This module creates a route for each CIDR block in a list `cidr_blocks` to a transit gateway route table. The route can be directed to any attachment within the transit gateway or can be configured as a blackhole route. A blackhole route is useful to drop traffic to a given CIDR block, or can be utilized to flush downstream route tables of ephemeral routes. -See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. +See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. > \[!IMPORTANT] > This module may require additional modules or configuration. Other modules, such as the `route` module, may be required to complete the route configuration. This module is intended to be used as a building block for more complex network topologies. @@ -30,7 +30,7 @@ A transit gateway route is a way to route traffic between VPCs, peers, VPNs, and ## Usage -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/transit-gateway-route/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/transit-gateway-route/). @@ -87,7 +87,7 @@ No modules. module "transit_gateway_route" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -127,7 +127,7 @@ module "transit_gateway_route" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.28.12" } inputs = { @@ -226,11 +226,11 @@ Map of ids of the transit gateway routes. diff --git a/docs/reference/modules/terraform-aws-vpc/transit-gateway/transit-gateway.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway/transit-gateway.md index 327813b4c..cc9355776 100644 --- a/docs/reference/modules/terraform-aws-vpc/transit-gateway/transit-gateway.md +++ b/docs/reference/modules/terraform-aws-vpc/transit-gateway/transit-gateway.md @@ -9,21 +9,21 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Transit Gateway Terraform Module -View Source +View Source Release Notes This Terraform module creates a transit gateway resource. A transit gateway is an effective method of connecting multiple VPCs, Direct Connects, VPNs, and other networks. Transit gateways are also a good way to connect VPCs to shared services, such as NAT gateways, firewalls, and other security appliances. By using a transit gateway, the number of connections to and from VPCs can be reduced, which reduces the number of routes that need to be managed. -See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. +See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. ## Usage -For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/examples/transit-gateway/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/examples/transit-gateway/). ## What's a Transit Gateway? @@ -65,7 +65,7 @@ What follows are the steps required to configure Transit Gateway resources withi * Create the Transit Gateway in the first region/account * Create the Transit Gateway in the second region/account * Create a Transit Gateway Peering Connection between the two Transit Gateways - * The peering option can be implemented using this module along with [transit-gateway-peering-attachment](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. + * The peering option can be implemented using this module along with [transit-gateway-peering-attachment](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. * Attach your VPCs to your Transit Gateway * Add routes between the Transit Gateways and your VPCs @@ -132,7 +132,7 @@ No modules. module "transit_gateway" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -205,7 +205,7 @@ module "transit_gateway" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.28.12" } inputs = { @@ -442,11 +442,11 @@ Identifier of the Transit Gateway's default propagation route table. diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-app-lookup/vpc-app-lookup.md b/docs/reference/modules/terraform-aws-vpc/vpc-app-lookup/vpc-app-lookup.md index bc73e9aed..9e6c183c2 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-app-lookup/vpc-app-lookup.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-app-lookup/vpc-app-lookup.md @@ -9,16 +9,16 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC-App Lookup Module -View Source +View Source Release Notes This folder contains a Terraform module which can use data sources to fetch all the data about a VPC created by the -[`vpc-app` module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-app), including the VPC ID, subnet IDs, route table IDs, NAT Gateway IDs, and so on. +[`vpc-app` module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-app), including the VPC ID, subnet IDs, route table IDs, NAT Gateway IDs, and so on. Normally, you can look up this data using either a `dependency` block in Terragrunt or a `terraform_remote_state` data source in Terraform, but in some cases, the team that needs the VPC data does not have access to the code or Terraform state for the VPC module, perhaps because networking is managed by a separate team, maybe in a separate repo. @@ -40,7 +40,7 @@ This module attempts to match the output variables API of `vpc-app` exactly. module "vpc_app_lookup" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # OPTIONAL VARIABLES @@ -118,7 +118,7 @@ module "vpc_app_lookup" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.28.12" } inputs = { @@ -618,11 +618,11 @@ The name configured for VPC. diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-app-network-acls/vpc-app-network-acls.md b/docs/reference/modules/terraform-aws-vpc/vpc-app-network-acls/vpc-app-network-acls.md index 841852ab4..eefb998a9 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-app-network-acls/vpc-app-network-acls.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-app-network-acls/vpc-app-network-acls.md @@ -9,17 +9,17 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC-App Network ACLs Terraform Module -View Source +View Source Release Notes This Terraform Module adds a default set of [Network ACLs](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html) to a VPC created using the -[vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-app) module. The ACLs enforce the following security settings (based on [A Reference VPC +[vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-app) module. The ACLs enforce the following security settings (based on [A Reference VPC Architecture](https://www.whaletech.co/2014/10/02/reference-vpc-architecture.html)): * **Public subnet**: Allow all requests. @@ -93,7 +93,7 @@ module "network_acls" { module "vpc_app_network_acls" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -245,7 +245,7 @@ module "vpc_app_network_acls" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.28.12" } inputs = { @@ -757,11 +757,11 @@ Use this variable to ensure the Network ACL does not get created until the VPC i diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-app/vpc-app.md b/docs/reference/modules/terraform-aws-vpc/vpc-app/vpc-app.md index 8bdd1ed76..3763b84aa 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-app/vpc-app.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-app/vpc-app.md @@ -9,16 +9,16 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC-App Terraform Module -View Source +View Source Release Notes This Terraform Module launches a single VPC meant to house applications. By contrast, DevOps-related services such as -Jenkins or InfluxDB should be in a "mgmt" VPC. (See the [vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-mgmt) module.) +Jenkins or InfluxDB should be in a "mgmt" VPC. (See the [vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-mgmt) module.) ## Background @@ -78,7 +78,7 @@ nearly all use-cases, and is consistent with many examples and existing document ### Other VPC Core Concepts -Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. +Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. ## IPv6 @@ -118,7 +118,7 @@ module "vpc_app_ipv6_example" { module "vpc_app" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -190,9 +190,9 @@ module "vpc_app" { # Allows to filter list of Availability Zones based on their current state. # Can be either "available", "information", "impaired" or "unavailable". By - # default the list includes a complete set of Availability Zones to which the - # underlying AWS account has access, regardless of their state. - availability_zone_state = null + # default only available AZs are used, which prevents subnet creation failures + # in AZs that are impaired or offline. + availability_zone_state = "available" # DEPRECATED. The AWS Region where this VPC will exist. This variable is no # longer used and only kept around for backwards compatibility. We now @@ -652,7 +652,7 @@ module "vpc_app" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.28.12" } inputs = { @@ -727,9 +727,9 @@ inputs = { # Allows to filter list of Availability Zones based on their current state. # Can be either "available", "information", "impaired" or "unavailable". By - # default the list includes a complete set of Availability Zones to which the - # underlying AWS account has access, regardless of their state. - availability_zone_state = null + # default only available AZs are used, which prevents subnet creation failures + # in AZs that are impaired or offline. + availability_zone_state = "available" # DEPRECATED. The AWS Region where this VPC will exist. This variable is no # longer used and only kept around for backwards compatibility. We now @@ -1320,10 +1320,10 @@ List of specific Availability Zone IDs to use. If null (default), all availabili -Allows to filter list of Availability Zones based on their current state. Can be either 'available', 'information', 'impaired' or 'unavailable'. By default the list includes a complete set of Availability Zones to which the underlying AWS account has access, regardless of their state. +Allows to filter list of Availability Zones based on their current state. Can be either 'available', 'information', 'impaired' or 'unavailable'. By default only available AZs are used, which prevents subnet creation failures in AZs that are impaired or offline. - + @@ -2425,11 +2425,11 @@ A map of all transit subnets, with the subnet ID as the key, and all `aws-subnet diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder-rules/vpc-dns-forwarder-rules.md b/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder-rules/vpc-dns-forwarder-rules.md index d982c8dd3..dc63076f4 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder-rules/vpc-dns-forwarder-rules.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder-rules/vpc-dns-forwarder-rules.md @@ -9,23 +9,23 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC DNS Forwarder Rules Terraform Module -View Source +View Source Release Notes This Terraform Module creates [Route 53 Resolver Forwarding Rules](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-rules-managing.html) for a VPC that will -utilize Route 53 Resolver Endpoints created with the [vpc-dns-forwarder module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-dns-forwarder). These forwarding +utilize Route 53 Resolver Endpoints created with the [vpc-dns-forwarder module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-dns-forwarder). These forwarding rules, combined with Route 53 Resolvers, allow DNS queries for specific domains to be resolved by peered VPCs. ## How do you specify the hostnames that use the forwarder? By default, no DNS query will be routed through the Route 53 Resolvers created by the [vpc-dns-forwarder -module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-dns-forwarder). You need to create forwarding rules that specify which specific domains should be +module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-dns-forwarder). You need to create forwarding rules that specify which specific domains should be resolved through the Route 53 Resolvers so that they are resolved over the peering connection. You can use this module to construct the forwarding rules. @@ -72,7 +72,7 @@ forwarder rule, it will match any domain that ends with `.local` (note the dot), module "vpc_dns_forwarder_rules" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -126,7 +126,7 @@ module "vpc_dns_forwarder_rules" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.28.12" } inputs = { @@ -179,11 +179,11 @@ inputs = { diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder/vpc-dns-forwarder.md b/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder/vpc-dns-forwarder.md index cee7d9b20..fb10d1295 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder/vpc-dns-forwarder.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-dns-forwarder/vpc-dns-forwarder.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC DNS Forwarder Terraform Module -View Source +View Source Release Notes @@ -47,7 +47,7 @@ private endpoints internal to the target VPC. By default, no DNS query will be routed through the Route 53 Resolvers created by this module. You need to create forwarding rules that specify which specific domains should be resolved through the Route 53 Resolvers created by this -module. You can use the [vpc-dns-forwarder-rules module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-dns-forwarder-rules) to construct the forwarding rules. +module. You can use the [vpc-dns-forwarder-rules module](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-dns-forwarder-rules) to construct the forwarding rules. ## Sample Usage @@ -62,7 +62,7 @@ module. You can use the [vpc-dns-forwarder-rules module](https://github.com/grun module "vpc_dns_forwarder" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -138,7 +138,7 @@ module "vpc_dns_forwarder" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.28.12" } inputs = { @@ -379,11 +379,11 @@ The secondary IP address of the DNS resolver in the origin VPC. This is the IP t diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-flow-logs/vpc-flow-logs.md b/docs/reference/modules/terraform-aws-vpc/vpc-flow-logs/vpc-flow-logs.md index 933cea5cf..b2dbc849d 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-flow-logs/vpc-flow-logs.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-flow-logs/vpc-flow-logs.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC Flow Logs Terraform Module -View Source +View Source Release Notes @@ -86,7 +86,7 @@ TODO: Publish flow logs to an S3 bucket or CloudWatch Logs group in another acco module "vpc_flow_logs" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # OPTIONAL VARIABLES @@ -236,7 +236,7 @@ module "vpc_flow_logs" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.28.12" } inputs = { @@ -800,11 +800,11 @@ The name of the S3 bucket where flow logs are published. diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-interface-endpoint/vpc-interface-endpoint.md b/docs/reference/modules/terraform-aws-vpc/vpc-interface-endpoint/vpc-interface-endpoint.md index 71532249a..52ff0f27e 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-interface-endpoint/vpc-interface-endpoint.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-interface-endpoint/vpc-interface-endpoint.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # Interface VPC Endpoint -View Source +View Source Release Notes @@ -193,7 +193,7 @@ Not specifying a rule allows all traffic. ## Other VPC Core Concepts -Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) like subnets and NAT Gateways. +Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) like subnets and NAT Gateways. ## Sample Usage @@ -208,7 +208,7 @@ Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform- module "vpc_interface_endpoint" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -2154,7 +2154,7 @@ module "vpc_interface_endpoint" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.28.12" } inputs = { @@ -8904,11 +8904,11 @@ If you have private dns enabled, then your streaming calls would automatically g diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-mgmt-network-acls/vpc-mgmt-network-acls.md b/docs/reference/modules/terraform-aws-vpc/vpc-mgmt-network-acls/vpc-mgmt-network-acls.md index 172009633..2973f0d70 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-mgmt-network-acls/vpc-mgmt-network-acls.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-mgmt-network-acls/vpc-mgmt-network-acls.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # \[DEPRECATED] VPC-Mgmt Network ACLs Terraform Module -View Source +View Source Release Notes @@ -28,7 +28,7 @@ aware that, in a future release, once we feel the new functionality in `vpc-app` This Terraform Module adds a default set of [Network ACLs](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_ACLs.html) to a VPC created using the -[vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-mgmt) module. The ACLs enforce the following security settings (based on [A Reference VPC +[vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-mgmt) module. The ACLs enforce the following security settings (based on [A Reference VPC Architecture](https://www.whaletech.co/2014/10/02/reference-vpc-architecture.html)): * **Public subnet**: Allow all requests. @@ -63,7 +63,7 @@ EC2 instance), a network ACL controls what inbound and outbound traffic is allow module "vpc_mgmt_network_acls" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -142,7 +142,7 @@ module "vpc_mgmt_network_acls" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.28.12" } inputs = { @@ -344,11 +344,11 @@ The number to use for the first rule that is created by this module. All rules i diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-mgmt/vpc-mgmt.md b/docs/reference/modules/terraform-aws-vpc/vpc-mgmt/vpc-mgmt.md index 62d528fb7..2782320d9 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-mgmt/vpc-mgmt.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-mgmt/vpc-mgmt.md @@ -9,11 +9,11 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # \[DEPRECATED] VPC-Mgmt Terraform Module -View Source +View Source Release Notes @@ -27,7 +27,7 @@ aware that, in a future release, once we feel the new functionality in `vpc-app` `vpc-mgmt` entirely. This Terraform Module launches a single VPC meant to house DevOps and other management services. By contrast, the apps -that power your business should run in an "app" VPC. (See the [vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-app) module.) +that power your business should run in an "app" VPC. (See the [vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-app) module.) ## What's a VPC? @@ -65,7 +65,7 @@ To summarize: ## VPC Peering -Learn more about VPC Peering in the [vpc-peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-peering) module. +Learn more about VPC Peering in the [vpc-peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-peering) module. ## SSH Access via the Bastion Host @@ -79,7 +79,7 @@ examples](https://github.com/gruntwork-io/terraform-aws-server/tree/main/example ## Other VPC Core Concepts -Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. +Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. ## Sample Usage @@ -94,7 +94,7 @@ Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform- module "vpc_mgmt" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -140,9 +140,9 @@ module "vpc_mgmt" { # Allows to filter list of Availability Zones based on their current state. # Can be either "available", "information", "impaired" or "unavailable". By - # default the list includes a complete set of Availability Zones to which the - # underlying AWS account has access, regardless of their state. - availability_zone_state = null + # default only available AZs are used, which prevents subnet creation failures + # in AZs that are impaired or offline. + availability_zone_state = "available" # DEPRECATED. The AWS Region where this VPC will exist. This variable is no # longer used and only kept around for backwards compatibility. We now @@ -313,7 +313,7 @@ module "vpc_mgmt" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.28.12" } inputs = { @@ -362,9 +362,9 @@ inputs = { # Allows to filter list of Availability Zones based on their current state. # Can be either "available", "information", "impaired" or "unavailable". By - # default the list includes a complete set of Availability Zones to which the - # underlying AWS account has access, regardless of their state. - availability_zone_state = null + # default only available AZs are used, which prevents subnet creation failures + # in AZs that are impaired or offline. + availability_zone_state = "available" # DEPRECATED. The AWS Region where this VPC will exist. This variable is no # longer used and only kept around for backwards compatibility. We now @@ -603,10 +603,10 @@ List of excluded Availability Zone names. -Allows to filter list of Availability Zones based on their current state. Can be either 'available', 'information', 'impaired' or 'unavailable'. By default the list includes a complete set of Availability Zones to which the underlying AWS account has access, regardless of their state. +Allows to filter list of Availability Zones based on their current state. Can be either 'available', 'information', 'impaired' or 'unavailable'. By default only available AZs are used, which prevents subnet creation failures in AZs that are impaired or offline. - + @@ -1052,11 +1052,11 @@ A null_resource that indicates that the VPC is ready, including all of its resou diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-accepter/vpc-peering-cross-accounts-accepter.md b/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-accepter/vpc-peering-cross-accounts-accepter.md index f385be55d..a5f4d9ef7 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-accepter/vpc-peering-cross-accounts-accepter.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-accepter/vpc-peering-cross-accounts-accepter.md @@ -9,13 +9,13 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # vpc-peering-cross-accounts-accepter -View Source +View Source -Release Notes +Release Notes This module manages the accepter's side of the VPC Peering Connection between two differents accounts that you control. @@ -78,15 +78,12 @@ No modules. module "vpc_peering_cross_accounts_accepter" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES # ---------------------------------------------------------------------------------------------------- - # The VPC CIDR of the requester VPC. - requester_vpc_cidr = - # List of route tables to add routes to. route_tables = @@ -101,6 +98,15 @@ module "vpc_peering_cross_accounts_accepter" { # when queried from instances in the peer VPC. dns_resolution = false + # DEPRECATED: Use requester_vpc_cidrs instead. The VPC CIDR of the requester + # VPC. + requester_vpc_cidr = null + + # A list of CIDR blocks of the requester VPC. When the requester VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to requester_vpc_cidr. + requester_vpc_cidrs = [] + # The timeout for the creation of the Route Tables. It defines how long to # wait for a route table to be created before considering the operation # failed. Ref: @@ -136,7 +142,7 @@ module "vpc_peering_cross_accounts_accepter" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.28.12" } inputs = { @@ -145,9 +151,6 @@ inputs = { # REQUIRED VARIABLES # ---------------------------------------------------------------------------------------------------- - # The VPC CIDR of the requester VPC. - requester_vpc_cidr = - # List of route tables to add routes to. route_tables = @@ -162,6 +165,15 @@ inputs = { # when queried from instances in the peer VPC. dns_resolution = false + # DEPRECATED: Use requester_vpc_cidrs instead. The VPC CIDR of the requester + # VPC. + requester_vpc_cidr = null + + # A list of CIDR blocks of the requester VPC. When the requester VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to requester_vpc_cidr. + requester_vpc_cidrs = [] + # The timeout for the creation of the Route Tables. It defines how long to # wait for a route table to be created before considering the operation # failed. Ref: @@ -200,14 +212,6 @@ inputs = { ### Required - - - -The VPC CIDR of the requester VPC. - - - - @@ -235,6 +239,24 @@ Allow a local VPC to resolve public DNS hostnames to private IP addresses when q + + + +DEPRECATED: Use requester_vpc_cidrs instead. The VPC CIDR of the requester VPC. + + + + + + + + +A list of CIDR blocks of the requester VPC. When the requester VPC has multiple CIDR blocks, all of them should be listed here so that routes are created for each. If not set, falls back to requester_vpc_cidr. + + + + + @@ -296,11 +318,11 @@ Peering connection ID. diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-requester/vpc-peering-cross-accounts-requester.md b/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-requester/vpc-peering-cross-accounts-requester.md index 37656e76e..a0b408ba9 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-requester/vpc-peering-cross-accounts-requester.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-peering-cross-accounts-requester/vpc-peering-cross-accounts-requester.md @@ -9,13 +9,13 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # vpc-peering-cross-accounts-requester -View Source +View Source -Release Notes +Release Notes This module manages the requester's side of the VPC Peering Connection between two differents accounts that you control. @@ -73,7 +73,7 @@ No modules. module "vpc_peering_cross_accounts_requester" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -85,9 +85,6 @@ module "vpc_peering_cross_accounts_requester" { # The region of the accepter VPC. accepter_region = - # The VPC CIDR of the accepter VPC. - accepter_vpc_cidr = - # The ID of the accepter VPC. accepter_vpc_id = @@ -101,6 +98,15 @@ module "vpc_peering_cross_accounts_requester" { # OPTIONAL VARIABLES # ---------------------------------------------------------------------------------------------------- + # DEPRECATED: Use accepter_vpc_cidrs instead. The VPC CIDR of the accepter + # VPC. + accepter_vpc_cidr = null + + # A list of CIDR blocks of the accepter VPC. When the accepter VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to accepter_vpc_cidr. + accepter_vpc_cidrs = [] + # Allow a local VPC to resolve public DNS hostnames to private IP addresses # when queried from instances in the peer VPC. allow_remote_vpc_dns_resolution = false @@ -131,7 +137,7 @@ module "vpc_peering_cross_accounts_requester" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.28.12" } inputs = { @@ -146,9 +152,6 @@ inputs = { # The region of the accepter VPC. accepter_region = - # The VPC CIDR of the accepter VPC. - accepter_vpc_cidr = - # The ID of the accepter VPC. accepter_vpc_id = @@ -162,6 +165,15 @@ inputs = { # OPTIONAL VARIABLES # ---------------------------------------------------------------------------------------------------- + # DEPRECATED: Use accepter_vpc_cidrs instead. The VPC CIDR of the accepter + # VPC. + accepter_vpc_cidr = null + + # A list of CIDR blocks of the accepter VPC. When the accepter VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to accepter_vpc_cidr. + accepter_vpc_cidrs = [] + # Allow a local VPC to resolve public DNS hostnames to private IP addresses # when queried from instances in the peer VPC. allow_remote_vpc_dns_resolution = false @@ -211,14 +223,6 @@ The region of the accepter VPC. - - - -The VPC CIDR of the accepter VPC. - - - - @@ -245,6 +249,24 @@ The VPC ID. ### Optional + + + +DEPRECATED: Use accepter_vpc_cidrs instead. The VPC CIDR of the accepter VPC. + + + + + + + + +A list of CIDR blocks of the accepter VPC. When the accepter VPC has multiple CIDR blocks, all of them should be listed here so that routes are created for each. If not set, falls back to accepter_vpc_cidr. + + + + + @@ -298,11 +320,11 @@ Peering connection ID. diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-peering-external/vpc-peering-external.md b/docs/reference/modules/terraform-aws-vpc/vpc-peering-external/vpc-peering-external.md index a2d2f1157..ee1e6845f 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-peering-external/vpc-peering-external.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-peering-external/vpc-peering-external.md @@ -9,13 +9,13 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC Peering For External VPCs Module -View Source +View Source -Release Notes +Release Notes This Terraform Module creates route table entries for a [VPC Peering Connection](http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/Welcome.html) between one of your internal VPCs (e.g. @@ -87,7 +87,7 @@ EC2 instance), a network ACL controls what inbound and outbound traffic is allow module "vpc_peering_external" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -110,9 +110,6 @@ module "vpc_peering_external" { # rules. egress_starting_rule_number = - # The IP address range of the external VPC in CIDR notation (e.g. 10.0.2.0/16) - external_vpc_cidr_block = - # The starting rule number for adding the global DENY ingress rules to the # Network ACLs in var.all_network_acl_ids. This should be a high number # (always higher than var.ingress_starting_rule_number) to ensure rules that @@ -136,23 +133,6 @@ module "vpc_peering_external" { # there is no way to know in Terraform if yours already has one. network_acl_ids_with_external_vpc_access = - # The number of IDs in var.all_network_acl_ids. We should be able to compute - # this automatically, but due to a Terraform limitation, we can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_all_network_acl_ids = - - # The number of route table IDs in var.internal_vpc_route_table_ids. We should - # be able to compute this automatically, but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_internal_vpc_route_tables = - - # The number of IDs in var.network_acl_ids_with_external_vpc_access. We should - # be able to compute this automatically, but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_network_acl_ids_with_external_vpc_access = - # Allow communication between the internal and external VPC on ports between # var.outbound_from_port and var.outbound_to_port. outbound_from_port = @@ -187,6 +167,27 @@ module "vpc_peering_external" { # and var.ephemeral_to_port, inclusive, from var.external_vpc_cidr_block ephemeral_to_port = 65535 + # DEPRECATED: Use external_vpc_cidr_blocks instead. The IP address range of + # the external VPC in CIDR notation. + external_vpc_cidr_block = null + + # A list of IP address ranges of the external VPC in CIDR notation. When the + # external VPC has multiple CIDR blocks, all of them should be listed here. If + # not set, falls back to external_vpc_cidr_block. + external_vpc_cidr_blocks = [] + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_all_network_acl_ids = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_internal_vpc_route_tables = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_network_acl_ids_with_external_vpc_access = null + } @@ -202,7 +203,7 @@ module "vpc_peering_external" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.28.12" } inputs = { @@ -228,9 +229,6 @@ inputs = { # rules. egress_starting_rule_number = - # The IP address range of the external VPC in CIDR notation (e.g. 10.0.2.0/16) - external_vpc_cidr_block = - # The starting rule number for adding the global DENY ingress rules to the # Network ACLs in var.all_network_acl_ids. This should be a high number # (always higher than var.ingress_starting_rule_number) to ensure rules that @@ -254,23 +252,6 @@ inputs = { # there is no way to know in Terraform if yours already has one. network_acl_ids_with_external_vpc_access = - # The number of IDs in var.all_network_acl_ids. We should be able to compute - # this automatically, but due to a Terraform limitation, we can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_all_network_acl_ids = - - # The number of route table IDs in var.internal_vpc_route_table_ids. We should - # be able to compute this automatically, but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_internal_vpc_route_tables = - - # The number of IDs in var.network_acl_ids_with_external_vpc_access. We should - # be able to compute this automatically, but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_network_acl_ids_with_external_vpc_access = - # Allow communication between the internal and external VPC on ports between # var.outbound_from_port and var.outbound_to_port. outbound_from_port = @@ -305,6 +286,27 @@ inputs = { # and var.ephemeral_to_port, inclusive, from var.external_vpc_cidr_block ephemeral_to_port = 65535 + # DEPRECATED: Use external_vpc_cidr_blocks instead. The IP address range of + # the external VPC in CIDR notation. + external_vpc_cidr_block = null + + # A list of IP address ranges of the external VPC in CIDR notation. When the + # external VPC has multiple CIDR blocks, all of them should be listed here. If + # not set, falls back to external_vpc_cidr_block. + external_vpc_cidr_blocks = [] + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_all_network_acl_ids = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_internal_vpc_route_tables = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_network_acl_ids_with_external_vpc_access = null + } @@ -316,11 +318,11 @@ inputs = { diff --git a/docs/reference/modules/terraform-aws-vpc/vpc-peering/vpc-peering.md b/docs/reference/modules/terraform-aws-vpc/vpc-peering/vpc-peering.md index 2243aa086..28058f842 100644 --- a/docs/reference/modules/terraform-aws-vpc/vpc-peering/vpc-peering.md +++ b/docs/reference/modules/terraform-aws-vpc/vpc-peering/vpc-peering.md @@ -9,19 +9,19 @@ import VersionBadge from '../../../../../src/components/VersionBadge.tsx'; import { HclListItem, HclListItemDescription, HclListItemTypeDetails, HclListItemDefaultValue, HclGeneralListItem } from '../../../../../src/components/HclListItem.tsx'; import { ModuleUsage } from "../../../../../src/components/ModuleUsage"; - + # VPC-Peering Terraform Module -View Source +View Source -Release Notes +Release Notes This Terraform Module creates [VPC Peering Connections](http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/Welcome.html) between VPCs. Normally, VPCs are completely isolated from each other, but sometimes, you want to allow traffic to flow between them, such as allowing -DevOps tools running in a Mgmt VPC (see [vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-mgmt)) to talk to apps running in a Stage or Prod VPC (see -[vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.11/modules/vpc-app)). This module can create peering connections and route table entries that make this sort of +DevOps tools running in a Mgmt VPC (see [vpc-mgmt](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-mgmt)) to talk to apps running in a Stage or Prod VPC (see +[vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.28.12/modules/vpc-app)). This module can create peering connections and route table entries that make this sort of cross-VPC communication possible. ## What's a VPC? @@ -57,7 +57,7 @@ and production, someone in staging *cannot* access production. module "vpc_peering" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.28.12" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -66,9 +66,6 @@ module "vpc_peering" { # The ID of the AWS account that should own the peering connection. aws_account_id = - # The CIDR block (e.g. 10.0.200.0/24) associated with the destination VPC. - destination_vpc_cidr_block = - # The ID of the VPC which is the destination of the VPC peering connection. destination_vpc_id = @@ -79,20 +76,6 @@ module "vpc_peering" { # added pointing to origin VPC. destination_vpc_route_table_ids = - # The number of route table ids in var.destination_vpc_route_table_ids. This - # should be computable, but due to a but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_destination_vpc_route_tables = - - # The number of route table ids in var.origin_vpc_route_table_ids. This should - # be computable, but due to a but due to a Terraform limitation, we can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_origin_vpc_route_tables = - - # The CIDR block (e.g. 10.0.100.0/24) associated with the origin VPC. - origin_vpc_cidr_block = - # The ID of the VPC which is the origin of the VPC peering connection. origin_vpc_id = @@ -126,6 +109,32 @@ module "vpc_peering" { # variable. custom_tags = {} + # DEPRECATED: Use destination_vpc_cidr_blocks instead. The CIDR block + # associated with the destination VPC. + destination_vpc_cidr_block = null + + # A list of CIDR blocks associated with the destination VPC. When a VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to destination_vpc_cidr_block. + destination_vpc_cidr_blocks = [] + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_destination_vpc_route_tables = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_origin_vpc_route_tables = null + + # DEPRECATED: Use origin_vpc_cidr_blocks instead. The CIDR block associated + # with the origin VPC. + origin_vpc_cidr_block = null + + # A list of CIDR blocks associated with the origin VPC. When a VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to origin_vpc_cidr_block. + origin_vpc_cidr_blocks = [] + } @@ -141,7 +150,7 @@ module "vpc_peering" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.28.11" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.28.12" } inputs = { @@ -153,9 +162,6 @@ inputs = { # The ID of the AWS account that should own the peering connection. aws_account_id = - # The CIDR block (e.g. 10.0.200.0/24) associated with the destination VPC. - destination_vpc_cidr_block = - # The ID of the VPC which is the destination of the VPC peering connection. destination_vpc_id = @@ -166,20 +172,6 @@ inputs = { # added pointing to origin VPC. destination_vpc_route_table_ids = - # The number of route table ids in var.destination_vpc_route_table_ids. This - # should be computable, but due to a but due to a Terraform limitation, we - # can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_destination_vpc_route_tables = - - # The number of route table ids in var.origin_vpc_route_table_ids. This should - # be computable, but due to a but due to a Terraform limitation, we can't: - # https://github.com/hashicorp/terraform/issues/14677#issuecomment-302772685 - num_origin_vpc_route_tables = - - # The CIDR block (e.g. 10.0.100.0/24) associated with the origin VPC. - origin_vpc_cidr_block = - # The ID of the VPC which is the origin of the VPC peering connection. origin_vpc_id = @@ -213,6 +205,32 @@ inputs = { # variable. custom_tags = {} + # DEPRECATED: Use destination_vpc_cidr_blocks instead. The CIDR block + # associated with the destination VPC. + destination_vpc_cidr_block = null + + # A list of CIDR blocks associated with the destination VPC. When a VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to destination_vpc_cidr_block. + destination_vpc_cidr_blocks = [] + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_destination_vpc_route_tables = null + + # DEPRECATED: No longer needed as the count is computed automatically. Kept + # for backwards compatibility. + num_origin_vpc_route_tables = null + + # DEPRECATED: Use origin_vpc_cidr_blocks instead. The CIDR block associated + # with the origin VPC. + origin_vpc_cidr_block = null + + # A list of CIDR blocks associated with the origin VPC. When a VPC has + # multiple CIDR blocks, all of them should be listed here so that routes are + # created for each. If not set, falls back to origin_vpc_cidr_block. + origin_vpc_cidr_blocks = [] + } @@ -221,14 +239,186 @@ inputs = { + + + +## Reference + + + + +### Required + + + + +The ID of the AWS account that should own the peering connection. + + + + + + + +The ID of the VPC which is the destination of the VPC peering connection. + + + + + + + +The name of the VPC which is the destination of the VPC peering connection. + + + + + + + +A list of IDs of route tables in the destination VPC that should have routes added pointing to origin VPC. + + + + + + + +The ID of the VPC which is the origin of the VPC peering connection. + + + + + + + +The name of the VPC which is the origin of the VPC peering connection. + + + + + + + +A list of IDs of route tables in the origin VPC that should have routes added pointing to destination VPC. + + + + +### Optional + + + + +A boolean parameter to enable or disable DNS resolution on both accepter and requester side of the connection peering. + + + + + + + + +A boolean parameter to auto-accept the VPC peering connection. + + + + + + + + +Set to false to have this module create no resources. This weird parameter exists solely because Terraform does not support conditional modules. Therefore, this is a hack to allow you to conditionally decide if the VPC Peering function and other resources should be created or not. + + + + + + + + +A map of tags to apply to the VPC Peering Connection. The key is the tag name and the value is the tag value. Note that the tag 'Name' is automatically added by this module but may be optionally overwritten by this variable. + + + + + + + + +DEPRECATED: Use destination_vpc_cidr_blocks instead. The CIDR block associated with the destination VPC. + + + + + + + + +A list of CIDR blocks associated with the destination VPC. When a VPC has multiple CIDR blocks, all of them should be listed here so that routes are created for each. If not set, falls back to destination_vpc_cidr_block. + + + + + + + + +DEPRECATED: No longer needed as the count is computed automatically. Kept for backwards compatibility. + + + + + + + + +DEPRECATED: No longer needed as the count is computed automatically. Kept for backwards compatibility. + + + + + + + + +DEPRECATED: Use origin_vpc_cidr_blocks instead. The CIDR block associated with the origin VPC. + + + + + + + + +A list of CIDR blocks associated with the origin VPC. When a VPC has multiple CIDR blocks, all of them should be listed here so that routes are created for each. If not set, falls back to origin_vpc_cidr_block. + + + + + + + + + + + +VPC Peering connection object + + + + + + +