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 13: Line 13:


* Evident.io ( bought by Palo Alto Networks https://www.paloaltonetworks.com/products/secure-the-cloud/evident )
* Evident.io ( bought by Palo Alto Networks https://www.paloaltonetworks.com/products/secure-the-cloud/evident )
* Cloudcheckr ( https://cloudcheckr.com/ )
* Cloudcheckr ( https://cloudcheckr.com/ ) - I can recommend this. I've used this in anger. It is a great tool, lots more than just compliance ( cost control and reporting as well )


Or you can use some open source tools:
Or you can use some open source tools:

Revision as of 17:47, 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: