Amazon OpenSearch Service announces End-of-Sale (EOS) and End-of-Life (EOL) dates for Elasticsearch and OpenSearch variants

Provides expert support for 19 distinct variations of open-source Elasticsearch, as well as 11 unique implementations of. With the passage of time, we’ve continually enhanced our existing engine variants by incorporating numerous stability, resiliency, and safety features, thereby enabling customers to maximize their value from OpenSearch Service. As software programs age, ensuring they continue to meet rigorous safety and compliance standards is crucial. The majority of legacy variants supported in OpenSearch Service, equivalent to Elasticsearch versions 1.5 and 2.3, are reliant on third-party dependencies that are no longer receiving active support. By migrating to our latest engine iterations, customers can maximize their returns by leveraging the benefits of cutting-edge options, enhanced value-to-cost ratios, and upgraded safety features in OpenSearch.

We are currently projecting timelines for the conclusion of Commonplace Help and Prolonged Help support for legacy Elasticsearch versions up to 6.7, Elasticsearch versions 7.1 through 7.8, OpenSearch versions from 1.0 through 1.2, and OpenSearch versions 2.3 through 2.9 available on Amazon OpenSearch Service? Commonplace Support receives routine updates with standard bug fixes and security patches at a fixed price per instance hour. Prolonged Support, meanwhile, prioritizes critical security fixes and operating system patches, offering additional stability for an incremental fee tied to normalized usage hours. To ensure seamless continuity, we must facilitate timely access to critical security updates for a sufficient duration, thereby empowering clients to migrate smoothly to future engine upgrades while they prepare for the transition. For additional information regarding Extended Assistance, refer to our dedicated webpage.

The following features are no longer supported as of Elasticsearch 7.17:

Commonplace help: This feature was used to retrieve information about a specific type or group of types in the Elasticsearch documentation.
Prolonged help: This feature allowed users to request more detailed information about a specific topic or query.

SKIP

See below for the end-of-life schedule for legacy Elasticsearch versions available on OpenSearch Service, including Commonplace Help and Prolonged Help dates. We strongly recommend that clients utilizing various Elasticsearch iterations upgrade to the latest OpenSearch versions. All Elasticsearch versions will receive a minimum of 12 months of Extended Support, with Model 5.6 receiving 36 months of Extended Support. Once support for a model expires, the associated domains will no longer receive bug fixes or security updates.

The following common and prolonged help texts are designed for OpenSearch variations:

**Commonplace Help**

* **Setup**: To start using OpenSearch, you need to set up your environment with the required dependencies. Follow our installation guide to get started.
* **Indexing data**: Indexing data into OpenSearch involves creating an index, mapping your data, and then uploading it. You can use our SDKs or APIs to accomplish this.
* **Querying data**: Once you’ve indexed your data, you can query it using our robust search capabilities. Use our query language to filter, sort, and retrieve the results that matter most.

**Prolonged Help**

* **Index Configuration**: To optimize index performance, consider adjusting settings like shard count, replica count, and refresh intervals. Consult our documentation for more information.
* **Data Mapping**: When mapping your data, think about the relationships between fields and how they’ll affect search results. Use our mapping guidelines to ensure optimal querying.
* **Query Best Practices**: To get the most out of OpenSearch, follow best practices like using relevant query types, applying filters, and leveraging faceting for better results. Consult our query guide for more information.

We commit to providing at least 12 months of Community Support for OpenSearch variations operating on Amazon OpenSearch Service, with a minimum of 12 months of support extending from the end-of-life date for the corresponding upstream open-source OpenSearch version, or from the release date of the subsequent minor version on OpenSearch Service, whichever period is longer. OpenSearch versions will receive a minimum of 12 months of Extended Support following the end of Mainstream Support, ensuring a continued focus on security and stability throughout their lifecycle. Test the open-source OpenSearch.

Please refer to Desk 2 below for the completion dates of Commonplace Help and Extended Help for various OpenSearch versions available on OpenSearch Service. To receive future updates on changes to Commonplace Help and Extended Help, follow.

We strongly recommend updating your domains to leverage the latest features and improvements in the OpenSearch service, ensuring optimal performance and maximizing the value derived from this powerful tool. Minor model upgrades on OpenSearch typically unfold seamlessly, as they rarely involve breaking changes; therefore, we strongly recommend migrating to the latest minor version, or one that has not yet reached its end-of-life milestone. If you’re currently utilizing OpenSearch 1.2, consider upgrading to OpenSearch 1.3, which is the last minor version in the 1.x series and will continue to receive support from both the open-source community and AWS. When upgrading from an older Elasticsearch version (6.x or 7.x), consider migrating to a more recent model such as 6.8 or 7.10 for selection.

Numerous techniques exist to enhance a cluster to a modern model, with varying approaches dependent on the current model in use and the desired upgraded model. For more information on how to upgrade your area to a cutting-edge model, see the comprehensive guide below. You can also use this option for upgrading to newer versions.

Domains utilising services under Extended Support may incur a flat additional fee per normalised hourly rate (NHR)? Within the US East (Northern Virginia) Amazon Web Services area, the cost is $0.0065 per National Institute of Health unit. Please see actual pricing by area.

The Net Instruction Hours (NIH) are calculated based on the instance size and the number of instance hours. For example, for a 24-hour m7.giant.search instance in the US EAST (North Virginia) region, priced at $0.068 per hour (on-demand), the total cost would be $1.632 ($0.068 × 24). For clients utilizing a model in Prolonged Help, an additional fee of $0.0065 per NIH will apply, calculated as $0.0065 multiplied by 24 (occasion hours) and 2 (medium-sized situation normalization factor), resulting in a total cost of $0.312 for 24 hours of Prolonged Help. The total cost for 24-hour usage is calculated by combining the standard hourly rate with the Extended Assistance fee, totaling $1.944 (comprising $1.632 and $0.312, minus storage costs). The OpenSearch Service demonstrates various normalization challenges across diverse occasion sizes at its next desk.

Abstract

Throughout various iterations of OpenSearch, we continually introduce innovative capabilities across multiple dimensions, including enhanced features, improved performance, heightened resilience, and bolstered security measures. We strongly recommend migrating from existing OpenSearch variants to maximize the benefits of using OpenSearch Service. For inquiries regarding Commonplace and Prolonged Help options, please refer to our comprehensive documentation. For additional questions, contact .

Concerning the authors

Serves as a Senior Supervisor of Product Development for Amazon’s OpenSearch Service within Amazon Net Companies. With nearly two decades of experience spanning diverse fields including analytics, search, cloud computing, community safety, and telecommunications.

Serving as a senior technical program supervisor at Amazon Net Services, he is singularly focused on spearheading innovative initiatives and tackling intricate problem-solving endeavors. He collaborates diligently with teams and customers to ensure seamless operations and achieve more with fewer resources. Exteriorly, his leisure pursuits include trekking and a variety of team sports.

Serving as Senior Principal Options Architect at Amazon Net Companies, based primarily in Palo Alto, California. Jon provides expert guidance to a diverse range of clients who rely on OpenSearch and Amazon OpenSearch Service for their search and log analytics workloads, helping them successfully migrate these critical functions to the secure and scalable AWS Cloud environment. Prior to joining AWS, Jon’s experience as a software developer spanned four years of developing a large-scale ecommerce search engine. Jon holds a Bachelor of Arts degree from the University of Pennsylvania, as well as Master of Science and Doctor of Philosophy degrees in Computer Science and Artificial Intelligence from Northwestern University.