{
  "slug": "aws-rds-postgresql-14-extended-support-end-of-support",
  "title": "Amazon RDS for PostgreSQL: PostgreSQL 14 end of RDS Extended Support",
  "summary": "RDS end of Extended Support date for PostgreSQL 14 on Amazon RDS for PostgreSQL: 28 Feb 2030. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
  "cloud": "aws",
  "service": "Amazon RDS for PostgreSQL",
  "service_slug": "rds-postgresql",
  "category": "database",
  "type": "end_of_support",
  "announced_date": null,
  "effective_date": "2030-02-28",
  "effective_precision": "day",
  "impact": "After the RDS end of Extended Support date (28 Feb 2030), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 14.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
  "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
  "replacement": null,
  "affected_versions": [
    "14"
  ],
  "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
  "extra_source_urls": [
    "https://endoflife.date/amazon-rds-postgresql"
  ],
  "vendor_ref": "amazon-rds-postgresql@14",
  "last_checked_at": "2026-11-12T09:55:35.707Z",
  "created_at": "2026-11-13T13:36:44.208Z",
  "updated_at": "2026-11-13T13:36:44.208Z",
  "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-extended-support-end-of-support",
  "short_url": "https://eolwatch.dev/i/d7",
  "markdown_url": "https://eolwatch.dev/items/aws-rds-postgresql-14-extended-support-end-of-support.md",
  "json_url": "https://eolwatch.dev/items/aws-rds-postgresql-14-extended-support-end-of-support.json",
  "estate_check": {
    "resource_types": [
      "aws_db_instance",
      "aws_rds_cluster"
    ],
    "fields": [
      "engine",
      "engine_version_actual",
      "engine_version"
    ],
    "inputs": [
      "Terraform state or plan (JSON)"
    ]
  }
}