[wish] Support for non-AWS deployment about security_monkey HOT 2 CLOSED

Security Monkey should be deployable to any machine that has the required dependencies installed.

For development you can even run it on your local machine. The biggest problem with deploying on a non-aws machine is figuring out how to get AWS credentials to the machine which will be running Security Monkey.

You could potentially deploy the credentials via chef, puppet or some other configuration management system. If you wanted you could even manually deploy the credentials by placing them in the ~/.aws/credentials file.

The file you mentioned common/sts_connect.py is how Security Monkey gets credentials (tokens) to other AWS accounts. It assumes that Security Monkey has already started with some AWS credentials (obtained via one of the methods mentioned above).

Security Monkey needs to have the AWS roles defined in the documentation so that it can make the correct calls to AWS, but how you get credentials onto the box it is running is totally up to you.

from security_monkey.

Thanks for the quick answer.
My fault, I was missing the fact that boto is by default pulling credential from config files. Being aware of that, I was in fact able to deploy it locally following you suggestions.
Closing because NOTABUG.

from security_monkey.