AWS Config is the only one you need for your AWS infrastructure monitoring

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

For the first time user, the whole configuration options can be really confusing. The explanation and user experiences is not very straightforward and user friendly to use. You need to know at least basic knowledge of how the majority of AWS cloud system works on top of the AWS services that you actually use. The amount of configuration option could be overwhelming when you set it up the first time.

It's really good if your infrastructure services is all in AWS, that means everything could be audited and monitored using AWS config. You also can create alarms to notify you or your team about any changes on your AWS resources which is very useful to prevent abuse if you have a fairly large team. It's also very useful whenever some third party wants to audit your AWS resources, if you have a fairly comprehensive AWS config configured, the auditing process will be easy since they only need to look at your AWS config setup.