AWS AmazonRDS: Document ssl_groups TLS key-exchange configuration for Aurora PostgreSQL
Summary
Adds a TLS section covering the ssl_groups cluster parameter in Aurora PostgreSQL 18+, default and allowlisted named groups (including post-quantum ML-KEM groups X25519MLKEM768 and SecP256r1MLKEM768), server preference ordering, and hardening guidance to enforce TLS 1.3 via ssl_min_protocol_version and rds.force_ssl.
Security assessment
The diff adds security guidance about controlling TLS key-exchange groups, including post-quantum ML-KEM groups and how to force their use by enabling rds.force_ssl and setting ssl_min_protocol_version to TLSv1.3. It is encryption-hardening documentation rather than a fix for a named vulnerability or incident, so no CVE is cited.
Evidence
+The `ssl_groups` parameter specifies the named groups to use for TLS key exchange. For more information, see the [ssl_groups](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-SSL-GROUPS) in the PostgreSQL documentation.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Security.md b/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Security.md index 70bc567..5ec12c4 100644 --- a//AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Security.md +++ b//AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Security.md @@ -58,0 +59,2 @@ For general information about SSL/TLS support and PostgreSQL databases, see [SSL + * TLS key-exchange groups in Aurora PostgreSQL + @@ -232,0 +235,25 @@ Starting with Aurora PostgreSQL 18.3, TLS 1.3 ciphers are no longer controlled b +### TLS key-exchange groups in Aurora PostgreSQL + +The `ssl_groups` parameter specifies the named groups to use for TLS key exchange. For more information, see the [ssl_groups](https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-SSL-GROUPS) in the PostgreSQL documentation. + +In Aurora PostgreSQL 18 and later, you can modify the `ssl_groups` cluster parameter to use specific values from the allowlisted groups. This is a dynamic parameter that doesn't require a reboot. + +The following table lists the default and allowlisted custom `ssl_groups` values by engine major version. + +PostgreSQL engine version | Default `ssl_groups` values | Allowlisted custom `ssl_groups` values +---|---|--- +18 | `prime256v1:X25519` | `X25519MLKEM768` `SecP256r1MLKEM768` `X25519` `prime256v1` `secp384r1` + +When you configure `ssl_groups`, keep the following behavior in mind: + + * The order of the list sets the server preference. The first group in the list that the client also supports is used for a connection. + + * `ssl_groups` applies only to key exchange that uses named groups. For example, `ssl_groups` is ignored by TLS v1.2 cipher suites that use RSA key exchange. To use only the specified groups, make sure that `rds.force_ssl` is enabled. Then either set `ssl_min_protocol_version` to `TLSv1.3`, or restrict `ssl_ciphers` to ECDHE-based suites for TLS v1.2-based connections. + +ML-KEM groups require TLS v1.3. To enforce that they are used, set `ssl_min_protocol_version` to `TLSv1.3`. + + + + +For more information about modifying parameters and parameter groups, see [Modifying parameters in a DB cluster parameter groupin Amazon Aurora](./USER_WorkingWithParamGroups.ModifyingCluster.html). +