Starting March 1, 2027, new AWS Site-to-Site VPN connections will default to recommended cryptographic algorithms. Today, a new connection enables every available algorithm for Internet Key Exchange (IKE) version, encryption, integrity, and Diffie-Hellman group. After the change, only the recommended algorithms are enabled unless you choose others. Existing connections are not affected.
Every Site-to-Site VPN connection uses IKE for tunnel negotiation and IPsec for data-plane encryption, so the algorithms you allow determine the strength of your tunnels. Since 2015, you have been able to choose from a range of encryption, integrity, and key exchange algorithms. We have since added IKEv2 support, per-tunnel algorithm configuration, additional algorithms, and a Recommended sample configuration. The new default applies that recommended configuration automatically, with no extra steps required.
This post explains what changes, what stays the same, and how to audit and update your connections.
What is changing
Today, when you create a new Site-to-Site VPN connection, every available algorithm is enabled by default for IKE version, encryption, integrity, and Diffie-Hellman group. You can clear options to restrict which algorithms are negotiated. Effective March 1, 2027, that changes. For each of IKE version, integrity, encryption, and Diffie-Hellman group, only the recommended algorithms are enabled by default on new connections. If you need to interoperate with devices that require non-recommended algorithms, you can still explicitly opt those algorithms back in when you create the connection. If you don’t, new connections that you create after the change will fail to negotiate with those devices. This includes connections that you create through AWS CloudFormation, AWS Cloud Development Kit (AWS CDK), or Terraform.
Table 1 compares the current and new defaults. It uses the values that the CreateVpnConnection and ModifyVpnTunnelOptions APIs accept. AES128 and AES256 are AES-CBC.
| Phase | Parameter | Current behavior (all options enabled) | New default (recommended only) |
| IKE (Phase 1) | IKE version | IKEv1, IKEv2 | IKEv2 |
| IKE (Phase 1) | Encryption | AES128, AES256, AES128-GCM-16, AES256-GCM-16 | AES256-GCM-16 |
| IKE (Phase 1) | Integrity | SHA1, SHA2-256, SHA2-384, SHA2-512 | SHA2-384 |
| IKE (Phase 1) | Diffie-Hellman group | Groups 2, 14–24 | Group 20 (384-bit ECP) |
| IPsec (Phase 2) | Encryption | AES128, AES256, AES128-GCM-16, AES256-GCM-16 | AES256-GCM-16 |
| IPsec (Phase 2) | Integrity | SHA1, SHA2-256, SHA2-384, SHA2-512 | SHA2-384 |
| IPsec (Phase 2) | Diffie-Hellman group | Groups 2, 5, 14–24 | Group 20 (384-bit ECP) |
Table 1: Site-to-Site VPN tunnel option defaults: Current and new
These algorithms follow current AWS cryptographic best practices. Each one protects a different part of the tunnel:
AES256-GCM-16provides authenticated encryption with associated data (AEAD).- SHA2-384 provides the pseudorandom function (PRF) and the integrity algorithm.
- Diffie-Hellman group 20, a 384-bit elliptic-curve group approved by the National Institute of Standards and Technology (NIST), secures the key exchange that provides forward secrecy.
Site-to-Site VPN will continue to update based on the latest cryptographic preferences, including post-quantum algorithms.
What isn’t changing
- Existing VPN connections are not affected – If you have a VPN tunnel in use today, nothing about it changes on March 1, 2027. Its negotiated algorithms stay exactly as configured.
- You can still use non-recommended algorithms on new VPN connections – If your on-premises device requires a non-recommended algorithm (for example, an appliance that doesn’t support IKEv2 or elliptic curve (ECP) groups), you can explicitly specify those parameters when you create a new connection. Site-to-Site VPN honors your explicit configuration. For steps, see Create a VPN connection in the AWS Site-to-Site VPN User Guide.
- No downtime from the new default – The new default applies only when you create a connection, so it doesn’t interrupt your existing tunnels. If you choose to migrate existing tunnels, as described in the next section, each tunnel has brief downtime when you update it.
How do I update existing VPNs?
To migrate your existing VPN tunnels to the recommended algorithms before March 1, 2027, use the following process:
- Audit your current tunnels – Use the GetActiveVpnTunnelStatus API to inspect the algorithms currently negotiated on each of your active tunnels. This tells you exactly which IKE and IPsec algorithms are in use today.
Tip: To audit every Site-to-Site VPN connection in all enabled AWS Regions of your account, use the audit script in the next section of this post.
- Update your customer gateway device – Reconfigure your on-premises device to use the recommended algorithms (IKEv2,
AES256-GCM-16, SHA2-384, Group 20). If the tunnel doesn’t re-establish, you can roll back by updating to the non-recommended algorithms. - Validate connectivity – After the tunnel re-establishes, confirm that it’s up and uses the recommended algorithms. Call GetActiveVpnTunnelStatus again and check that the algorithm fields match your new configuration.
- Lock down the AWS side, one tunnel at a time – Use the ModifyVpnTunnelOptions API to remove the non-recommended algorithms from the AWS tunnel configuration. Work through your tunnels one at a time to minimize risk. Each update causes a brief period of downtime for that tunnel.
Site-to-Site VPN audit script
The following script audits all Site-to-Site VPN connections in every enabled Region of your account. Use it for step 1 (Audit your current tunnels) in the “How do I update existing VPNs?” section.
How to run the script
We recommend running the script in AWS CloudShell, a browser-based terminal that you open from the AWS Management Console. It works the same on Windows and macOS, and it already includes the AWS Command Line Interface (AWS CLI), so you don’t need to install anything.
Before you start, make sure that the AWS Identity and Access Management (IAM) user or role that you sign in with has access to CloudShell and these read-only permissions: ec2:DescribeRegions, ec2:DescribeVpnConnections, and ec2:GetActiveVpnTunnelStatus.
- Sign in and open AWS CloudShell.
- Run
cat > vpn-tunnel-crypto-report.sh, paste the script, and then press Ctrl+D. - Run
bash vpn-tunnel-crypto-report.sh > report.csv. - Choose Actions > Download file, enter
report.csv, and open the file in a spreadsheet.
Conclusion
Starting March 1, 2027, new Site-to-Site VPN connections will default to recommended cryptographic algorithms: IKEv2, AES256-GCM-16, SHA2-384, and Diffie-Hellman group 20. Existing connections keep their current configuration.
Before that date, take these steps:
- Run the audit script in this post to see which algorithms your tunnels negotiate today.
- If your customer gateway device supports only non-recommended algorithms, set the tunnel algorithm options explicitly in your scripts and templates. This includes AWS CloudFormation, AWS CDK, and Terraform. Otherwise, new connections that you create after the change will fail to negotiate with that device.
- Plan when to move your existing tunnels to the recommended algorithms.
To learn more, see the following resources:
- Configure tunnel options for AWS Site-to-Site VPN
- Best practices for an AWS Site-to-Site VPN customer gateway device
- AWS Site-to-Site VPN User Guide
- AWS Site-to-Site VPN product page


