AWS Config - Enforce, Evaluate, Remediate
April 29, 2021

AWS Config - Enforce, Evaluate, Remediate

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with AWS Config

We use AWS Config to ensure our resources on AWS adhere to AWS best practices. It is used to assess and evaluate your AWS services and their configuration. There is also the option for automatic remediation when a service is found to be breaching a rule. AWS Config is a great tool for [the] governance of your AWS accounts.
  • The ability to track changes in AWS is paramount, AWS config allows you to do this
  • Allows the auditing of an AWS account
  • Can view history of an account that has AWS config enabled
  • Vendor [lock-in] as this is only available on AWS
  • [The] interface is dated and is [in] need of updating by AWS
  • Graphing is [...] not the easiest to configure
  • Rule enforcement
  • Auto remediation
  • Reporting
  • Enforcing audit requirements
  • Easy to set up alerting when there are rule breaches
  • Auto remediation reduces the manual policing of such breaches
I have not assessed any other tools that do a similar function to AWS Config.

Do you think AWS Config delivers good value for the price?


Are you happy with AWS Config's feature set?


Did AWS Config live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of AWS Config go as expected?


Would you buy AWS Config again?


The specific situation we find it useful to use AWS Config is to apply config rules to enforce certain audit requirements, from ISO 9001/27001 for example. This means we know that no resources can be created that will breach these audit requirements. However, as the [number] of rules start to grow it can become cumbersome to manage.