Getting an error running osquery inside k8s on aws...
# generalr
Ryan
11/14/2019, 8:30 PMGetting an error running osquery inside k8s on aws.
Copy code
Exception making HTTP request to URL (<http://169.254.169.254/latest/meta-data/iam/security-credentials>): Invalid URLt
theopolis
11/15/2019, 7:59 PM
My knowledge of cloud infra is so poor, so please pardon if I'm way off here: I heard the local metadata endpoints can be flaky and that osquery should implement some re-checking/etc.
r
Ryan
11/15/2019, 8:01 PMits a bug in osquery in how it handles the redirect its receiving
Ryan
11/15/2019, 8:01 PMt
theopolis
11/15/2019, 8:02 PM
ah, I think this is easily fixable -- there is a "follow redirects" option for the internal HTTP client. Can we trace where in code the request is made?
r
Ryan
11/15/2019, 8:04 PMyeah its the http_client code
t
theopolis
11/15/2019, 8:06 PM
I replied to the issue, I think I see the problem and the fix is easy.
r
Ryan
11/15/2019, 8:12 PMawesome good to know
Ryan
11/15/2019, 8:14 PMhrm not sure your response is accurate. i dont think its an issue with follow redirects happening as i can see that it happens, its that the http_client attempts to redirect to a non valid URL
Ryan
11/15/2019, 8:15 PMRyan
11/15/2019, 8:16 PMthat Location is just a path which is then sent on L421 to uri. uri then bombs because a location doesnt match the URL regex
t
theopolis
11/15/2019, 9:21 PM
I see, perhaps we are not implementing the http client correctly
r
Ryan
11/18/2019, 1:44 PMjust saw your PR, thanks. am pulling it and building it myself to verify it fixes the issue.
👍 1
t
theopolis
11/19/2019, 12:07 AM
hey @Ryan, did you have a chance to test https://github.com/osquery/osquery/pull/6049
r
Ryan
11/19/2019, 12:08 AMYeah commented on the issue. Looks good
t
theopolis
11/19/2019, 12:09 AM
ah, sorry, missed that!
theopolis
11/19/2019, 12:09 AM
thank you!
2 Views