EOL.Wiki EOL.Wiki
← ← Back to all products

Amazon Opensearch

Active
Other Latest Version: 3.1 Latest Release: N/A

Versions

14

Latest Version

N/A

Active Support

7

EOL

7

Lifecycle Timeline

Today
3.1
3.1
2.19
2.19
2.17
2.17
2.15
2.15
2.13
2.13
2.11
2.11
2.9
2.9
2.7
2.7
2.5
2.5
2.3
2.3
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.1Sep 9, 2025-No-No
Active
2.19Apr 30, 2025-No-No
Active
2.17Nov 13, 2024-No-No
Active
2.15Oct 11, 2024-No-No
Active
2.13May 21, 2024-No-No
Active
2.11Nov 17, 2023-No-No
Active
2.9Oct 2, 2023-Nov 7, 2025-No
EOL
2.7Jul 10, 2023-Nov 7, 2025-No
EOL
2.5Mar 13, 2023-Nov 7, 2025-No
EOL
2.3Nov 15, 2022-Nov 7, 2025-No
EOL
1.3Aug 16, 2022-No-No
Active
1.2Apr 4, 2022-Nov 7, 2025-No
EOL
1.1Jan 4, 2022-Nov 7, 2025-No
EOL
1.0Sep 8, 2021-Nov 7, 2025-No
EOL

Frequently Asked Questions

Which versions of Amazon Opensearch have reached end of life?
The following Amazon Opensearch versions have reached end of life and no longer receive security updates: 2.9, 2.7, 2.5, 2.3, 1.2, 1.1, 1.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Amazon Opensearch 2.9?
Amazon Opensearch 2.9 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Amazon Opensearch?
The latest version of Amazon Opensearch is 3.1, released in the 3.1 release cycle.
How many versions of Amazon Opensearch are currently supported?
Amazon Opensearch currently has 7 actively supported version(s): 3.1, 2.19, 2.17, 2.15, 2.13, 2.11, 1.3.
When does Amazon Opensearch 3.1 reach end of life?
Amazon Opensearch 3.1 does not have a specific end-of-life date announced yet.
What should I do when Amazon Opensearch reaches end of life?
When a Amazon Opensearch version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.