AWS Config Reviews and Ratings

Use Cases and Deployment Scope

Having migrated to the AWS cloud over the last year and a half, we started with AWS from the beginning. It is great to check if your implemented resources align with what you want and/or AWS best practices and to keep a history of all the configuration changes. Both are very helpful for any compliance question you might encounter.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.