AWS Config vs. OpsCompass

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

Our AWS Cloud was a perfect fit for OpsCompass. We needed a better method for understanding the size/extent of our Cloud--rather than the manual approach we'd been using. It's saved us a lot of time, and allowed us to delay adding additional heads for at least six to nine months. It also gives us a better/faster grasp of potential security issues - we see them right away, and we can assess each issue far faster than ever before. When we expand to Azure, Ops Compass will be able to do the same thing for us. (We have no plans to expand into Google Cloud Platform, but Ops Compass works well in all 3 clouds, apparently.)

• 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

• Quick inventory of all my cloud resources
• Detects changes to my cloud resources--including the source of the changes (user or system)
• Cost impacts of changes to my cloud infrastructure

• 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

• I would like to see more integrations to help surface alerts. Slack would be great, as an example.
• An imbedded tour or onboarding would help our new users, but overall, the product is pretty easy to figure out

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 like that OpsCompass is native, multi-cloud, and gives us a consistent method and approach to managing our security across multiple environments. It was more attractively priced and had easier, simpler deployment. It took us about 30 minutes to get it connected to both of our clouds and get a quick view of all of our infrastructure.

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

Incentivized

• Our team was able to do roughly 30% more with the product. The automation helps us spot issues without a lot of manual work
• We identified changes that would have had a massive cost impact--spinning up or forgetting about infrastructure we didn't need.
• OpsCompass prevents configuration drift and maintains a healthy state across multi-clouds.