Aws notes/Getting Serious About AWS Config Rules: Difference between revisions

From Federal Burro of Information
Jump to navigationJump to search
No edit summary
No edit summary
Line 19: Line 19:
* [https://github.com/awslabs/aws-config-rdk AWS Config Rules Development Kit]
* [https://github.com/awslabs/aws-config-rdk AWS Config Rules Development Kit]
* [https://github.com/awslabs/aws-config-rules AWS Rules]
* [https://github.com/awslabs/aws-config-rules AWS Rules]
== The OS way ==
For those of you who just want results. ( not for those of you who want to write your own rules ). THink of this as 80/20. For 20% work, you get 80% of the functionality and effect. If you have nthing, or little time, this is for you.
* You have the right amount of know-how.
* You want the right amount of automation.
* And open source is the right price.
1. install rdk ( rule development kit )
pip install rdk
2. clone the rules:
cd ~/work
git clone git@github.com:awslabs/aws-config-rules.git
cd aws-condif

Revision as of 18:00, 13 November 2018

Overview

There are a suite of service in AWS that can help you get yourself to an auditable position:

  • AWS config
  • AWS Cloudtrails

You can define rule about how your cloud account should be, and make an immutable record of how it is and changes over time with these two services.

There are published best practices , so you can go and roll your own setup.

You could pay someone else to do it:

Or you can use some open source tools:

The OS way

For those of you who just want results. ( not for those of you who want to write your own rules ). THink of this as 80/20. For 20% work, you get 80% of the functionality and effect. If you have nthing, or little time, this is for you.

  • You have the right amount of know-how.
  • You want the right amount of automation.
  • And open source is the right price.

1. install rdk ( rule development kit )

pip install rdk

2. clone the rules:

cd ~/work
git clone git@github.com:awslabs/aws-config-rules.git
cd aws-condif