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!

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...