Engine releases for Amazon Neptune - Amazon Neptune
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Engine releases for Amazon Neptune

Amazon Neptune releases engine updates regularly.

You can determine which engine release version you currently have installed using the instance-status API or the Neptune console. The version number tells you whether you are running an original release (implicitly .R1), or a later patch (.R2, .R3, and so on). For more information about release numbering, see Engine version numbers.

Note

For minor engine releases from 1.0.1.0 onwards, the implicit starting version is .R1, and subsequent patches are .R2, .R3, and so on.

For information about how to update your Neptune DB engine and other information about updates, see Neptune engine updates.

The table below lists all the engine releases since 1.0.1.0, along with information about version end-of-life. You can use the dates in this table to plan your testing and upgrade cycles.

Version Major version Minor version Status Released End of life

1.2.0.0

1.2

0.0

active

2022-05-31

2024-07-31

1.1.1.0

1.1

1.0

active

2022-04-19

2024-07-31

1.1.0.0

1.1

0.0

active

2021-11-19

2023-01-31

1.0.5.1

1.0

5.1

active

2021-10-01

2022-10-31

1.0.5.0

1.0

5.0

active

2021-07-27

2022-10-31

1.0.4.2

1.0

4.2

active

2021-06-01

2022-10-31

1.0.4.1

1.0

4.1

active

2020-12-08

2022-10-31

1.0.4.0

1.0

4.0

active

2020-10-12

2022-10-31

1.0.3.0

1.0

3.0

active

2020-08-03

2022-10-31

1.0.2.2

1.0

2.2

active

2020-03-09

2022-07-29

1.0.2.1

1.0

2.1

active

2019-11-22

2022-07-29

1.0.2.0

1.0

2.0

deprecated

2019-11-08

2020-05-19

1.0.1.2

1.0

1.2

deprecated

2019-10-15

1.0.1.1

1.0

1.1

deprecated

2019-08-13

1.0.1.0.*

1.0

1.0.*

deprecated

2019-07-02 and before

Planning for Amazon Neptune engine version life-span

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.

When an engine version reaches its end of life, you will be required to upgrade your Neptune database to a newer version.

In general, Neptune engine versions continue to be available as follows:

  • Minor engine versions: Minor engine versions remain available for at least 6 months following their release.

  • Major engine versions: Major engine versions remain available for at least 12 months following their release.

At least 3 months before an engine version reaches its end of life, Amazon will send an automated email notification to the email address associated with your Amazon account and post the same message to your Amazon Health Dashboard. This will give you time to plan and prepare to upgrade.

Starting 1 month before an engine version reaches its end of life, you will no longer be able to create new clusters or instances using that version, nor will autoscaling be able to create instances using that version.

If you have set the AutoMinorVersionUpgrade field to true in the writer DB instance of a DB cluster, Neptune automatically updates the minor engine version of the cluster to the latest minor version whenever possible thereafter.

An engine version that actually reaches its end of life will automatically be upgraded during a maintenance window. The message sent to you 3 months before the engine version's end of life will contain details about what this automatic update would involve, including the version to which you would be automatically upgraded, the impact on your DB clusters, and actions that we recommend.