Using CloudCheckr to check AWS account for best practices

CloudCheckr’s best practice checks take a detailed look at your AWS deployment to ensure your infrastructure is configured properly, and highlights areas that may be cause for concern.  These checks will focus on four key areas:

Security – CloudCheckr will look and see if you are setting proper permissions, if ACLs are configured correctly, if proper password policies are in place, if instances or AMIs are open to the public, and several other items.

Availability – CloudCheckr will look at your deployment to not only verify that everything is up and running, but also ensure that your architecture is properly configured to respond when things do go awry.

Cost – CloudCheckr will look for items that have been deployed but aren’t being used, or are not being used properly, and highlight those for you.  These can be anything from unused Elastic Load Balancers, Elastic IPs, Reserved instances, to huge S3 objects what can increase your costs.

Usage – CloudCheckr will review your architecture to see whether you are taking advantage of features which are highly recommended, but are often not consistently or properly deployed., and whether they are being used in the most advantageous way.

You will find two Best Practices Reports within CloudCheckr:

Best Practices Report – shows  the details about any issues found, as well as descriptive text explaining what was checked and why it is important.

Each Best Practices check is sorted by category (Security, Cost, Availability, and Usage) as well as importance (High, Medium, Low, and Informational).  The results of your Best Practices checks can by sorted by any of these categories using the tabs and dropdowns at top of the report.

Leave a Reply