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 c04bfb9ca8..841d75a3b9 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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.26.5" } inputs = { @@ -221,11 +221,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 763685a34e..cf11056682 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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.26.5" } inputs = { @@ -221,11 +221,11 @@ inputs = { 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 a8f9eb0613..ff490875d4 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.26.5" } inputs = { @@ -178,11 +178,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/transit-gateway-attachment/transit-gateway-attachment.md b/docs/reference/modules/terraform-aws-vpc/transit-gateway-attachment/transit-gateway-attachment.md index b319e07a5a..6fa6ac1698 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.26.4/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.26.5/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.26.4/examples/transit-gateway-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -156,7 +156,7 @@ module "transit_gateway_attachment" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.26.5" } inputs = { @@ -329,11 +329,11 @@ EC2 Transit Gateway Attachment identifier. 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 7995620501..c9adbf9021 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.26.4/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.26.5/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.26.4/examples/transit-gateway-peering-attachment). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.26.5" } inputs = { @@ -259,11 +259,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 5950a592e2..21db1c24b3 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.26.4/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.26.5/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.26.4/examples/transit-gateway-peering-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.26.5" } inputs = { @@ -261,11 +261,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 778d8ca8c6..e80834bc95 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.26.4/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.26.5/modules//_docs/vpc-core-concepts.md) for more information on the core networking components and topologies. ## What is a Transit Gateway Route? @@ -27,7 +27,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.26.4/examples/transit-gateway-route/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/examples/transit-gateway-route/). @@ -84,7 +84,7 @@ No modules. module "transit_gateway_route" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -124,7 +124,7 @@ module "transit_gateway_route" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.5" } inputs = { @@ -224,11 +224,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 4b4a02b06e..7d873bd78e 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.26.4/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.26.5/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.26.4/examples/transit-gateway/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.4/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.4/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.26.5/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -201,7 +201,7 @@ module "transit_gateway" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.26.5" } inputs = { @@ -402,11 +402,11 @@ Transit Gateway identifier. 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 a72e771645..0bb68a5e2b 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.26.4/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.26.5/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. @@ -92,7 +92,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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -211,7 +211,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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.26.5" } inputs = { @@ -625,11 +625,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 ffeeaaa00c..40948d1d91 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,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"; - + # IPv6 -View Source +View Source Release Notes @@ -55,8 +55,8 @@ To summarize: * In a given subnet tier, there are usually three or four actual subnets, one for each Availability Zone. * Therefore, if we created a single VPC in the `us-west-2` region, which has Availability Zones `us-west-2a`,`us-west-2b`, and `us-west-2c`, each subnet tier would have three subnets (one per Availability Zone) for a total of 9 subnets in all. -* The only way to reach this VPC is from the public Internet via a publicly exposed sevice, or via the [mgmt VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.4/modules/vpc-mgmt), - which uses [VPC Peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.4/modules/vpc-peering) to make this VPC accessible from the mgmt VPC. +* The only way to reach this VPC is from the public Internet via a publicly exposed sevice, or via the [mgmt VPC](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/modules/vpc-mgmt), + which uses [VPC Peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/modules/vpc-peering) to make this VPC accessible from the mgmt VPC. * Philosophically, everything in a VPC should be isolated from all resources in any other VPC. In particular, we want to ensure that our stage environment is completely independent from prod. This architecture helps to reinforce that. @@ -71,7 +71,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.26.4/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.26.5/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. ## IPv6 Design @@ -109,7 +109,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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -500,7 +500,7 @@ module "vpc_app" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.5" } inputs = { @@ -1736,11 +1736,11 @@ A map of all public subnets, with the subnet name as the key, and all `aws-subne 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 15c5c41421..97d83d898f 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.26.4/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.26.5/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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.26.5" } inputs = { @@ -180,11 +180,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 d93c17f243..2642dfb7f5 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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.26.5" } inputs = { @@ -380,11 +380,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 67550c6184..d60e8e5abc 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # OPTIONAL VARIABLES @@ -232,7 +232,7 @@ module "vpc_flow_logs" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.26.5" } inputs = { @@ -784,11 +784,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 b0ac4c4c4c..66f27e51fa 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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -2023,7 +2023,7 @@ module "vpc_interface_endpoint" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.5" } inputs = { @@ -8331,11 +8331,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 8a44322131..bfb92f428d 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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.26.5" } inputs = { @@ -345,11 +345,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 5602bfae9a..7e25acae95 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.26.4/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.26.5/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.26.4/modules/vpc-peering) module. +Learn more about VPC Peering in the [vpc-peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.5/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.26.4/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -301,7 +301,7 @@ module "vpc_mgmt" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.5" } inputs = { @@ -1011,11 +1011,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 ca8a33f561..5874db7171 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,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-peering-cross-accounts-accepter -View Source +View Source Release Notes @@ -78,7 +78,7 @@ 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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -136,7 +136,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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.26.5" } inputs = { @@ -297,11 +297,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 71a25e99bb..a53d3c746f 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,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-peering-cross-accounts-requester -View Source +View Source Release Notes @@ -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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -131,7 +131,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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.26.5" } inputs = { @@ -299,11 +299,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 572819f107..4591e88408 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,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 Peering For External VPCs Module -View Source +View Source Release Notes @@ -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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -202,7 +202,7 @@ module "vpc_peering_external" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.26.5" } inputs = { @@ -317,11 +317,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 ba2c063475..4a6b1d3e97 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 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.26.4/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.26.4/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.26.5/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.26.5/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.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.26.5" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -141,7 +141,7 @@ module "vpc_peering" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.26.4" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.26.5" } inputs = { @@ -225,11 +225,11 @@ inputs = {