VpnTunnelOptionsSpecification
In this article:
VpnTunnelOptionsSpecification#
VPN connection tunnel options.
Contents#
IKEVersions — The allowed IKE versions for the VPN tunnel. Currently, there is no support for both IKE versions at the same time.
Type: List of IKEVersionsRequestListValue objects
Valid values:
ikev1|ikev2Default:
ikev1Required: No
Phase1DHGroupNumbers — The allowed Diffie-Hellman group numbers for a VPN tunnel in the first IKE phase.
Type: List of Phase1DHGroupNumbersRequestListValue objects
Valid values:
5|14|15|16|17|18|19|20|21Constraints: Six values maximum
Default: Groups
14,15,16,17,18Required: No
Phase1EncryptionAlgorithms — The allowed encryption algorithms for the VPN tunnel in the first IKE phase.
Type: List of Phase1EncryptionAlgorithmsRequestListValue objects
Valid values:
aes256|aes_ctr128|aes_ctr256|aes_gcm128|aes_gcm256|camellia128|camellia256|chacha20poly1305Constraints:
aes_ccm128,aes_ccm256,aes_gcm128,aes_gcm256, andchacha20poly1305are not supported inikev1. All algorithms support 192-bit keys, provided that 128-bit and 256-bit versions are specified at the same time. The 192-bit version is not supported on its own.Default: All supported algorithms, depending on the IKE version
Required: No
Phase1IntegrityAlgorithms — The allowed integrity algorithms for the VPN tunnel in the first IKE phase.
Type: List of Phase1IntegrityAlgorithmsRequestListValue objects
Valid values:
sha1|sha256|sha384|sha512Default:
sha256,sha384,sha512Required: No
Phase1LifetimeSeconds — The lifetime for phase 1 of the IKE (in seconds).
Type: Integer
Constraints: An integer value between 900 and 28800.
Default: 28800
Required: No
Phase2DHGroupNumbers — The allowed Diffie-Hellman group numbers for a VPN tunnel in the second IKE phase.
Type: List of Phase2DHGroupNumbersRequestListValue objects
Valid values:
0|5|14|15|16|17|18|19|20|21Constraints: This option supports at most one value. Group numbers
19,20, and21are not supported inikev1. The value0applies to Phase 2 only and means that PFS (Perfect Forward Secrecy) is disabled. Disabling PFS is not recommended, because it can compromise the session encryption key.Default:
14Required: No
Phase2EncryptionAlgorithms — The allowed encryption algorithms for the VPN tunnel in the second IKE phase.
Type: List of Phase2EncryptionAlgorithmsRequestListValue objects
Valid values:
aes256|aes_ccm128|aes_ccm256|aes_ctr128|aes_ctr256|aes_gcm128|aes_gcm256|camellia128|camellia256|chacha20poly1305Constraints:
chacha20poly1305is not supported inikev1. All algorithms support 192-bit keys, provided that 128-bit and 256-bit versions are specified at the same time. The 192-bit version is not supported on its own.Default: All supported algorithms, depending on the IKE version
Required: No
Phase2IntegrityAlgorithms — The allowed integrity algorithms for the VPN tunnel for the second IKE phase.
Type: List of Phase2IntegrityAlgorithmsRequestListValue objects
Valid values:
sha1|sha256|sha384|sha512Default:
sha256,sha384,sha512Required: No
Phase2LifetimeSeconds — The lifetime for phase 2 of the IKE (in seconds).
Type: Integer
Constraints: An integer value between 900 and 3600 must not exceed the value for Phase1LifetimeSeconds.
Default: 3600
Required: No
PreSharedKey — a key (PSK) used for initial authentication between VPN gateways and user gateways.
Type: String
Required: No
Constraints: A key should contain 8 to 64 characters, including letters, digits, periods (
.), underscores (_), and should not start with zero (0).
ReplayWindowSize — the number of packets in the IKE replay window.
Type: Integer
Constraints: An integer value between 32 and 2048
Default: 1024
Required: No
TunnelInsideCidr — A /30 block from the
169.254.252.0/22subnet to be used inside the IPsec tunnel of a VPN connection. The block must be unique for every connection that uses the current VPN gateway (VGW ID) and the public IP address of the customer gateway to which the connection is established. By default, inside tunnel addresses are assigned as follows: the first usable address is assigned to the VPC, and the second to the customer gateway. If necessary, you can specify the preferred address for the VPC, for example169.254.252.2/30. In that case, the VPN connection on the VPC side is assigned169.254.252.2, and the customer gateway is assigned169.254.252.1.Type: String
Required: No
Algorithm compatibility for different IKE versions:
Encryption |
IKEv1 |
IKEv2 |
Defaults |
||
|---|---|---|---|---|---|
Phase1 |
Phase2 |
Phase1 |
Phase2 |
||
AES256 |
Yes |
Yes |
Yes |
Yes |
Yes |
AES128-CTR |
Yes |
Yes |
Yes |
Yes |
Yes |
AES256-CTRa |
Yes |
Yes |
Yes |
Yes |
Yes |
CAMELLIA128 |
Yes |
Yes |
Yes |
Yes |
Yes |
CAMELLIA256 |
Yes |
Yes |
Yes |
Yes |
Yes |
AES128-GCM-16 |
No |
Yes |
Yes |
Yes |
Yes |
AES256-GCM-16 |
No |
Yes |
Yes |
Yes |
Yes |
AES128-CCM-16 |
No |
Yes |
No |
Yes |
Yes |
AES256-CCM-16 |
No |
Yes |
No |
Yes |
Yes |
CHACHA20-POLY1305 |
No |
No |
Yes |
Yes |
Yes |
Integrity |
IKEv1 |
IKEv2 |
Defaults |
||
|---|---|---|---|---|---|
Phase1 |
Phase2 |
Phase1 |
Phase2 |
||
SHA1 |
Yes |
Yes |
Yes |
Yes |
No |
SHA2-256 |
Yes |
Yes |
Yes |
Yes |
Yes |
SHA2-384 |
Yes |
Yes |
Yes |
Yes |
Yes |
SHA2-512 |
Yes |
Yes |
Yes |
Yes |
Yes |
Diffie-Hellman |
IKEv1 |
IKEv2 |
Defaults |
||
|---|---|---|---|---|---|
Phase1 |
Phase2 |
Phase1 |
Phase2 |
||
0 |
No |
Yes |
No |
Yes |
No |
5 |
Yes |
Yes |
Yes |
Yes |
No |
14 |
Yes |
Yes |
Yes |
Yes |
Yes |
15 |
Yes |
Yes |
Yes |
Yes |
Only P1 |
16 |
Yes |
Yes |
Yes |
Yes |
Only P1 |
17 |
Yes |
Yes |
Yes |
Yes |
Only P1 |
18 |
Yes |
Yes |
Yes |
Yes |
Only P1 |
19 |
Yes |
No |
Yes |
Yes |
No |
20 |
Yes |
No |
Yes |
Yes |
No |
21 |
Yes |
No |
Yes |
Yes |
No |