Home / Guides

Amazon Neptune 1.1 and 1.2 end of life: Dec 4, 2026

THE TAKEAWAY

Amazon Neptune engine versions 1.1.1.0 and 1.2.0.0 through 1.2.1.2 reach end of life on Dec 4, 2026. After that you can't create clusters or instances on them, and AWS automatically upgrades remaining clusters during a maintenance window.

Versions ending Dec 4, 2026What happens on Dec 4, 2026Where to upgradeFind and upgrade your clusters

Last checked against AWS documentation:

Versions ending Dec 4, 2026

Engine versionEnd of lifeAWS upgrade target
Neptune 1.1.1.0Dec 4, 20261.2.1.0
Neptune 1.2.0.0Dec 4, 20261.3.0.0
Neptune 1.2.0.1Dec 4, 20261.3.0.0
Neptune 1.2.0.2Dec 4, 20261.3.0.0
Neptune 1.2.1.0Dec 4, 20261.3.0.0
Neptune 1.2.1.1Dec 4, 20261.3.0.0
Neptune 1.2.1.2Dec 4, 20261.3.0.0

"Upgrade to" is the version AWS lists in its engine releases table. Note that 1.2.1.0 also ends Dec 4, 2026, so 1.1.1.0 clusters need to keep going to 1.3 or later.

What happens on Dec 4, 2026

  • You can no longer create new clusters or instances on these versions, and autoscaling can't create instances on them either.
  • Clusters still on an end-of-life version are automatically upgraded during a maintenance window. AWS says the notice it sends at least 3 months before end of life spells out which version you'll be moved to and the impact.
  • AWS's Neptune lifecycle page describes no extended-support option: at end of life you are required to upgrade. AWS also says Legacy Engines are not Generally Available and are subject to SLA exceptions.

Where to upgrade

TargetEnd of life
Neptune 1.3.0.0 to 1.4.6.1Mar 6, 2027
1.4.6.2 to Neptune 1.4.7.1Jun 3, 2027
Neptune 1.4.8.0Oct 27, 2027
Neptune 1.4.8.1, Neptune 1.5.0.0Not announced (TBD)

1.3.x and early 1.4.x end Mar 6, 2027, only three months later, so aim for 1.4.8.1 or 1.5.0.0 if you can.

Find and upgrade your clusters

aws neptune describe-db-clusters \
  --query "DBClusters[?Engine=='neptune'].[DBClusterIdentifier,EngineVersion]" --output table

AWS says major engine releases must always be installed manually, and recommends the Neptune Blue-Green deployment solution to minimize downtime. To upgrade right away by CLI:

aws neptune modify-db-cluster \
  --db-cluster-identifier my-cluster \
  --engine neptune \
  --engine-version 1.4.8.1 \
  --apply-immediately

Always pass --engine-version; AWS warns that otherwise you may not get the version you expect. If you use custom parameter groups, also pass --db-cluster-parameter-group-name and --db-instance-parameter-group-name. Run per Region and test on a clone or Blue-Green copy first.

Sources

FAQ

When do Neptune 1.1 and 1.2 reach end of life?

Dec 4, 2026, for engine versions 1.1.1.0, 1.2.0.0, 1.2.0.1, 1.2.0.2, 1.2.1.0, 1.2.1.1 and 1.2.1.2, per the AWS Neptune engine releases page.

What happens to my Neptune cluster after Dec 4, 2026?

You can no longer create clusters or instances on those versions, and AWS automatically upgrades the cluster during a maintenance window.

Can I pay to stay on Neptune 1.2?

AWS's Neptune engine lifecycle documentation describes no extended-support option. When a version reaches end of life you are required to upgrade.

Which Neptune version should I upgrade to?

1.4.8.1 or 1.5.0.0 have no announced end of life yet. 1.3.0.0 through 1.4.6.1 end Mar 6, 2027.

More guides