Notification

POSSIBLE ACTION REQUIRED

Your Logstash instance SSL Certificate is due to expire on the 12th October 2019.

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 intermediate 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 4th October.

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

If you need to test any configuration options there is a shared test Logstash endpoint available - how to use the test endpoint.

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

Regards

Logit.io

FAQ's

I haven't configured an intermediate 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 2 or 3 years, our current certificate is nearing its expiry date and the intermediate certificate has changed on our new certificate

What happens if I do not replace the intermediate 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? 

The certificate will also be changing - but the intermediate certificate used will not be changing. It is unlikely that you will need to edit any settings.

If I'm sending via api.logit.io do I need to do anything? 

The certificate will also be changing - but the intermediate certificate used will not be changing. It is unlikely that you will need to edit any settings. 

How do i know i have the correct intermediate certificate?

The md5 hash of the new intermediate.crt is 45d79caee571b20ed5c21d51294a138b

Linux:
md5sum /etc/rsyslog.d/keys/ca.d/star.logit.io.crt
MacOS:
md5 /etc/rsyslog.d/keys/ca.d/star.logit.io.crt
Did this answer your question?