This repository has been archived by the owner on Sep 17, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 796
Security Monkey not loading any data in the UI. However it scans my account on the EC2 console when I run "monkey find_changes". #1126
Labels
Comments
I've had this behaviour when the application is unable to write to it's log
files. I set up proper logfile rotation and that seemed to have fixed it
for me. Not sure if this is the same issue for you, but I thought I'd share
…On Mon, 22 Oct 2018 at 12:32, Ritwik Sinha ***@***.***> wrote:
I have setup Security Monkey on our AWS infra using the official guide but
the data is not being populated on the UI.
When I run "monkey find_changes" on the EC2, I see my account being
scanned but there is still no data on the Security Monkey UI.
I double checked the IAM Roles and Policies and couldn't find any issue
there.
HELP WOULD BE HIGHLY APPREICIATED.
A massive thanks to the creators of this btw!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1126>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AIkOhVMbOedXb4K6yir5gd2miilkqGnRks5unay4gaJpZM4XzNwv>
.
|
A few things:
It would be recommended too to include the commit hash and the branch that you used. |
Also, please try the steps in the troubleshooting guide and also review previously filed issues as this is a common issue that users experience. |
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have setup Security Monkey on our AWS infra using the official guide but the data is not being populated on the UI.
When I run "monkey find_changes" on the EC2, I see my account being scanned but there is still no data on the Security Monkey UI.
I double checked the IAM Roles and Policies and couldn't find any issue there.
HELP WOULD BE HIGHLY APPREICIATED.
A massive thanks to the creators of this btw!
The text was updated successfully, but these errors were encountered: