Your Logstash instance SSL Certificate is due to expire at 23.59 (UTC) on the 21st November 2022.

We will need to rotate the certificate used on your Logstash endpoints before the current certificate expires.

If you are sending over a SSL/TLS connection and have configured verification against a specific certificate you will need to update your configuration.

Configurations likely to need updating include sending from Syslog and older Filebeat installations (typically v1.3 or below) configurations - how to update your configurations

If you take no further action we will be upgrading all stacks from the 15th November.

Expected time for the upgrade to complete is less than 2 minutes.

Further information and FAQs can be found in the Help Centre.



I haven't configured a certificate anywhere?

Our old and new certificates are trusted by default in most systems, if you have not configured a specific certificate, you should not need to do anything.

Why do your need to do this?

Logit signed SSL certificates are typically valid for 1 year, our current certificate is nearing its expiry date and the root certificate has not changed on our new certificate

What happens if I do not replace the certificate?

The certificate needs replacing before it expires. 

The exact consequences of not replacing the certificate would depend on the specific software sending your logs but typically your sender would refuse to establish any new connections to logstash after the certificate expires.

Can you check my configuration for me?

Contact us via support or get in touch with your account manager and we will discuss further options.

If I’m sending from an amazon s3 bucket do I need to do anything? 

No changes should be required, although we will still need to restart your Logstash instance to upgrade the certificate.

If I’m sending directly to Elasticsearch do I need to do anything? 

No, the certificate has already been updated.

If I'm sending via do I need to do anything? 

No, the certificate has already been updated.

How do i know i have the correct intermediate certificate?

The md5 hash of the new intermediate.crt is 5945bad341623ae14991e09ffe851725

md5sum /etc/rsyslog.d/keys/ca.d/
md5 /etc/rsyslog.d/keys/ca.d/
Did this answer your question?