Add site-to-site-vpn
Terraform/OpenTofu component
#1106
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
site-to-site-vpn
Terraform/OpenTofu componentwhy
The component provisions a Site-To-Site VPN with a target AWS VPC on one side of the tunnel. The other (customer) side can be any VPN gateway endpoint, e.g. a hardware device, other cloud VPN, etc.
AWS Site-to-Site VPN is a fully-managed service that creates a secure connection between your data center or branch
office and your AWS resources using IP Security (IPSec) tunnels. When using Site-to-Site VPN, you can connect to both
your Amazon Virtual Private Clouds (VPC) and AWS Transit Gateway, and two tunnels per connection are used for
increased redundancy.
The component provisions the following resources:
AWS Virtual Private Gateway (a representation of the AWS side of the tunnel)
AWS Customer Gateway (a representation of the other (remote) side of the tunnel). It requires:
/32
IP of the VPN endpointAWS Site-To-Site VPN connection. It creates two VPN tunnels for redundancy and requires:
Route table entries to direct the appropriate traffic from the local VPC to the other side of the tunnel
references