Git Product home page Git Product logo

terraform-aws-vpn-connection's Introduction

Project Banner

Latest ReleaseLast UpdatedSlack Community

Terraform module to provision a site-to-site VPN connection between a VPC and an on-premises network.

The module does the following:

  • Creates a Virtual Private Gateway (VPG) and attaches it to the VPC
  • Creates a Customer Gateway (CGW) pointing to the provided IP address of the Internet-routable external interface on the on-premises network
  • Creates a Site-to-Site Virtual Private Network (VPN) connection and assigns it to the VPG and CGW
  • Requests automatic route propagation between the VPG and the provided route tables in the VPC
  • If the VPN connection is configured to use static routes, provisions a static route between the VPN connection and the CGW

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform
Example of running atmos to manage infrastructure from our Quick Start tutorial.

Usage

  module "vpn_connection" {
    source = "cloudposse/vpn-connection/aws"
    # Cloud Posse recommends pinning every module to a specific version
    # version = "x.x.x"
    namespace                                 = "eg"
    stage                                     = "dev"
    name                                      = "test"
    vpc_id                                    = "vpc-xxxxxxxx"
    vpn_gateway_amazon_side_asn               = 64512
    customer_gateway_bgp_asn                  = 65000
    customer_gateway_ip_address               = "172.0.0.1"
    route_table_ids                           = ["rtb-xxxxxxxx", "rtb-yyyyyyyy", "rtb-zzzzzzzz"]
    vpn_connection_static_routes_only         = "true"
    vpn_connection_static_routes_destinations = ["10.80.1.0/24"]
  }

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Requirements

Name Version
terraform >= 1.3.0
aws >= 2.0

Providers

Name Version
aws >= 2.0

Modules

Name Source Version
logs cloudposse/cloudwatch-logs/aws 0.6.8
this cloudposse/label/null 0.25.0

Resources

Name Type
aws_customer_gateway.default resource
aws_ec2_tag.default resource
aws_ec2_transit_gateway_route.default resource
aws_ec2_transit_gateway_route_table_association.default resource
aws_ec2_transit_gateway_route_table_propagation.default resource
aws_vpn_connection.default resource
aws_vpn_connection_route.default resource
aws_vpn_gateway.default resource
aws_vpn_gateway_route_propagation.default resource

Inputs

Name Description Type Default Required
additional_tag_map Additional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration.		 map(string) {} no
attributes ID element. Additional attributes (e.g. workers or cluster) to add to id,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the delimiter
and treated as a single ID element.		 list(string) [] no
context Single object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as null to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional_tag_map, which are merged.		 any 
{
  "additional_tag_map": {},
  "attributes": [],
  "delimiter": null,
  "descriptor_formats": {},
  "enabled": true,
  "environment": null,
  "id_length_limit": null,
  "label_key_case": null,
  "label_order": [],
  "label_value_case": null,
  "labels_as_tags": [
    "unset"
  ],
  "name": null,
  "namespace": null,
  "regex_replace_chars": null,
  "stage": null,
  "tags": {},
  "tenant": null
}
 no
customer_gateway_bgp_asn The gateway's Border Gateway Protocol (BGP) Autonomous System Number (ASN) number 65000 no
customer_gateway_ip_address The IP address of the gateway's Internet-routable external interface string n/a yes
delimiter Delimiter to be used between ID elements.
Defaults to - (hyphen). Set to "" to use no delimiter at all.		 string null no
descriptor_formats Describe additional descriptors to be output in the descriptors output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
{<br> format = string<br> labels = list(string)<br>}
(Type is any so the map values can later be enhanced to provide additional options.)
format is a Terraform format string to be passed to the format() function.
labels is a list of labels, in order, to pass to format() function.
Label values will be normalized before being passed to format() so they will be
identical to how they appear in id.
Default is {} (descriptors output will be empty).		 any {} no
enabled Set to false to prevent the module from creating any resources bool null no
environment ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' string null no
existing_transit_gateway_id Existing Transit Gateway ID. If provided, the module will not create a Virtual Private Gateway but instead will use the transit_gateway. For setting up transit gateway we can use the cloudposse/transit-gateway/aws module and pass the output transit_gateway_id to this variable. string "" no
id_length_limit Limit id to this many characters (minimum 6).
Set to 0 for unlimited length.
Set to null for keep the existing setting, which defaults to 0.
Does not affect id_full.		 number null no
label_key_case Controls the letter case of the tags keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via the tags input.
Possible values: lower, title, upper.
Default value: title.		 string null no
label_order The order in which the labels (ID elements) appear in the id.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.		 list(string) null no
label_value_case Controls the letter case of ID elements (labels) as included in id,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via the tags input.
Possible values: lower, title, upper and none (no transformation).
Set this to title and set delimiter to "" to yield Pascal Case IDs.
Default value: lower.		 string null no
labels_as_tags Set of labels (ID elements) to include as tags in the tags output.
Default is to include all labels.
Tags with empty values will not be included in the tags output.
Set to [] to suppress all generated tags.
Notes:
The value of the name tag, if included, will be the id, not the name.
Unlike other null-label inputs, the initial setting of labels_as_tags cannot be
changed in later chained modules. Attempts to change it will be silently ignored.		 set(string) 
[
  "default"
]
 no
name ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as a tag.
The "name" tag is set to the full id string. There is no tag with the value of the name input.		 string null no
namespace ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique string null no
regex_replace_chars Terraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.		 string null no
route_table_ids The IDs of the route tables for which routes from the Virtual Private Gateway will be propagated list(string) [] no
stage ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release' string null no
tags Additional tags (e.g. {'BusinessUnit': 'XYZ'}).
Neither the tag keys nor the tag values will be modified by this module.		 map(string) {} no
tenant ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for string null no
transit_gateway_enabled Set to true to enable VPN connection to transit gateway and then pass in the existing_transit_gateway_id bool false no
transit_gateway_route_table_id The ID of the route table for the transit gateway that you want to associate + propogate the VPN connection's TGW attachment string null no
transit_gateway_routes A map of transit gateway routes to create on the given TGW route table (via transit_gateway_route_table_id) for the created VPN Attachment. Use the key in the map to describe the route. 
map(object({
    blackhole              = optional(bool, false)
    destination_cidr_block = string
  }))
 {} no
vpc_id The ID of the VPC to which the Virtual Private Gateway will be attached string null no
vpn_connection_local_ipv4_network_cidr The IPv4 CIDR on the customer gateway (on-premises) side of the VPN connection. string "0.0.0.0/0" no
vpn_connection_log_retention_in_days Specifies the number of days you want to retain log events. number 30 no
vpn_connection_remote_ipv4_network_cidr The IPv4 CIDR on the AWS side of the VPN connection. string "0.0.0.0/0" no
vpn_connection_static_routes_destinations List of CIDR blocks to be used as destination for static routes. Routes to destinations will be propagated to the route tables defined in route_table_ids list(string) [] no
vpn_connection_static_routes_only If set to true, the VPN connection will use static routes exclusively. Static routes must be used for devices that don't support BGP bool false no
vpn_connection_tunnel1_cloudwatch_log_enabled Enable or disable VPN tunnel logging feature for the tunnel bool false no
vpn_connection_tunnel1_cloudwatch_log_output_format Set log format for the tunnel. Default format is json. Possible values are: json and text string "json" no
vpn_connection_tunnel1_dpd_timeout_action The action to take after DPD timeout occurs for the first VPN tunnel. Specify restart to restart the IKE initiation. Specify clear to end the IKE session. Valid values are clear | none | restart. string "clear" no
vpn_connection_tunnel1_ike_versions The IKE versions that are permitted for the first VPN tunnel. Valid values are ikev1 | ikev2. list(string) [] no
vpn_connection_tunnel1_inside_cidr The CIDR block of the inside IP addresses for the first VPN tunnel string null no
vpn_connection_tunnel1_phase1_dh_group_numbers List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24. list(string) [] no
vpn_connection_tunnel1_phase1_encryption_algorithms List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16. list(string) [] no
vpn_connection_tunnel1_phase1_integrity_algorithms One or more integrity algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512. list(string) [] no
vpn_connection_tunnel1_phase2_dh_group_numbers List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24. list(string) [] no
vpn_connection_tunnel1_phase2_encryption_algorithms List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16. list(string) [] no
vpn_connection_tunnel1_phase2_integrity_algorithms One or more integrity algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512. list(string) [] no
vpn_connection_tunnel1_preshared_key The preshared key of the first VPN tunnel. The preshared key must be between 8 and 64 characters in length and cannot start with zero. Allowed characters are alphanumeric characters, periods(.) and underscores(_) string null no
vpn_connection_tunnel1_startup_action The action to take when the establishing the tunnel for the first VPN connection. By default, your customer gateway device must initiate the IKE negotiation and bring up the tunnel. Specify start for AWS to initiate the IKE negotiation. Valid values are add | start. string "add" no
vpn_connection_tunnel2_cloudwatch_log_enabled Enable or disable VPN tunnel logging feature for the tunnel bool false no
vpn_connection_tunnel2_cloudwatch_log_output_format Set log format for the tunnel. Default format is json. Possible values are: json and text string "json" no
vpn_connection_tunnel2_dpd_timeout_action The action to take after DPD timeout occurs for the second VPN tunnel. Specify restart to restart the IKE initiation. Specify clear to end the IKE session. Valid values are clear | none | restart. string "clear" no
vpn_connection_tunnel2_ike_versions The IKE versions that are permitted for the second VPN tunnel. Valid values are ikev1 | ikev2. list(string) [] no
vpn_connection_tunnel2_inside_cidr The CIDR block of the inside IP addresses for the second VPN tunnel string null no
vpn_connection_tunnel2_phase1_dh_group_numbers List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24. list(string) [] no
vpn_connection_tunnel2_phase1_encryption_algorithms List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16. list(string) [] no
vpn_connection_tunnel2_phase1_integrity_algorithms One or more integrity algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512. list(string) [] no
vpn_connection_tunnel2_phase2_dh_group_numbers List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24. list(string) [] no
vpn_connection_tunnel2_phase2_encryption_algorithms List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16. list(string) [] no
vpn_connection_tunnel2_phase2_integrity_algorithms One or more integrity algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512. list(string) [] no
vpn_connection_tunnel2_preshared_key The preshared key of the second VPN tunnel. The preshared key must be between 8 and 64 characters in length and cannot start with zero. Allowed characters are alphanumeric characters, periods(.) and underscores(_) string null no
vpn_connection_tunnel2_startup_action The action to take when the establishing the tunnel for the second VPN connection. By default, your customer gateway device must initiate the IKE negotiation and bring up the tunnel. Specify start for AWS to initiate the IKE negotiation. Valid values are add | start. string "add" no
vpn_gateway_amazon_side_asn The Autonomous System Number (ASN) for the Amazon side of the VPN gateway. If you don't specify an ASN, the Virtual Private Gateway is created with the default ASN number 64512 no

Outputs

Name Description
customer_gateway_id Customer Gateway ID
transit_gateway_attachment_id The ID of the transit gateway attachment for the VPN connection (if a TGW connection)
vpn_connection_customer_gateway_configuration The configuration information for the VPN connection's Customer Gateway (in the native XML format)
vpn_connection_id VPN Connection ID
vpn_connection_tunnel1_address The public IP address of the first VPN tunnel
vpn_connection_tunnel1_cgw_inside_address The RFC 6890 link-local address of the first VPN tunnel (Customer Gateway side)
vpn_connection_tunnel1_vgw_inside_address The RFC 6890 link-local address of the first VPN tunnel (Virtual Private Gateway side)
vpn_connection_tunnel2_address The public IP address of the second VPN tunnel
vpn_connection_tunnel2_cgw_inside_address The RFC 6890 link-local address of the second VPN tunnel (Customer Gateway side)
vpn_connection_tunnel2_vgw_inside_address The RFC 6890 link-local address of the second VPN tunnel (Virtual Private Gateway side)
vpn_gateway_id Virtual Private Gateway ID

Related Projects

Check out these related projects.

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

Request Quote

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

  • Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
  • Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
  • Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
  • Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
  • GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Request Quote

Day-2: Your Operational Mastery

  • Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
  • Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
  • Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
  • Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
  • Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
  • Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
  • Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

Request Quote

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Review our Code of Conduct and Contributor Guidelines.
  2. Fork the repo on GitHub
  3. Clone the project to your own machine
  4. Commit changes to your own branch
  5. Push your work back up to your fork
  6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

License

Preamble to the Apache License, Version 2.0

Complete license is available in the LICENSE file.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

Copyright © 2017-2024 Cloud Posse, LLC

README footer

Beacon

terraform-aws-vpn-connection's People

Contributors

actions-user avatar aknysh avatar cloudpossebot avatar dylanbannon avatar esolitos avatar gberenice avatar gowiem avatar matharoo avatar max-lobur avatar maximmi avatar osterman avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

lbalak50 ogrodniczek paulboot karunakar114 maverick1974 srinivas-yatirajula ronaldkonjer arun9theja td-vijay ccaiccie knorrkator techiewarrior olegevtushenko infinnity-card alyragab thor-consulting iqnupe doytsujin mossey mtaufikromdony kihahu lukas085 black00791 gberenice ebury mikedizon derekstrickland srihari-nomi vkanelov ryanoatz99 ariansyahyutama vidaletti rajesh-dhandapani asmtal ecogit-stage patelavtx sanmakol kelvintsim classicvalues paulvandenburg mnulensihomer gaji-gesa jonatanhost packet-sniffer marciozampiron l0tke nymedia matharoo eanselmi digtl-machine cloudscript-technology lawrencewarren tabthree3

terraform-aws-vpn-connection's Issues

Error on plan execution

Describe the Bug

On plan execution:

│ Error: Output refers to sensitive values
│
│ on outputs.tf line 16:
│ 16: output "vpn_connection_customer_gateway_configuration" {
│
│ To reduce the risk of accidentally exporting sensitive data that was
│ intended to be only internal, Terraform requires that any root module
│ output containing sensitive data be explicitly marked as sensitive, to
│ confirm your intent.
│
│ If you do intend to export this data, annotate the output value as
│ sensitive by adding the following argument:
│ sensitive = true

Expected Behavior

Expected:

Plan: 5 to add, 0 to change, 0 to destroy.

Changes to Outputs:

  • customer_gateway_id = (known after apply)
  • vpn_connection_customer_gateway_configuration = (sensitive value)
  • vpn_connection_id = (known after apply)
  • vpn_connection_tunnel1_address = (known after apply)
  • vpn_connection_tunnel1_cgw_inside_address = (known after apply)
  • vpn_connection_tunnel1_vgw_inside_address = (known after apply)
  • vpn_connection_tunnel2_address = (known after apply)
  • vpn_connection_tunnel2_cgw_inside_address = (known after apply)
  • vpn_connection_tunnel2_vgw_inside_address = (known after apply)
  • vpn_gateway_id = (known after apply)

──────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.
Releasing state lock. This may take a few moments...

Steps to Reproduce

terraform {
required_version = ">= 0.13.0"

required_providers {
aws = {
source = "hashicorp/aws"
version = ">= 2.0"
}
null = {
source = "hashicorp/null"
version = ">= 2.0"
}
}
}

Screenshots

No response

Environment

OSX Ventura
terraform {
required_version = ">= 0.13.0"

required_providers {
aws = {
source = "hashicorp/aws"
version = ">= 2.0"
}
null = {
source = "hashicorp/null"
version = ">= 2.0"
}
}
}

Module version:
[email protected]:cloudposse/terraform-aws-vpn-connection.git?ref=0.9.0

Additional Context

Fix this:

output "vpn_connection_customer_gateway_configuration" {
description = "The configuration information for the VPN connection's Customer Gateway (in the native XML format)"
sensitive = true
value = join(
"",
aws_vpn_connection.default.*.customer_gateway_configuration,
)
}

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

terraform
main.tf
versions.tf
  • aws >= 2.0
  • null >= 2.0
  • hashicorp/terraform >= 0.13.0
  • Check this box to trigger a request for Renovate to run again on this repository

Output Request

Describe the Feature

When transit_gateway_enabled = true a tgw attachment is created, the module should output the tgw attachment id

Expected Behavior

When transit_gateway_enabled = true a tgw attachment is created, the module should output the tgw attachment id

Use Case

When transit_gateway_enabled = true a tgw attachment is created, the module should output the tgw attachment id

Describe Ideal Solution

When transit_gateway_enabled = true a tgw attachment is created, the module should output the tgw attachment id

Alternatives Considered

No response

Additional Context

No response

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

Can't use this module 2 times for different VPN on 1 VPC

Describe the Bug

When using this module for 2d VPN connection on the VPC in my AWS infra I'm getting errors due to the new VPN Gateway trying to be created.

Error: error attaching EC2 VPN Gateway (vgw-***) to VPC (vpc-***): InvalidVpcState: VPC vpc-*** is currently attached to the Virtual Private Gateway.

Expected Behavior

It seems logical for me to be able to configure VPG that is used instead of creating a new one (especially when official VPC module has enable_vpn_gateway feature).

Steps to Reproduce

Steps to reproduce the behaviour:

  1. Run module for 1 VPN
  2. Run module with different parameters for 2 VPN, but reuse VPC id

Code snippets

module "vpn-connection-1" {
  source  = "cloudposse/vpn-connection/aws"
  version = "0.7.1"

  vpc_id                                    = module.vpc.vpc_id

  customer_gateway_ip_address               = "185.**.**.**"
  route_table_ids                           = []
  vpn_connection_static_routes_only         = "true"
  vpn_connection_static_routes_destinations = []

}

module "vpn-connection-2" {
  source  = "cloudposse/vpn-connection/aws"
  version = "0.7.1"

  vpc_id                                    = module.vpc.vpc_id

  customer_gateway_ip_address               = "74.**.**.**"
  route_table_ids                           = []
  vpn_connection_static_routes_only         = "true"
  vpn_connection_static_routes_destinations = []

  # phase 1
  vpn_connection_tunnel1_ike_versions                 = ["ikev2"]
  vpn_connection_tunnel1_phase1_dh_group_numbers      = ["21"]
  vpn_connection_tunnel1_phase1_encryption_algorithms = ["AES256"]
  vpn_connection_tunnel1_phase1_integrity_algorithms  = ["SHA256"]

  # phase2
  vpn_connection_tunnel2_ike_versions                 = ["ikev2"]
  vpn_connection_tunnel1_phase2_dh_group_numbers      = ["21"]
  vpn_connection_tunnel1_phase2_encryption_algorithms = ["AES256"]
  vpn_connection_tunnel1_phase2_integrity_algorithms  = ["SHA256"]

}

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

  • AWS
  • version = "0.7.1"

Add support for lifecycle control

Describe the Feature

https://docs.aws.amazon.com/vpn/latest/s2svpn/tunnel-endpoint-lifecycle.html

Tunnel endpoint lifecycle control provides control over the schedule of endpoint replacements, and can help minimize connectivity disruptions during AWS managed tunnel endpoint replacements.

Expected Behavior

I expect to be able to configure tunnel endpoint lifecycle control.

Use Case

It is required to control the VPN endpoint maintenance schedule in situations where you can't configure double tunnels.

Describe Ideal Solution

This feature is already supported by the provider, just support required arguments in the module.

Alternatives Considered

No response

Additional Context

No response

Add transit_gateway_id support to the module to allows multiple VPCs via single site-to-site vpn

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Slack Community

Describe the Feature

Allow passing in the transit_gateway_id to the module so that we can allow traffic to and through multiple VPCs with single site-to-site vpn.

Expected Behavior

Allow traffic to flow through to multiple VPCs without the need to setup multiple site-to-site vpns for each vpc because every vpn gateway only is attached to single vpc.

Use Case

Currently we cannot setup a VPN with transit gateway id, we can only setup with vpn virtual private gateway which is only attached to one 1 VPC. If we allow transit_gateway_id to be set then we can allow traffic to multiple vpcs via site-to-site vpn because its possible to attach multiple vpcs to single transit gateway.

Describe Ideal Solution

We can allow passing in just transit_gateway_id and let user setup transit-gateway outside of the module using the https://github.com/cloudposse/terraform-aws-transit-gateway

Alternatives Considered

Explain what alternative solutions or features you've considered.

Additional Context

In the resource "aws_vpn_connection"
transit_gateway_id - (Optional) The ID of the EC2 Transit Gateway.

Using defaults results in circular modifications in-place

Describe the Bug

When creating a VPN using the aws_vpn_connection resource, lots of defaults for the VPN are set up which is desired. When you come to plan/apply you get in-place changes where the default values are to be taken out and replaced with nothing. This leads to the VPN being modified and the tunnels going down during the process despite nothing actually happening.

Expected Behavior

You don't modify in place or anything when the modification is to remove the default values so that you can use the default values.

Steps to Reproduce

  1. Create a resource
resource "aws_vpn_connection" "main" {
    count                       = var.enable_vpn ? 1 : 0
    vpn_gateway_id              = aws_vpn_gateway.vpn_gateway[0].id
    customer_gateway_id         = aws_customer_gateway.customer_gateway[0].id
    type                        = "ipsec.1"
    static_routes_only          = true

    tags = {
        Name = "${var.customer_name}-VPN"
    }
}
  1. Apply the VPN - and then later apply again
# aws_vpn_connection.main[0] will be updated in-place
  ~ resource "aws_vpn_connection" "main" {
        id                                   = "vpn-0c6ec0afe0bd1debb"
        tags                                 = {
            "Name" = "***-VPN"
        }
      ~ tunnel1_ike_versions                 = [
          - "ikev1",
          - "ikev2",
        ]
      ~ tunnel1_phase1_dh_group_numbers      = [
          - 2,
          - 14,
          - 15,
          - 16,
          - 17,
          - 18,
          - 19,
          - 20,
          - 21,
          - 22,
          - 23,
          - 24,
        ]
      ~ tunnel1_phase1_encryption_algorithms = [
          - "AES128",
          - "AES128-GCM-16",
          - "AES256",
          - "AES256-GCM-16",
        ]
      ~ tunnel1_phase1_integrity_algorithms  = [
          - "SHA1",
          - "SHA2-256",
          - "SHA2-384",
          - "SHA2-512",
        ]
      ~ tunnel1_phase2_dh_group_numbers      = [
          - 2,
          - 5,
          - 14,
          - 15,
          - 16,
          - 17,
          - 18,
          - 19,
          - 20,
          - 21,
          - 22,
          - 23,
          - 24,
        ]
      ~ tunnel1_phase2_encryption_algorithms = [
          - "AES128",
          - "AES128-GCM-16",
          - "AES256",
          - "AES256-GCM-16",
        ]
      ~ tunnel1_phase2_integrity_algorithms  = [
          - "SHA1",
          - "SHA2-256",
          - "SHA2-384",
          - "SHA2-512",
        ]
      ~ tunnel2_ike_versions                 = [
          - "ikev1",
          - "ikev2",
        ]
      ~ tunnel2_phase1_dh_group_numbers      = [
          - 2,
          - 14,
          - 15,
          - 16,
          - 17,
          - 18,
          - 19,
          - 20,
          - 21,
          - 22,
          - 23,
          - 24,
        ]
      ~ tunnel2_phase1_encryption_algorithms = [
          - "AES128",
          - "AES128-GCM-16",
          - "AES256",
          - "AES256-GCM-16",
        ]
      ~ tunnel2_phase1_integrity_algorithms  = [
          - "SHA1",
          - "SHA2-256",
          - "SHA2-384",
          - "SHA2-512",
        ]
      ~ tunnel2_phase2_dh_group_numbers      = [
          - 2,
          - 5,
          - 14,
          - 15,
          - 16,
          - 17,
          - 18,
          - 19,
          - 20,
          - 21,
          - 22,
          - 23,
          - 24,
        ]
      ~ tunnel2_phase2_encryption_algorithms = [
          - "AES128",
          - "AES128-GCM-16",
          - "AES256",
          - "AES256-GCM-16",
        ]
      ~ tunnel2_phase2_integrity_algorithms  = [
          - "SHA1",
          - "SHA2-256",
          - "SHA2-384",
          - "SHA2-512",
        ]
        # (41 unchanged attributes hidden)
    }

aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 1m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 1m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m0s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m10s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m20s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m30s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 2m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m0s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m10s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m20s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m30s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 3m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m0s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m10s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m20s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m30s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 4m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m0s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m10s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m20s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m30s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 5m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m0s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m10s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m20s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m30s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m40s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 6m50s elapsed]
aws_vpn_connection.main[0]: Still modifying... [id=vpn-0c6ec0afe0bd1debb, 7m0s elapsed]
  1. Have you tunnels go down

image

Environment (please complete the following information):

Terraform v1.1.9
on windows_386

  • provider registry.terraform.io/hashicorp/aws v4.13.0
  • provider registry.terraform.io/hashicorp/cloudinit v2.2.0
  • provider registry.terraform.io/hashicorp/kubernetes v2.11.0
  • provider registry.terraform.io/hashicorp/null v3.1.1
  • provider registry.terraform.io/hashicorp/template v2.2.0
  • provider registry.terraform.io/hashicorp/tls v3.3.0

Additional Context

Add any other context about the problem here.

Allow for adding routes to AWS route tables for accessing on-prem systems

Describe the Feature

It seems this feature is not yet supported. In my experiments the route-propagation setting is enabled, but routes to internal (on-prem) CIDRs are not added to my AWS route tables.

Expected Behavior

I'd expect my AWS route tables to be augmented with routes to my on-prem CIDRs via the virtual private gateway.

Use Case

This has been proven to be necessary for our platform.

Describe Ideal Solution

I'd expect my AWS route tables to be augmented with routes to my on-prem CIDRs via the virtual private gateway.

Alternatives Considered

No response

Additional Context

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.