AWS Config vs CloudCheckr

• It can help you define rules for provisioning and configuring of your AWS. We use it for this purpose.
• It maintains configuration history. So you can use the AWS Management Console, API, or CLI to obtain details of past configurations
• It gives you a configuration snapshot of all of your AWS resources and you can store it in AWS S3.
• You can integrate it with AWS CloudTrail to correlate configuration changes to particular events in your account.

Read full review

• Detailed Best Practices. It's important to align your cloud to industry best practices for security and cost—it just performs better if it's used the way it's meant to be used. AWS is very flexible, and that's great when you have special requirements, but you've got to at least know when you're using something in a non-standard way so you can think through the implications.
• Cost Reduction. Some recommendations are almost impossible to make at least for our setup, but many, many others are easy. We only have to log into CloudCheckr every few months and make a few changes for it to more than pay for itself.
• Right-Sizing. This is related to the other points, but for some reason is separate from their cost module. The metrics it's able to pull only tell half the story, so it's good to verify it's sizing recommendations before making changes. But it does show you what instances to focus on first, and even if you choose a slightly different size to move it to, it does clearly indicate it's current size isn't appropriate. And this works both ways, if the size is too big, you can save some cash by making it smaller, but if it's too small, you want to be sure to scale up before you run into performance problems.

Read full review

• Vendor lock-in, no easy migration path for example if you want to move some workloads to Azure, you'd not be able to lift and shift.
• Only at an AWS resource perspective - cannot do desired state configuration at an OS level (which makes sense but be good if you could even as a separate feature within AWS Config).

Read full review

• CloudCheckr features have a tendency to break without warning. Functionality in place for months could suddenly stop working.
• CloudCheckr support often delays work on support tickets for fixing broken application functionality.
• The CloudCheckr platform and documentation website often crash or experience performance degradation.
• CloudCheckr cost reporting is often impacted by faulty code or broken report functionality. This can contribute to a low level of confidence in CloudCheckr's ability to deliver accurate cost reporting.

Read full review

• Security awareness. With multiple teams deploying provides easy visibility on any security risks. Security breaches would have a substantial impact on business so a vital investment with little costs.

Read full review

• CloudCheckr has allowed us to increase resell margins as an MSP.
• CloudCheckr has made us aware of cost savings opportunities that exceed the price of the platform itself.
• CloudCheckr has given us additional visibility that has allowed us to manage and understand cloud computing costs.

Read full review