AWS Config Reviews

18 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Do you work for this company? Manage this listing

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-3 of 3)

Companies can't remove reviews or game the system. Here's why.
Anonymous | TrustRadius Reviewer
March 27, 2019

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

Score 7 out of 10
Vetted Review
Verified User
Review Source
We use AWS config to set a ground rule of our AWS configuration and resources. Since we are using AWS S3 for a lot of our critical resources, AWS config makes it easy for us to evaluate the configuration of those resources as well as tracking the configuration history to see whenever any configuration changes cause an issue to our service.
  • Track many AWS server configuration
  • Faster and easier audit process of your AWS services configuration
  • Keeping history of changes means its easy to spot any issues that occur whenever any changes happened
  • The interface is not really user friendly and the configuration option is not easy to use either
  • Only available for resources within AWS
  • Some service can be quite costly, we need to prioritise which service that we would apply AWS config to and leave the less important service without AWS config monitoring
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.
Read this authenticated review
Anonymous | TrustRadius Reviewer
January 09, 2019

AWS Config for all governance and audit needs

Score 8 out of 10
Vetted Review
Verified User
Review Source
AWS Config is used to assess, audit, and evaluate the configuration of your AWS resources. It is implemented in many applications that use AWS to deploy. It helps in assessment, operational auditing and general governance of AWS resources.
  • 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.
  • Dashboarding and graphs should be better and more configurable.
  • Some time the Config Rules are difficult to understand and configure. They could be made easy or have GUI to configure them. I know it is difficult to build but that would be a good win.
If you have multiple resources in your AWS environment then AWS Config can provide you with audit, governance, and comparison of any changes to your resource configuration over time. You can create alerts to be notified via AWS SNS if any configuration changes, which is very useful for development teams. Governance in an organization, like “Who made the change?”, “From what IP address?” is a very useful audit and operational governance tool.
Read this authenticated review
Anonymous | TrustRadius Reviewer
February 07, 2019

AWS Config - ideal for AWS workloads

Score 7 out of 10
Vetted Review
Verified User
Review Source
AWS Config allows us to monitor our configuration of AWS resources, whether that be configuration history so we can view any changes which might have caused an issue; or if we want to be able to replicate workloads in a previous configuration.

This also allows us to save all our configurations within an S3 bucket.

We get alerts on some workloads via SNS when applicable.
  • We are able to use AWS config to track changes within our environments.
  • We use AWS Config across multiple accounts (environment segregation) whilst maintaining a central (fully backed up because stores in S3 managed repository.
  • 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).
Ideal for compliance monitoring - so providing easy visibility on what volumes aren't encrypted, S3 buckets requests only come from HTTPS sites, RDS is encrypted at rest by default.

There are lots of useful scenarios whereby we use this. Other examples [of how] we use AWS Config include Redshift cluster configuration check, cloud trial is enabled.
Read this authenticated review

About AWS Config

AWS Config is a service that enables users to assess, audit, and evaluate the configurations of AWS resources. Config continuously monitors and records AWS resource configurations and allows users to automate the evaluation of recorded configurations against desired configurations. With Config, users can review changes in configurations and relationships between AWS resources, dive into detailed resource configuration histories, and determine overall compliance against the configurations specified in internal guidelines. This enables users to simplify compliance auditing, security analysis, change management, and operational troubleshooting.

AWS Config Features

Has featureConfiguration history of AWS resources
Has featureConfiguration history of software
Has featureResource relationships tracking
Has featureConfigurable and customizable rules
Has featureAutomatic remediation with Config rules
Has featureConformance packs
Has featureMulti-account, multi-region data aggregation
Has featureCustom configuration
Has featureConfiguration snapshots
Has featureCloud governance dashboard
Has featurePartner solutions

AWS Config Integrations

Jira Service Desk, AWS CloudTrail, AWS Systems Manager, Amazon EC2 Dedicated Hosts, Amazon Machine Image (AMI) IDs, Elastic Load Balancing (ELB), Application Load Balancers, AWS Organizations

AWS Config Competitors

ServiceNow Now Platform, CloudBees Core, Optimizely, SaltStack, Azure Automation & Control, ServiceNow IT Service Management, Red Hat Ansible Automation Platform, Puppet Enterprise (formerly Puppet Data Center Automation)

AWS Config Pricing

  • Does not have featureFree Trial Available?No
  • Does not have featureFree or Freemium Version Available?No
  • Has featurePremium Consulting/Integration Services Available?Yes
  • Entry-level set up fee?No

With AWS Config, you are charged based on the number of configuration items recorded, the number of active AWS Config rule evaluations and the number of conformance pack evaluations in your account. A configuration item is a record of the configuration state of a resource in your AWS account. An AWS Config rule evaluation is a compliance state evaluation of a resource by an AWS Config rule in your AWS account, and a conformance pack evaluation is the evaluation of a resource by an AWS Config rule within the conformance pack.

AWS Config Support Options

 Free VersionPaid Version
Email
Forum/Community
FAQ/Knowledgebase
Social Media
Video Tutorials / Webinar
Phone

AWS Config Technical Details

Deployment Types:On-premise
Operating Systems: Windows, Linux, Mac
Mobile Application:No
Supported Countries:Americas, Europe, Middle East, Africa, Asia Pacific