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!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...