All Apps and Add-ons

AWS cloudwatch logs stop reporting after Server gets restarted

kdimaria
Communicator

I have everything set up following this document: https://www.splunk.com/blog/2017/02/03/how-to-easily-stream-aws-cloudwatch-logs-to-splunk.html

It was working fine and always pushing the logs to Splunk but every time the server gets restarted, the logs stop being sent. But, if the server is restarted again after that, it's fine. The error message in cloudwatch says like ":rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed" and "SSL routines:ssl3_get_key_exchange:bad signature:.", not really sure how to make it so that if the server is restarted that it doesn't affect the cloudwatch logs from being pushed to Splunk.

0 Karma
Get Updates on the Splunk Community!

Your Guide to Splunk Digital Experience Monitoring

A flawless digital experience isn't just an advantage, it's key to customer loyalty and business success. But ...

Data Management Digest – November 2025

  Welcome to the inaugural edition of Data Management Digest! As your trusted partner in data innovation, the ...

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...