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.
aws_vpn_connection
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
}
Requires:
Especially need the option to specify IKEv2.
Any updates on this ? IKEv2 will be very helpful.
Eagerly waiting for ikev2, any approx timeline for this ?
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.
This would be definitely a great addition.
@brandonstevens, if possible could you also add support for these timer settings, please?
Thanks in advance!
See also #11584, which has a pending PR.
Most helpful comment
Especially need the option to specify IKEv2.