Hundreds of best practice checks covering security, availability, cost, and usage

AWS is a large, robust offering with a seemingly infinite number of configuration options to tailor your deployment perfectly around your needs.  However, the flexibility and sheer number of choices that Amazon provides when setting up your services are both a blessing and a curse.  It can be easy to overlook security loopholes, deploy options that aren’t the most cost-effective, and miss beneficial features which are hidden within the AWS API.


That’s where CloudCheckr’s best practice checks come in.  We will take a detailed look at your deployment to ensure your infrastructure is configured properly, and highlight areas that may be cause for concern.  These checks will focus on four key areas:  security, availability, cost and usage.


While Amazon handles security of their datacenter, AWS users are responsible for network, host, and application-level security.  CloudCheckr will look and see if you are setting proper permissions, if security groups are being utilized properly, 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.


When items are launched in AWS, it’s important that they are accessible.  However, sometimes things can go wrong such instances becoming unhealthy, or availability zones becoming unreachable.  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.


When launching and maintaining an infrastructure within AWS it’s easy to lose track of what’s out there, and what’s no longer needed.  CloudCheckr can help with this.  We will look for items that exists, but aren’t being used, and highlight those for you.  These can be anything from unused Elastic Load Balancers, Elastic IPs, or Reserved Instances, to huge S3 objects that can raise your invoice.


There are many options in AWS which are highly recommended, but that we have found are not consistently or properly deployed.  CloudCheckr will review your architecture to see whether you are taking advantage of these features, and whether they are being used in the most advantageous way.  We will ensure that Auto Scaling is configured, and configured properly, within EC2.  We’ll ensure that the users in IAM are created according to best practices.  That backups are taken automatically and retained for an appropriate amount of time.

For more information on CloudCheckr’s Best Practice report, please go here:

Leave a Reply