Description of issue:

This doc: https://github.com/Netflix/security_monkey/blob/develop/docs/update.md
states the required libraries/modules needed in order to pull data from GCP, however after installing the latest version I was unable to receive any data from GCP, while monitoring the workers I noticed some errors (which were marked as INFO for some reason) , these errors stated the lack

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
When draining nodes on a production cluster, it might be safer to use a health check between node/nodegroup draining loops - to ensure that until now things

Metadata:

• Operating System: Debian 8.10
• Installation method: install.sh script
• AWS CLI Version: not sure any more, less than 1.15.2

I was not able to login over SSH with existing IAM user account. Troubleshooting revealed

aws iam list-ssh-public-keys --user-name "$UnsaveUserName" --query "SSHPublicKeys[?Status == 'Active'].[SSHPublicKeyId]" --output text

in ```authorized_k

Hey @PiercingDan! Thanks for writing up this guide and featuring Flintrock in it prominently. I have a couple of suggestions that may help simplify the guide.

1. From Using your own AMI:

   Note that it is important that since flintrock is designed to install and configure S

Graylog 3.0.1

I'm in the scenario described here

If you don’t have a working DHCP server for your virtual machine, you will get the error message:

“Your appliance came up without a configured IP address. Graylog is probably not running correctly!”
In this case, you have to login and edit /etc/

Do you already have an issue opened with F5 support?

Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open an case with F5 if this is a critical issue.

Description

Describe the problem you're havin

Expected behavior

All user-settable, spel-specific variables should be documented in the project-documentation. Further, some variable-names might want modification to better-reflect their applicability (e.g., only spel-wide var-names get the spel_ token; AWS- or Azure-specific var-names get aws_ or azure_ name-tokens, respectively; etc.).

Actual behavior

Not all user-sett