Logz.io: Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central
Timeline of updates
- resolved
We’ve completed a retroactive maintenance operation to address a renewal related to an outdated certificate that may affect customers using Filebeat-based integrations in the US-east-1 and EU-central regions.
Only customers using Filebeat integrations that rely on outdated versions are potentially impacted.
If you’re experiencing issues with Filebeat log shipping, please update your Filebeat configuration to trust the latest certificate chain. You can download the updated certificate and follow our integration guide to apply the necessary changes.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
40e9e8f56c4609fe…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Logz.io, started 2025-07-28 09:22 UTC, resolved after -4102 min, 1 update(s).
- Title
- Certificate renewal for Filebeat-based Integrations in us-east-1 and eu-central
- Vendor
- Logz.io
- Date
- URL
- https://rewindex.com/company/logz-io/incidents/jn4t552d7cs1
Logz.io profileRecent Logz.io incidentsAll outages on July 28, 2025Logz.io in July 2025MarkdownJSON