From 575bdd646f206c9cc66f0064d798b76825eae94b Mon Sep 17 00:00:00 2001 From: "docs-sourcer[bot]" <99042413+docs-sourcer[bot]@users.noreply.github.com> Date: Thu, 7 Nov 2024 21:58:33 +0000 Subject: [PATCH] Updated with the [latest changes](https://github.com/gruntwork-io/terraform-aws-vpc/releases/tag/v0.26.27) from the `terraform-aws-vpc@v0.26.27` source branch. --- .../network-acl-inbound.md | 18 +++--- .../network-acl-outbound.md | 18 +++--- .../port-range-calculator.md | 16 ++--- .../modules/terraform-aws-vpc/route/route.md | 24 ++++---- .../transit-gateway-attachment.md | 26 ++++----- ...sit-gateway-peering-attachment-accepter.md | 26 ++++----- .../transit-gateway-peering-attachment.md | 26 ++++----- .../transit-gateway-route.md | 26 ++++----- .../transit-gateway/transit-gateway.md | 28 ++++----- .../vpc-app-lookup/vpc-app-lookup.md | 18 +++--- .../vpc-app-network-acls.md | 18 +++--- .../terraform-aws-vpc/vpc-app/vpc-app.md | 58 +++++++++++++------ .../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 | 22 +++---- .../vpc-peering-cross-accounts-accepter.md | 18 +++--- .../vpc-peering-cross-accounts-requester.md | 18 +++--- .../vpc-peering-external.md | 16 ++--- .../vpc-peering/vpc-peering.md | 20 +++---- 22 files changed, 254 insertions(+), 232 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 1f7a3bb5c3..25339e9148 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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-inbound?ref=v0.26.27" } 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 dc2d698f57..dba385e549 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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/network-acl-outbound?ref=v0.26.27" } 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 4eab655db2..3800df9bb3 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/port-range-calculator?ref=v0.26.27" } 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/route/route.md b/docs/reference/modules/terraform-aws-vpc/route/route.md index 6a4e114c17..1d1fce168d 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.26.26/examples/route/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/examples/route/). ## What is a route? @@ -44,14 +44,14 @@ Routes can be either dynamic or static. Dynamic routes are learned by the route | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -104,7 +104,7 @@ No modules. module "route" { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -193,7 +193,7 @@ module "route" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/route?ref=v0.26.27" } inputs = { @@ -448,11 +448,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 b3f03fbd9e..89ae7246d7 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.26/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.27/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.26/examples/transit-gateway-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/examples/transit-gateway-attachment/). @@ -37,14 +37,14 @@ For usage examples, check out the [examples folder](https://github.com/gruntwork | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-attachment?ref=v0.26.27" } 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 8b89deb11d..6f8e70e49a 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.26/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.27/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.26/examples/transit-gateway-peering-attachment). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/examples/transit-gateway-peering-attachment). @@ -33,14 +33,14 @@ For usage examples, check out the [examples folder](https://github.com/gruntwork | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment-accepter?ref=v0.26.27" } 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 bddb363083..987a09858e 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.26/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.27/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.26/examples/transit-gateway-peering-attachment/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/examples/transit-gateway-peering-attachment/). @@ -35,14 +35,14 @@ For usage examples, check out the [examples folder](https://github.com/gruntwork | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-peering-attachment?ref=v0.26.27" } 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 e895d0f092..3e0a1d5525 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.26/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.27/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.26.26/examples/transit-gateway-route/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/examples/transit-gateway-route/). @@ -38,14 +38,14 @@ For usage examples, check out the [examples folder](https://github.com/gruntwork | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway-route?ref=v0.26.27" } inputs = { @@ -227,11 +227,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 c3aaf1000a..e75e6e5663 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.26/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.27/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.26/examples/transit-gateway/). +For usage examples, check out the [examples folder](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/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.26/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.26/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.26/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.27/modules/transit-gateway-peering-attachment/) & [transit-gateway-peering-attachment-accepter](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/modules/transit-gateway-peering-attachment-accepter/) modules. See [VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/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 @@ -75,14 +75,14 @@ What follows are the steps required to configure Transit Gateway resources withi | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | -| [aws](#requirement_aws) | >= 4.5.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | +| [aws](#requirement_aws) | >= 4.5.0 | ## Providers | Name | Version | |------|---------| -| [aws](#provider_aws) | >= 4.5.0 | +| [aws](#provider_aws) | >= 4.5.0 | ## Modules @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/transit-gateway?ref=v0.26.27" } inputs = { @@ -426,11 +426,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 9afbb654b7..d587cb5780 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.26.26/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.26.27/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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-lookup?ref=v0.26.27" } inputs = { @@ -619,11 +619,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 658bea490a..d2fca67923 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.26/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.27/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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -241,7 +241,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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app-network-acls?ref=v0.26.27" } inputs = { @@ -741,11 +741,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 c32f15fe19..8e567894be 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 @@ -1,5 +1,5 @@ --- -title: "IPv6" +title: "VPC-App Terraform Module" hide_title: true --- @@ -9,22 +9,27 @@ 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 +# VPC-App Terraform Module -View Source +View Source Release Notes -## What's a VPC? +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.26.27/modules/vpc-mgmt) module.) + +## Background + +### What's a VPC? A [VPC](https://aws.amazon.com/vpc/) or Virtual Private Cloud is a logically isolated section of your AWS cloud. Each VPC defines a virtual network within which you run your AWS resources, as well as rules for what can go in and out of that network. This includes subnets, route tables that tell those subnets how to route inbound and outbound traffic, security groups, access controls lists for the network (NACLs), and any other network components such as VPN connections. -## Subnet Tiers +### Subnet Tiers This VPC defines four "tiers" of subnets: @@ -41,7 +46,7 @@ This VPC defines four "tiers" of subnets: dedicated for the transit of network traffic. It should be utilized as the attachment point for transit gateways, network appliances, VPN connections, and Direct Connect connections. -## VPC Architecture +### VPC Architecture The four-tier VPC is inspired by the VPC Architecture described by Ben Whaley in his blog post [A Reference VPC Architecture](https://www.whaletech.co/2014/10/02/reference-vpc-architecture.html). That blog post proposed the @@ -67,21 +72,23 @@ CIDR math quite straightforward. If using the 10.0.0.0/8 [RFC1918](http://www.fa this allows for 256 VPCs (10.0.0.0/16-10.255.255.255/16) with 65,534 IP addresses per VPC. This should be sufficient for nearly all use-cases, and is consistent with many examples and existing documentation found elsewhere. -## Gotchas +### Gotchas * If the `num_availability_zones` variable in the mgmt VPC and the `num_availability_zones` variable in the app VPC don't match, there are problems with the routes that are created between the two VPCs as part of setting up VPC Peering. If your use case requires different numbers of Availability Zones for each of these VPCs, please let us know and we'll investigate further! -## Other VPC Core Concepts +### Other VPC Core Concepts + +Learn about [Other VPC Core Concepts](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/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.26/modules//_docs/vpc-core-concepts.md) like subnets, NAT Gateways, and VPC Endpoints. +## IPv6 -## IPv6 Design +### IPv6 Design ![IPv6 Topology](/img/reference/modules/terraform-aws-vpc/vpc-app/_dual_stack_vpc.png) For more IPv6 information, please see the following documentation from AWS - [IPv6 on AWS](https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/IPv6-on-AWS.html) -## Simple IPv6 Assigned from AWS Example +### Simple IPv6 Assigned from AWS Example The following example assigns your VPC a CIDR block from AWS and assigns an IPv6 CIDR block to each public subnet. @@ -111,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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -199,6 +206,9 @@ module "vpc_app" { # routed from other VPC hosting the IGW. create_igw = true + # Flag that controls attachment of secondary EIP to NAT gateway. + create_nat_secondary_eip = false + # If set to false, this module will NOT create the private app subnet tier. create_private_app_subnets = true @@ -591,7 +601,7 @@ module "vpc_app" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-app?ref=v0.26.27" } inputs = { @@ -682,6 +692,9 @@ inputs = { # routed from other VPC hosting the IGW. create_igw = true + # Flag that controls attachment of secondary EIP to NAT gateway. + create_nat_secondary_eip = false + # If set to false, this module will NOT create the private app subnet tier. create_private_app_subnets = true @@ -1220,6 +1233,15 @@ If the VPC will create an Internet Gateway. There are use cases when the VPC is + + + +Flag that controls attachment of secondary EIP to NAT gateway. + + + + + @@ -2161,11 +2183,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 9ab706c29b..4ae0b2accf 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.26/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.27/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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder-rules?ref=v0.26.27" } 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 45a5b0777f..30d212a378 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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-dns-forwarder?ref=v0.26.27" } 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 b6bf6a7bac..982081cb30 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-flow-logs?ref=v0.26.27" } inputs = { @@ -801,11 +801,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 15cac64d3f..1cf5e1a74f 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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -2049,7 +2049,7 @@ module "vpc_interface_endpoint" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-interface-endpoint?ref=v0.26.27" } inputs = { @@ -8437,11 +8437,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 d76d7cc4c5..0aeb6d59d5 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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt-network-acls?ref=v0.26.27" } 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 cf136e7312..cb6a15205c 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.26/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.27/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.26/modules/vpc-peering) module. +Learn more about VPC Peering in the [vpc-peering](https://github.com/gruntwork-io/terraform-aws-vpc/tree/v0.26.27/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.26/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # REQUIRED VARIABLES @@ -313,7 +313,7 @@ module "vpc_mgmt" { # ------------------------------------------------------------------------------------------------------ terraform { - source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-mgmt?ref=v0.26.27" } inputs = { @@ -1053,11 +1053,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 d00c5b21b0..9ce66cecc1 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 @@ -23,7 +23,7 @@ This module manages the accepter's side of the VPC Peering Connection between tw | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | ## Providers @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-accepter?ref=v0.26.27" } 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 d946491a7c..758584ddb8 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 @@ -23,7 +23,7 @@ This module manages the requester's side of the VPC Peering Connection between t | Name | Version | |------|---------| -| [terraform](#requirement_terraform) | >= 1.0.0 | +| [terraform](#requirement_terraform) | >= 1.0.0 | ## Providers @@ -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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-cross-accounts-requester?ref=v0.26.27" } 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 97f7850599..cef5582902 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering-external?ref=v0.26.27" } 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 d4ede4f488..c8c7088453 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.26/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.26/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.27/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.27/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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.26.27" # ---------------------------------------------------------------------------------------------------- # 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.26" + source = "git::git@github.com:gruntwork-io/terraform-aws-vpc.git//modules/vpc-peering?ref=v0.26.27" } inputs = { @@ -225,11 +225,11 @@ inputs = {