AWS Security ChangesHomeSearch

AWS AmazonRDS high security documentation change

Service: AmazonRDS · 2025-11-28 · Security-related high

File: AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md

Summary

Added PostgreSQL 14.19 release notes with CVE-2025 fixes and security ownership fix

Security assessment

Includes backported CVE fixes and security ownership issue resolution without new security features

Diff

diff --git a/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md b/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
index dab3b7ceb..75456aa4f 100644
--- a//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
+++ b//AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/AuroraPostgreSQL.Updates.md
@@ -5 +5 @@
-PostgreSQL 17 versionsPostgreSQL 16 versionsPostgreSQL 15 versions (includes some deprecated versions)PostgreSQL 14 versions (includes some deprecated versions)PostgreSQL 13 versions (includes some deprecated versions)PostgreSQL 12 versions (includes some deprecated versions)PostgreSQL 11 versions (includes some deprecated versions)PostgreSQL 10 versions (Deprecated)PostgreSQL 9.6 versions (Deprecated)
+PostgreSQL 18.1PostgreSQL 17 versionsPostgreSQL 16 versionsPostgreSQL 15 versions (includes some deprecated versions)PostgreSQL 14 versions (includes some deprecated versions)PostgreSQL 13 versions (includes some deprecated versions)PostgreSQL 12 versions (includes some deprecated versions)PostgreSQL 11 versions (includes some deprecated versions)PostgreSQL 10 versions (Deprecated)PostgreSQL 9.6 versions (Deprecated)
@@ -27,0 +28,2 @@ For a list of AWS Regions, see [ Aurora PostgreSQL Region availability](https://
+  * PostgreSQL 18.1
+
@@ -48,0 +51,162 @@ For a list of AWS Regions, see [ Aurora PostgreSQL Region availability](https://
+## PostgreSQL 18.1
+
+The PostgreSQL community releases new Major versions of PostgreSQL annually. The Amazon RDS Database Preview Environment allows you to test beta, release candidate, and early production versions of Amazon Aurora releases. This allows customers to create DB Clusters on an early release of Aurora PostgreSQL 18 in the Preview environment and test its features.
+
+The following limitations apply to Aurora PostgreSQL Clusters in the Preview environment:
+
+  1. All DB instances/clusters are deleted 60 days after you create them, along with any backups and snapshots.
+
+  2. You can't copy a snapshot of a DB instance from Preview to a production environment.
+
+  3. The following options are supported by the Preview.
+
+    1. You can create DB instances using r6g, r6i, r7g, r7i, r8g, x2g, t3 and t4g instance types only. For more information about RDS Aurora instance classes, see DB instance classes.
+
+    2. You can use both single-AZ and multi-AZ deployments.
+
+    3. You can use standard PostgreSQL dump and load functions to export databases from or import databases to the Database Preview Environment.
+
+
+
+
+Some of the Features that are not supported for APG18.1 Preview:
+
+  1. Serverless v1/v2
+
+  2. Major Version Upgrades i.e. MVU
+
+  3. No new minors will be released in preview region i.e. APG17.1 will not be released in preview region
+
+  4. RDS PostgreSQL to Aurora PostgreSQL Inbound replication
+
+  5. Amazon RDS Blue/Green deployment
+
+  6. Cross-Region snapshot copy
+
+  7. Global DB
+
+  8. Database Activity Streams (DAS), RDS Proxy and Data Migration Service (DMS)
+
+  9. Auto Scaling Read Replicas
+
+  10.   11. RDS Export
+
+  12. Performance Insights
+
+  13. Custom Endpoints
+
+  14. Snapshot Copy
+
+  15. zero-ETL
+
+  16. Babelfish
+
+  17. PostGis Topology module is not supported because of a community regression: [https://trac.osgeo.org/postgis/ticket/5983](https://trac.osgeo.org/postgis/ticket/5983)
+
+
+
+
+### Creating a new DB Cluster in the preview environment
+
+Use the following procedure to create a DB Cluster in the preview environment.
+
+###### To create a DB Cluster in the preview environment
+
+  1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).
+
+  2. Choose Dashboard from the navigation pane.
+
+  3. In the Dashboard page, locate the Database Preview Environment section on the Dashboard page, as shown in the following image.
+
+  4. You can navigate directly to the Database preview environment. Before you can proceed, you must acknowledge and accept the limitations.
+
+  5. To create the Aurora PostgreSQL DB instance, follow the same process as that for creating any Amazon Aurora PostgreSQL DB Cluster. For more information, see the Console procedure in Creating an Amazon Aurora PostgreSQL DB cluster.
+
+  6. To create an Cluster in the Database Preview Environment using the RDS API or the AWS CLI, use the following endpoint.
+
+`rds-preview.us-east-2.amazonaws.com`
+
+
+
+
+###### Releases and patches
+
+  * Aurora PostgreSQL 18.1 in the Amazon RDS Preview environment
+
+
+
+
+### Aurora PostgreSQL 18.1 in the Amazon RDS Preview environment
+
+_**This is preview documentation for Amazon Aurora PostgreSQL version 18.1. It is subject to change.**_
+
+This release of Aurora PostgreSQL is compatible with PostgreSQL 18.1. For more information about the improvements in PostgreSQL 18.1, see [PostgreSQL release 18.0](https://www.postgresql.org/docs/18/release-18.html) and [PostgreSQL release 18.1](https://www.postgresql.org/docs/18/release-18-1.html).
+
+###### Parameter updates
+
+  * `track_cost_delay_timing` default is set to on
+
+  * `max_active_replication_origins` default is set to 20
+
+  * `pclient_connection_check_interval` default is set to 60000
+
+  * `log_connections` was updated to reflect the new PostgreSQL 18 behavior. The old default value of 0 is equivalent to the new default empty value, and the old value of 1 is equivalent to specifying all three values of receipt, authentication, and authorization
+
+  * `autovacuum_worker_slots`, `io_workers`, `io_max_concurrency`
+
+
+
+
+###### Extension updates
+
+  * Updated h3-pg to version 4.2.3
+
+  * Updated PostGIS to version 3.6.0
+
+  * Updated pg_hint_plan to version 1.8.0
+
+  * Updated pg_cron to version 1.6.7
+
+  * Updated hypopg to version 1.4.2
+
+  * Updated MySQL FDW to version REL-2_9_3
+
+  * Updated pglogical to version 2.4.6
+
+  * Updated pgvector to version 0.8.1
+
+  * Updated PLv8 to version 3.2.4
+
+  * Updated TDS FDW to version 2.0.5
+
+  * Updated pg_tle to version 1.5.2
+
+  * Updated PgAudit to version 18.0
+
+  * Updated to PgRouting to version 3.8.0
+
+
+
+
+###### General enhancements
+
+  * Reduced commit latency when I/O optimized is enabled
+
+
+
+
+###### Unsupported Features
+
+  * Aurora PostgreSQL 18.1 does not currently support logical decoding on Aurora Read Replicas.
+
+  * Aurora PostgreSQL 18.1 does not currently support failover control within a Cluster.
+
+  * Aurora PostgreSQL 18.1 does not currently support pg_createsubscriber on Aurora Read Replicas.
+
+  * Aurora PostgreSQL 18.1 does not currently support Aurora PostgreSQL Query Plan Management.
+
+  * Aurora PostgreSQL 18.1 does not currently support in-region write forwarding
+
+
+
+
@@ -52,0 +217,2 @@ For a list of AWS Regions, see [ Aurora PostgreSQL Region availability](https://
+  * PostgreSQL 17.6
+
@@ -61,0 +228,105 @@ For a list of AWS Regions, see [ Aurora PostgreSQL Region availability](https://
+### PostgreSQL 17.6
+
+This release of Aurora PostgreSQL is compatible with PostgreSQL 17.6. For more information about the improvements in PostgreSQL 17.6, see [PostgreSQL release 17.6](https://www.postgresql.org/docs/17/release-17-6.html).
+
+###### Releases and patches
+
+  * Aurora PostgreSQL 17.6, November 25, 2025
+
+
+
+
+#### Aurora PostgreSQL 17.6, November 25, 2025
+
+**New features**
+
+  * Introduced Dynamic Data Masking (DDM), a database-level security feature that protects sensitive data by masking column values before they are presented to database clients, without modifying the actual stored data. DDM enables organizations to control access to Personally Identifiable Information (PII) and other sensitive data through role-based masking policies that are applied dynamically at query execution time. For more details visit <Link to be updated>.
+
+  * Introduced Shared Plan Cache to reduce memory usage by sharing query plans between backend processes.
+
+  * Added support for correlated subquery cache for EXISTS, NOT EXISTS, and row comparison subqueries.
+
+  * Introduced a new feature to significantly reduce database downtime during restarts by initializing Aurora storage metadata in parallel and reducing contention during initialization.
+