AWS Config Reviews

I use AWS Config primarily for configuring virtual machines and managing the IAM part of our infrastructure. I configure virtual machines as a specific example of how I use AWS Config in my day-to-day work. I am also involved in configuring backups and configuring access for different users while using AWS Config in my organization.

AWS Config has positively impacted my organization, and this is very useful for us since we use the entire cloud platform and our infrastructure is now at the cloud level. We no longer use physical servers, which gives us an advantage and a reduction in costs.

I have noticed the cost reduction since we stopped using other servers that we had with another provider and migrated to the cloud. This gives us a great opportunity to have backups, and in any situation or event, we can recover the information more quickly and more effectively.

I consider carrying out all the configuration to be the best feature that AWS Config offers. The advantages include the manuals, though there are some things that are very detailed, which is a lot of information.

I find the documentation for the configuration part especially useful, as it really supports us in bringing up our instances, generating automatic backups, and allowing us to grant certain information or a certain level of access to certain users.

AWS Config could be improved if they could generate some training as support because it is a gigantic platform with many solutions and a lot of information, which would help us significantly.

I have been working in my current field for two years.

I consider AWS Config to be a stable platform. AWS Config is stable because we have not had any problems at all.

I think the scalability of AWS Config is good, as with just a few clicks we can bring up other instances or carry out different configurations for each of the ones we currently have.

My experience with AWS Config's customer support has been good. We have not had any problems and have not requested support much, as we rely more on the manuals.

Before using AWS Config, I used physical servers with another provider, and I decided to change for obvious reasons. There was a problem with the provider, and we were left for around a week without our services. I feel safer with AWS now.

I have seen a clear return on investment since using AWS Config. In terms of time, we no longer have to make so many requests to another provider because we had our system on other servers with another provider. This reduced the time significantly, and now I carry out the queries myself or implement any configuration we need directly.

My experience has been satisfactory with pricing, implementation costs, and licenses. The level of investment we are currently making for our backups is really worth it to have everything secure and able to recover all the information in any case of catastrophe. The cost reduction was also quite viable since we only have five instances, and sometimes we have two test instances we can shut down, which no longer generates consumption or costs when turned off. This is very beneficial.

We considered Google Cloud before choosing AWS Config; however, we did not opt for it.

My advice to others considering using AWS Config is that they really evaluate it and consider making the investment to have a solution in the cloud. I give this review a rating of 9 out of 10.

I use the solution in my company to check the vulnerabilities for all the resources, including tools like S3, EC2 Instances, and to help us with the IP addresses of those attempting to hack into our environment. The tool is useful for checking resources and for vulnerability scanning.

With AWS Config, it is easy to find out which IPs belong to the list of suspicious IP addresses. The tool also helps our company check which resources are affected by threats or attacks in our environment.

I have been using AWS Config for a year. I am a customer of AWS Config.

I have not faced any stability issues with the product. My company usually configures everything before sending the product to our customers, who have some support teams to monitor the configuration part that we manage. If there are issues in the product that our company's customers can't troubleshoot, they return to us and seek help with the troubleshooting part.

I had no reason to contact the solution's technical support.

AWS Config's dashboard improved our company's security as it helps with the vulnerability scanning of resources.

AWS Config integrates with the existing security infrastructure of our company, and it is an easy process that is not at all complicated.

AWS Config is a security product. The tool protects its users' resources and data from unauthorized access, security breaches, and threats. The product helps with data encryption. You can have your data on AWS KMS, which helps with data encryption. For areas like SSL/TLS encryption, the tool offers data protection between AWS services and endpoints.

As I need to learn the components of the product, I rate the overall tool a seven out of ten.

We use AWS solutions to host our applications, such as ClearPass and Mac applications, JEMOS, and Microsoft domain controllers. We also host DHCP on AWS.

Installing the instances and performing upgrades is smooth and clean.

The reboot process for AWS instances could be improved. Microsoft Azure does not have this problem, so AWS could consider making their instances more robust. You would not need to reboot your instances frequently to replace the hardware and stuff. They can look for a better approach or mechanism to improve in the future.

The concern is that you need to plan for the outage when you reboot an instance. You need to have a maintenance window where you can properly reboot the instance without affecting your application. When Amazon announces that you need to reboot an instance and are not ready, this becomes a problem.

I have been using AWS Config for three years. We are using the latest version of the solution.

AWS Config’s stability is subjective. Sometimes, it is difficult to tell whether the platform or the hosted application causes a problem. It is very difficult to say the cause of the problem. In some cases, we need to dig deep to find the root cause of the problem. AWS is a stable platform for hosting applications.

The solution is scalable for hosting or user assessing the application hosted and upgrade. It can support up to 40,000 users.

AWS Config has the best support. It is very easy to get support because you can send a request, and they will usually get back to you within 10 minutes. You can also talk to them via chat or schedule a phone call.

The initial setup of AWS Config is easy, but it is strange to familiarize for the first time. It is not tough to follow once you familiarize yourself with the steps and approach.

In terms of the regular setup, it is very fast. Whenever you need a new instance in a particular region, it can be finished within 5 to 10 minutes.

First of all, we need to check whether it is available or not. We can reserve it and schedule when to deploy the instance if it's available. The instance can then be deployed immediately in the specified VPC with the IP addresses, EBS size, memory size, and instance type to check whether you need more CPU. For example, we must ensure the ClearPass image is available in the desired region and version. Overall, the deployment process is straightforward and not very difficult.

The solution charges us per hour. There's no license.

Since I have a networking background, I deployed AWS Config with my teammate. We usually need two people for maintenance because sometimes we need to process.

It depends on the type of application you want to host. For example, Azure might be a better choice Azure might be a better choice if you want to host a Microsoft application because it offers more automation and integration with Microsoft services. AWS is a more open platform for developers who need more flexibility and control. AWS is also a good choice for hosting open-source OS like RedHat. It is also cheaper in terms of cost.

Overall, I rate the solution a nine out of ten.

It tracks configuration changes across all your AWS resources. Imagine it as a log of every tweak and setting alteration. This lets you build compliant policies based on desired configurations. 

For example, if a server gets exposed publicly, Config flags it as a deviation from your baseline, monitors it, and can even automatically fix it (auto-remediate) for you. That's the main use case, making sure our AWS setup adheres to our security and compliance standards.

The historical analysis is amazing. If a malicious actor changes something in your account, you can go back in time through Config's history, see exactly what was modified, and revert it to a safe point.

There is room for improvement in built-in tools, they are not up to the mark. Some of the built-in inbound rules feel outdated and could be refreshed with stronger, more relevant options.

I have been using it for two years. It's a native tool from AWS.

It is a stable product. 

It's hard to quantify individuals using Config directly. It manages your entire AWS account, so it's more of a platform-level tool.

There are dedicated admins responsible for overseeing Config. At least five or six AWS admins familiar with Config are there.

The customer service and support are quite helpful.  

The initial setup is super easy, it takes like two minutes. Literally a one-click deployment.

It is a very expensive tool. AWS pricing for Config is not fixed and depends on your organization's size and complexity. The more resources you have and the more frequent configuration changes occur, the higher the cost.

If you need auto-remediation for compliance purposes, then I would recommend using this solution. But if you already have another Cloud Security Posture Management (CSPM) tool, Config might be redundant. For purely AWS environments, though, it's a great choice.

Overall, I would rate the solution an eight out of ten. It's useful for compliance and security, but we have to balance the cost and other things.

Improvements are needed as per customer requirements. 

I have been using AWS Config for the past two years. 

It is a highly stable solution. I rate the stability an eight out of ten. 

The scalability is a ten out of ten. 

The initial setup is straightforward. 

Overall, I rate the solution a nine out of ten. 

Our primary use case for this solution is identifying data through the resources feature. This solution allows us to track changes on the platform and create a history of changes. Additionally, we use the remediation feature to ensure the safety of our information and track security breaches or exposures.

The tracking, history logs, and security alert features are valuable because they are critical features that assist us.

The solution is missing a configuration that can assist us when writing our programming languages.

We have used this solution for a year and a half, and we deploy it on the public cloud.

The solution is stable.

The solution is scalable and provides over 100 rules with the ability to rate them. We have between 50 to 75 people using it in our organization.

Our experience with customer service and support has been good.

The initial setup was straightforward for the first three features. However, it was a bit complex for the fourth feature, which involves writing your programming language. Also, deployment takes a few minutes.

I rate this solution a ten out of ten. However, it can be improved by including configurations that assist us when writing our programming languages.