Amazon Neptune 1.1 and 1.2 end of life: Dec 4, 2026
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.
Last checked against AWS documentation:
Versions ending Dec 4, 2026
| Engine version | End of life | AWS upgrade target |
|---|---|---|
| Neptune 1.1.1.0 | Dec 4, 2026 | 1.2.1.0 |
| Neptune 1.2.0.0 | Dec 4, 2026 | 1.3.0.0 |
| Neptune 1.2.0.1 | Dec 4, 2026 | 1.3.0.0 |
| Neptune 1.2.0.2 | Dec 4, 2026 | 1.3.0.0 |
| Neptune 1.2.1.0 | Dec 4, 2026 | 1.3.0.0 |
| Neptune 1.2.1.1 | Dec 4, 2026 | 1.3.0.0 |
| Neptune 1.2.1.2 | Dec 4, 2026 | 1.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
| Target | End of life |
|---|---|
| Neptune 1.3.0.0 to 1.4.6.1 | Mar 6, 2027 |
| 1.4.6.2 to Neptune 1.4.7.1 | Jun 3, 2027 |
| Neptune 1.4.8.0 | Oct 27, 2027 |
| Neptune 1.4.8.1, Neptune 1.5.0.0 | Not 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
- EKS extended support cost calculator
- RDS & Aurora extended support pricing
- RDS MySQL 8.0 end of support
- RDS PostgreSQL end-of-support dates
- Lambda runtime deprecation schedule
- ElastiCache for Redis OSS end of support
- OpenSearch & Elasticsearch end of support
- OpenSearch extended support fees from Nov 7, 2026
- Lambda Python 3.10 deprecation (Oct 31, 2026)
- RDS MariaDB 10.6 end of support (Dec 31, 2026)
- EKS 1.31 end of extended support (Nov 26, 2026)
- RDS PostgreSQL 14 end of standard support (Feb 28, 2027)
- Lambda .NET 8 deprecation (Nov 10, 2026)