[rules] Added AWS Config Compliance and Remediation Rules

[jack1902]

to: @ryandeivert
cc: @airbnb/streamalert-maintainers
related to:
resolves:

Background

Added Rules to trigger alerts on AWS Config NON_COMPLIANT and when Config Remediation takes place

Changes

• Added rule to Alert on AWS Config NON_COMPLIANT
• Added rule to Alert on AWS Config Remediation (this is extremely useful to notify people they got auto-remediated so they don't go crazy when things just suddenly change on them)

Testing

• Added the .json file to run ./manage test rules Rules engine passes :)
• Ran ./tests/scripts/pylint.sh Fixed errors
• Ran ./tests/scripts/unit_tests.sh

[coveralls]

Coverage remained the same at 95.427% when pulling e3cfa59 on jack1902:rules/aws_config into fcdf0a8 on airbnb:release-3-1-0.

[jack1902]

Alternatively, this could be placed under rules/community/config/ with names like compliance.py and remediation.py this then makes one rule per file under the service within AWS. This would make it easier to break down test files to trigger ONE rule instead of multiple since the test files currently map to the rules folder.

This is a wider structure question which i'm happy to put into a seperate issue as i see rules/community/cloudtrail potentially ballooning into a lot of files making it difficult to track specific things down