Final notice: Removing support for TLS 1.1, TLS 1.0 and plaintext access on Oct 8 2020

Scheduled Maintenance Report for ESS (Public)

Completed

This work is completed at this time. We are now working to resolve the issues reported around TLS negotiation.

Posted Oct 08, 2020 - 16:33 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted Oct 08, 2020 - 14:45 UTC

Scheduled

We are continuing progress with work to make the final change to stop supporting TLS 1.1, TLS 1.0 and plaintext access until 16:00 pm UTC in us-west-1, us-west-2, us-east-1 and eu-west-1.

Customers using clients that were still sending data to their deployments on Elasticsearch Service using TLS 1.0/1.1 or plain-text HTTP, have received a series of emails and notifications on this topic.

To ensure continued service, you must update any client that is using TLS 1.1, TLS 1.0 or plaintext communication. Please read the blog post that has details on the client versions that support TLS 1.2.

Posted Oct 08, 2020 - 14:43 UTC

This scheduled maintenance affected: GCP Oregon (us-west1) (Elasticsearch connectivity: GCP us-west1, Kibana connectivity: GCP us-west1, APM connectivity: GCP us-west1), AWS Oregon (us-west-2) (Elasticsearch connectivity: AWS us-west-2, Kibana connectivity: AWS us-west-2, APM connectivity: AWS us-west-2), AWS Ireland (eu-west-1) (Elasticsearch connectivity: AWS eu-west-1, Kibana connectivity: AWS eu-west-1, APM connectivity: AWS eu-west-1), and AWS N. Virginia (us-east-1) (Elasticsearch connectivity: AWS us-east-1, Kibana connectivity: AWS us-east-1, APM connectivity: AWS us-east-1).