Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Site-to-Site VPN Adds Configurability of Security Algorithms and Timer Settings for VPN Tunnels #9980

Closed
brandonstevens opened this issue Sep 4, 2019 · 9 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@brandonstevens
Copy link
Contributor

brandonstevens commented Sep 4, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

While creating VPN connections, you can now specify the security algorithms allowed for your tunnels and the timer settings proposed during negotiation by tunnel endpoints on the AWS side.

New or Affected Resource(s)

  • aws_vpn_connection

Potential Terraform Configuration

resource "aws_vpn_connection" "main" {
  vpn_gateway_id      = "${aws_vpn_gateway.vpn_gateway.id}"
  customer_gateway_id = "${aws_customer_gateway.customer_gateway.id}"
  type                = "ipsec.1"
  static_routes_only  = true

  tunnel1_dpd_timeout_seconds = 30
  tunnel1_ike_versions        = ["ikev1"]

  tunnel1_phase_1_dh_group_numbers      = [14]
  tunnel1_phase_1_encryption_algorithms = ["AES256"]
  tunnel1_phase_1_integrity_algorithms  = ["SHA2-256"]
  tunnel1_phase_1_lifetime_seconds      = 28000

  tunnel1_phase_2_dh_group_numbers      = [14]
  tunnel1_phase_2_encryption_algorithms = ["AES256"]
  tunnel1_phase_2_integrity_algorithms  = ["SHA2-256"]
  tunnel1_phase_2_lifetime_seconds      = 28000
}

References

Requires:

@brandonstevens brandonstevens added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 4, 2019
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 4, 2019
@MMarulla
Copy link
Contributor

Especially need the option to specify IKEv2.

@dflorea01
Copy link

Any updates on this ? IKEv2 will be very helpful.

@bflad bflad added service/ec2 Issues and PRs that pertain to the ec2 service. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 30, 2020
@sidhurana
Copy link

Eagerly waiting for ikev2, any approx timeline for this ?

@sidhurana
Copy link

sidhurana commented Apr 6, 2020

Just found that by default AWS VPN tunnel covers both IKEv1/IKEv2. We don't need to mention it explicitly. Though in AWS downloaded config it might show only ikev1 but it's enabled for ikev2 as well.

But it can be security issue to enable IKEv1 and AES-128, so it would be better to have above config so we can precisely mention the requirements.

@jcchak
Copy link

jcchak commented Aug 6, 2020

This would be definitely a great addition.

@brandonstevens, if possible could you also add support for these timer settings, please?

  • RekeyMarginTimeSeconds
  • RekeyFuzzPercentage
  • ReplayWindowSize

Thanks in advance!

@dthvt
Copy link
Contributor

dthvt commented Sep 15, 2020

See also #11584, which has a pending PR.

@dthvt
Copy link
Contributor

dthvt commented Apr 23, 2021

@brandonstevens I believe this is fixed in the latest provider version, if you want to review and close.

@breathingdust
Copy link
Member

This looks to have been closed in #11584 🚀

@github-actions
Copy link

github-actions bot commented Jun 2, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
8 participants