AWS Config vs. CloudBolt

To keep track of changes and to answer many compliance issues this is a life-saver. AWS does a good job providing tools like this. Any AWS workload should be monitored with AWS Config. It even is great for troubleshooting and seeing who changed what at what time.

Incentivized

Creates dynamic groups and flexible Active Directory configurations. Improves our automation capabilities. Helps us to automate a part of our Active Directory administration process. Helps us to automate the process of registration and cleaning the computer accounts with Active Directory. Helps us to improve the reliability of registration to mitigate failures like retry logic and post validation checks.

Incentivized

• 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.

Incentivized

• Create configuration with Microsoft endpoints.
• Support complex globally distributed multi-domains.
• Create and remove dynamic OU.
• Allows for static text in combination with dynamic content.

Incentivized

• 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).

Incentivized

• Support could be improved on a >tier 1 level
• Logging could be more descriptive/specific
• Stability of the actual server

Incentivized

The performance has never been an issue for us, the dashboard gives us real-time monitoring and the alert sends us the notification within less than a minute of it happening, this applies to all of the monitored resources on AWS. However we can't (or probably haven't figured out how to) integrate with any other third party services, so we can't really evaluate how it integrates with other services

Incentivized

Despite the comparison it is not really apples to apples, the main purpose of the service is quite similar which is to monitor your application or services. In terms of AWS services, AWS Config provides more options to monitor and log your service on the infrastructure level which is very useful on that level and overall will give you more information about what is currently happening. Meanwhile PaperTrail is more suited to monitor and log your service and could only give you information on the application level.

Incentivized

We honestly haven't looked into much. We've been using CloudBolt [Software] for a long, long time. I think we briefly looked into Morpheus but figured it was too much effort to lift everything, communicate it, etc. We selected CloudBolt [Software] because, at the time (and still do), they served our very specific case. We also liked the ability to customize certain aspects of the deployments - that enabled our "power users" to really tweak things just right for their departmental tasks.

Incentivized

• Enforcing audit requirements
• Easy to set up alerting when there are rule breaches
• Auto remediation reduces the manual policing of such breaches

Incentivized

• We have invested countless man hours to troubleshooting and being support's QA.
• Most of our teams have saved an invaluable amount of time by being able to automate their deployments.
• After the initial time you spend [understanding] all the nuances, the configuring of groups, permissions, etc., does make administering it easier.

Incentivized