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
The scheduled maintenance has been completed.
Posted Oct 08, 2020 - 16:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Oct 08, 2020 - 08:02 UTC
Update
We will be undergoing scheduled maintenance during this time.
Posted Oct 07, 2020 - 21:47 UTC
Scheduled
In January this year we announced our plan to stop supporting TLS 1.0/1.1 and unencrypted traffic to Elasticsearch Service. Due to COVID19, we extended this timeline to July 2020, and then based on data decided to give customers another extension until October 2020.

We are going to make the final change to stop supporting TLS 1.1, TLS 1.0 and plaintext access on Oct 8 2020 between 8:00 am and 14:00 pm UTC.

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 07, 2020 - 21:34 UTC
This scheduled maintenance affected: GCP Finland (europe-north1) (Elasticsearch connectivity: GCP europe-north1, Kibana connectivity: GCP europe-north1, APM connectivity: GCP europe-north1), GCP London (europe-west2) (APM connectivity: GCP europe-west2, Kibana connectivity: GCP europe-west2, Elasticsearch connectivity: GCP europe-west2), GCP Mumbai (asia-south1) (Elasticsearch connectivity: GCP asia-south1, Kibana connectivity: GCP asia-south1, APM connectivity: GCP asia-south1), GCP Netherlands (europe-west4) (APM connectivity: GCP europe-west4, Elasticsearch connectivity: GCP europe-west4, Kibana connectivity: GCP europe-west4), AWS Tokyo (ap-northeast-1) (Elasticsearch connectivity: AWS ap-northeast-1, Kibana connectivity: AWS ap-northeast-1, APM connectivity: AWS ap-northeast-1), GCP Frankfurt (europe-west3) (Elasticsearch connectivity: GCP europe-west3, Kibana connectivity: GCP europe-west3, APM connectivity: GCP europe-west3), AWS Frankfurt (eu-central-1) (Kibana connectivity: AWS eu-central-1, Deployment snapshots: AWS eu-central-1, Elasticsearch connectivity: AWS eu-central-1), AWS Seoul (ap-northeast-2) (Kibana connectivity: AWS ap-northeast-2, Deployment hosts: AWS ap-northeast-2, Deployment metrics: AWS ap-northeast-2), AWS São Paulo (sa-east-1) (Elasticsearch connectivity: AWS sa-east-1, Kibana connectivity: AWS sa-east-1, APM connectivity: AWS sa-east-1), GCP Iowa (us-central1) (Elasticsearch connectivity: GCP us-central1, Kibana connectivity: GCP us-central1, APM connectivity: GCP us-central1), GCP Oregon (us-west1) (Elasticsearch connectivity: GCP us-west1, Kibana connectivity: GCP us-west1, APM connectivity: GCP us-west1), GCP Belgium (europe-west1) (Kibana connectivity: GCP europe-west1, APM connectivity: GCP europe-west1), AWS N. California (us-west-1) (Elasticsearch connectivity: AWS us-west-1, Kibana connectivity: AWS us-west-1, APM connectivity: AWS us-west-1), 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), AWS N. Virginia (us-east-1) (Elasticsearch connectivity: AWS us-east-1, Kibana connectivity: AWS us-east-1, APM connectivity: AWS us-east-1), AWS Singapore (ap-southeast-1) (Elasticsearch connectivity: AWS ap-southeast-1, Kibana connectivity: AWS ap-southeast-1, APM connectivity: AWS ap-southeast-1), AWS Sydney (ap-southeast-2) (Elasticsearch connectivity: AWS ap-southeast-2, APM connectivity: AWS ap-southeast-2, Kibana connectivity: AWS ap-southeast-2), and AWS London (eu-west-2) (Elasticsearch connectivity: AWS eu-west-2, Kibana connectivity: AWS eu-west-2, APM connectivity: AWS eu-west-2).