Deadline extended for end of support for TLS 1.0/1.1 and unencrypted (plaintext HTTP) traffic to Elasticsearch Service | Elastic Blog
Engineering

Deadline extended for end of support for TLS 1.0/1.1 and unencrypted (plaintext HTTP) traffic to Elasticsearch Service

As COVID19 continues to affect the world, we have decided to extend the timeline for removing support for TLS 1.0/1.1 and unencrypted traffic for clients sending data to Elasticsearch Service by another three months to July 21, 2020 from the initial date of April 21, 2020.

In addition to extending the date, we have decided to do a trial run (by removing support for plaintext HTTP and TLS 1.0/1.1) prior to the final cutoff. We aim to do this between June 29 and July 10, 2020 for a short period of time (about 2 days) and will keep the status page updated. This will allow you to identify clients that might not yet be updated or even identified to be updated if you have monitoring setup.

What do you need to do?

In order to understand if your clients need to be updated, read the blog post we published in January that has details on the client versions that support TLS 1.2. If you are still unable to determine if your clients support TLS 1.2, please reach out to our support team via our support portal or by emailing support@elastic.co.

We understand that the current pandemic has no deadline, and we are keeping our eyes and ears open to what our community needs. We will align and evolve plans accordingly. If you have any further questions, please email support@elastic.co.

Thanks for being a valued Elasticsearch Service customer.