# general

Zach Zeid

09/30/2019, 5:11 PM
is there a way to enable verbosity even more to be able to see the underlying AWS call for kinesis? It appears it's not connecting to the endpoint, but doesn't provide anymore information
So it looks like the primary issue was that I was running 3.3.0 as it was what we were running in our environment. It appears the primary issue was how the AWS SDK that osquery uses changed how they make HTTP requests to their endpoints (from google searching, this appears common from older versions of osquery.) Upgrading to osquery 4.0.2 resolved that issue and does connect and sending logs now. Is my assumption here correct?