Share this post:
As you may know, the End of Life (EOL) date for Elasticsearch 5.6 is fast approaching. This means that on March 11, 2019, Elasticsearch is ending support for minor releases of version 5.6.x. As a consequence, you should plan on migrating your databases over to Elasticsearch version 6.x and making any modifications to your applications that may need to be made.
IBM Cloud Databases for Elasticsearch support for version 5.6
In order to keep your databases secure and compliant on IBM Cloud, IBM Cloud Databases for Elasticsearch is going to continue to support version 5.6 for 180 days starting today. That means that for 180 days, you’ll be able to continue to provision Elastisearch version 5.6, but this comes with a caveat:
We reserve the right to end support at our discretion if a security vulnerability is discovered during the 180-day window. This means that we may need to shut down those Elasticsearch deployments and remove them from our system since they would not meet compliance regulations.
Therefore, the way forward is to stop provisioning Databases for Elasticsearch 5.6 and start migrating your existing deployments over to Databases for Elasticsearch version 6.x. Additionally, if you’re using Compose for Elasticsearch 5.6, our recommendation is to migrate to Databases for Elasticsearch 6.x since it’s a HIPAA-ready and GDPR compliant database.
We’ve released a guide that shows you how to securely migrate your Compose for Elasticsearch 5.6 database over to Databases for Elasticsearch version 6.x.: “A How-To for Migrating Elasticsearch to IBM Cloud Databases for Elasticsearch.” If you’re already using Databases for Elasticsearch version 5.6 and want to upgrade to 6.x, this migration guide is relevant to you also so that you can upgrade to the latest version of Databases for Elasticsearch on IBM Cloud.