PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-19

Verify post-quantum TLS on Aurora PostgreSQL 18

Aurora PostgreSQL 18 and later let you configure post-quantum TLS key exchange with the ssl_groups cluster parameter. To confirm a hybrid group is actually in use, connect directly to a test database with a client that supports TLS 1.3 and the group. Inspect what the new connection negotiated. AWS currently documents that connections through RDS Proxy cannot negotiate these hybrid groups.

AWS Aurora PostgreSQL 18 Post-quantum TLS RDS Proxy

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • AWS announced that ssl_groups is configurable. The Aurora PostgreSQL 18 default remains prime256v1:X25519.
  • Hybrid groups require TLS 1.3 and client support. Aurora uses the first group on the server list that the client also supports.
  • ssl_groups is dynamic. Check new handshakes and preserve the original value for rollback.
  • Clients offering classical and hybrid groups can negotiate a classical group with RDS Proxy. A hybrid-only client cannot complete the proxy handshake.

Check the engine version and default before changing the cluster

On October 29, 2026, AWS announced that Aurora PostgreSQL 18 and later can change ssl_groups. The parameter lists named groups for TLS key exchange. A group defines how the client and server agree on a shared secret. Hybrid groups combine a traditional key exchange with ML-KEM.

The Aurora PostgreSQL 18 default is prime256v1:X25519. AWS lists X25519MLKEM768, SecP256r1MLKEM768, X25519, prime256v1 and secp384r1 as configurable groups. Check the engine and parameter group family for your cluster. The announcement does not list project-by-project availability or fees.

How does group order affect a new connection?

The order of ssl_groups sets the server’s preference. AWS says a connection uses the first listed group the client also supports. Suppose you put X25519MLKEM768 before the classical groups on a test cluster. A TLS 1.3 client that supports it can negotiate the hybrid group. A classical-only client still needs a classical group both sides support.

Hybrid groups require TLS 1.3. Raising the minimum TLS version alone can still leave classical groups available. Check the allowed groups and the negotiated result. ssl_groups does not control RSA key exchange in TLS 1.2. If your organization requires specific groups for every connection, evaluate rds.force_ssl, the minimum TLS version, and client compatibility together.

How do you verify direct and RDS Proxy connections?

Check whether the application connects to the Aurora database endpoint or to an RDS Proxy endpoint. AWS currently documents that connections through RDS Proxy cannot negotiate hybrid post-quantum groups. A client offering hybrid and classical groups can negotiate a classical group with the proxy. A hybrid-only client cannot complete that handshake.

In an authorized test environment, connect directly to the database using the same driver and TLS library as the application. Record the endpoint, client version, and the TLS version and group negotiated by a new connection. A successful query or a TLS 1.3 session does not establish that the group is hybrid. Record proxy compatibility separately for applications that use it.

How can you stage the change and roll it back?

Record the original value in the cluster parameter group, then make a scoped adjustment in an isolated environment. AWS classifies ssl_groups as dynamic and says it does not require a reboot. Check whether the clients you need can open new connections, and record expected groups, negotiated groups and failures. If you also plan to raise the minimum TLS version, test older drivers separately.

If an existing client cannot connect, restore the saved parameter value and check a new connection with the same client. Before a production change, identify the direct and proxy paths you need to support and prepare validation and rollback for each.

Sources

Frequently Asked Questions

Why do I still see X25519 after configuring a hybrid group?

Check the endpoint, TLS version, client support and ssl_groups order. For a direct database connection, both sides need to support the hybrid group. Through RDS Proxy, AWS currently documents classical group negotiation.

Do I need to reboot the cluster to change ssl_groups?

AWS marks this parameter as dynamic, so changing it alone does not require a reboot. If you replace the entire parameter group or change other parameters too, check the apply behavior for those operations separately.