AWS Config vs. HPE Morpheus

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

We use Morpheus and graphene to monitor our on-premise servers. A consistent tool for using across servers/VMs, databases and networking equipment would provide a wholistic monitoring experience

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

• Copious native 3rd party integrations.
• Ties into multiple public and private clouds for single management plane.
• True multi-tenancy.

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

• More dashboard/visualization capabilities

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

We have always been able to reach the support organization at Morpheus on the rare event we needed them. They have been nothing but helpful.

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 previously were using VRA. VRA, while some of the new versions look interesting is hard for both administration as well as end user consumption.

Incentivized

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

Incentivized

• It has allowed us to shorten operational time that it took to provide resources to teams.
• There is better cost visibility in the different cloud solutions.

Incentivized