The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
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.
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.
