{
  "slug": "aws-aurora-mysql-version-3-extended-support-end-of-support",
  "title": "Amazon Aurora MySQL: version 3 end of RDS Extended Support",
  "summary": "End of RDS Extended Support date for Amazon Aurora MySQL version 3: 31 Jul 2029. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
  "cloud": "aws",
  "service": "Amazon Aurora MySQL",
  "service_slug": "aurora-mysql",
  "category": "database",
  "type": "end_of_support",
  "announced_date": null,
  "effective_date": "2029-07-31",
  "effective_precision": "day",
  "impact": "End of RDS Extended Support date for this major version: 31 Jul 2029. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- Support dates for a major engine version can also be read with the AWS CLI or the RDS API. See [Viewing support dates for engine versions in Amazon RDS Extended Support](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-viewing-support-dates.html).",
  "migration_path": "1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.\n2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.\n3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.\n4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).\n5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
  "replacement": null,
  "affected_versions": [
    "3"
  ],
  "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html",
  "extra_source_urls": [
    "https://endoflife.date/amazon-aurora-mysql"
  ],
  "vendor_ref": "amazon-aurora-mysql@3",
  "last_checked_at": "2026-11-12T09:55:40.805Z",
  "created_at": "2026-11-13T13:36:44.208Z",
  "updated_at": "2026-11-13T13:36:44.208Z",
  "url": "https://eolwatch.dev/items/aws-aurora-mysql-version-3-extended-support-end-of-support",
  "short_url": "https://eolwatch.dev/i/co",
  "markdown_url": "https://eolwatch.dev/items/aws-aurora-mysql-version-3-extended-support-end-of-support.md",
  "json_url": "https://eolwatch.dev/items/aws-aurora-mysql-version-3-extended-support-end-of-support.json",
  "estate_check": {
    "resource_types": [
      "aws_rds_cluster"
    ],
    "fields": [
      "engine",
      "engine_version_actual",
      "engine_version"
    ],
    "inputs": [
      "Terraform state or plan (JSON)"
    ]
  }
}