Amazon Neptune is a fast, reliable, fully managed graph database service that makes it easy to build and run applications that work with highly connected datasets. It supports multiple property-graph query languages: Apache TinkerPop, Gremlin, openCypher, and SPARQL. Neptune powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, and network security.
| Release | Security Support | Latest |
|---|---|---|
| 1.2.1.1 |
Ends
in 10 months (06 Mar 2025)
|
1.2.1.1
(11 Mar 2024)
|
| 1.3.1.0 |
Ends
in 1 year and 7 months (30 Nov 2025)
|
1.3.1.0
(06 Mar 2024)
|
| 1.3.0.0 |
Ends
in 1 year and 7 months (30 Nov 2025)
|
1.3.0.0
(15 Nov 2023)
|
| 1.2.1.0 |
Ends
in 10 months (06 Mar 2025)
|
1.2.1.0.R7
(06 Oct 2023)
|
| 1.2.0.2 |
Ends
in 10 months (06 Mar 2025)
|
1.2.0.2.R6
(12 Sep 2023)
|
| 1.2.0.1 |
Ends
in 10 months (06 Mar 2025)
|
1.2.0.1.R3
(27 Sep 2023)
|
| 1.2.0.0 |
Ends
in 10 months (06 Mar 2025)
|
1.2.0.0.R4
(29 Sep 2023)
|
| 1.1.1.0 |
Ends
in 6 months (31 Oct 2024)
|
1.1.1.0.R7
(23 Jan 2023)
|
| 1.1.0.0 |
Ends
in 6 months (31 Oct 2024)
|
1.1.0.0.R2
(16 May 2022)
|
| 1.0 |
Ended
1 year and 2 months ago (30 Jan 2023)
|
1.0.5.1.R4
(16 May 2022)
|
Neptune engine versions almost always reach their end-of-life at the end of a calendar quarter. Exceptions occur only when important security or availability issues arise.
In general, Neptune engine versions continue to be available as follows:
- Minor engine versions: remain available for at least 6 months following their release.
- Major engine versions: remain available for at least 12 months following their release.
New engine versions are announced on the Changes and Updates page, as well as published via an RSS feed. It takes several days for a new release to become available in every region.
At least 3 months before an engine version reaches its End-of-life, AWS sends an automated email notification and posts the same message to the AWS Health Dashboard. This will include details about the update (upgraded version, impact on clusters, recommended actions).
When an engine version reaches its end of life, customers can no longer create new clusters or instances using that version, nor will autoscaling be able to create instances using that version. An engine version that reaches its end of life will automatically be upgraded during a maintenance window.
Legacy Engines are not considered Generally Available, and AWS guarantees no support for the same. Databases running on a Legacy Engine are subject to Service Level Agreement (SLA) Exceptions.
| Engine Version | Upgrade To |
|---|---|
| 1.2.1.1 | 1.3.0.0 |
| 1.3.1.0 | N/A |
| 1.3.0.0 | 1.3.1.0 |
| 1.2.1.0 | 1.3.0.0 |
| 1.2.0.2 | 1.3.0.0 |
| 1.2.0.1 | 1.3.0.0 |
| 1.2.0.0 | 1.3.0.0 |
| 1.1.1.0 | 1.2.1.0 |
| 1.1.0.0 | 1.1.1.0 |
| 1.0 | 1.1.0.0 |
More information is available on the Amazon Neptune website.
You should be running one of the supported release numbers listed above in the rightmost column.
aws neptune describe-db-clusters --db-cluster-identifier your-neptune-db-identifier --filters Name=engine,Values=neptune
You can submit an improvement to this page
on GitHub
.
This page has a corresponding
Talk Page.
A JSON version of this page is available at /api/amazon-neptune.json. See the API Documentation for more information. You can subscribe to the iCalendar feed at /calendar/amazon-neptune.ics.