AWS Config vs. ServiceNow IT Operations Management

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.

Incentivized

We have taken advantage of the single platform for different IT disciplines over the past few years and now we are doing more and more with the integrations. Our teams are looking at the same information which stops the blame game a lot. Their newest AIOps has been a very nice surprise as we've tried another tool for about 2 years and it required us to hire outside consultants to try and build what we needed. So far, ServiceNow found a lot of things we didn't know to look for. It's not perfect in fixing everything, but really has provided a lot of visibility and troubleshooting.

• 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

Incentivized

• The centralized dashboard allows us to keep track of production incidents as they come in, and allow us to view and sort them based on severity, making sure it's tracked
• The read/edit access and role granting process is straightforward, meaning that only the right people can change /update the statuses of incidents without unintended consequences
• With AI driven classification, it's easy to track outage impacts

Incentivized

• It's only AWS, no third party.
• Not the most intuitive interface, but with a little getting used to it is OK.

Incentivized

• Scan network is limited to their discovery tool, which is costly
• Integration to jamf and ubunto tools
• Agents TCO
• integration to password management tools which are critical for successful scans

Incentivized

Would rate lower for other workloads but for AWS workloads its simple to set up, cost effective and customisable. Primary use case is compliance from a governance perspective.

Incentivized

I do not know or have used any other product in AWS cloud space that matches what AWS Config provides. We have some custom built monitoring and governance, however that is there because AWS Config does not provide it currently.

Incentivized

BMC was our legacy system before deploying ServiceNow. It's time had passed for us as it couldn't really keep up with our move to cloud and the number of services we were using. The cost kept getting higher, especially with all of the customization we had to do. Over the years, just got unwieldy. We still use Splunk for raw data and log analysis, but we upgraded to ServiceNow event management and the Loom system log analytics. We had Loom before ServiceNow bought them, but it's nice it's all on one platform for us. Splunk at times had so much info, we didn't know where to start, but ServiceNow gives us a great starting point.

• Enforcing audit requirements
• Easy to set up alerting when there are rule breaches
• Auto remediation reduces the manual policing of such breaches

Incentivized

• With the regular use of ServiceNow IT Operations Management platform, our incident resolution time has gone down by over 90% over the past year
• Our access and role granting process has been streamlined leading to increased developer hours by around ~90 PM
• With the enablement of AIOps driven impact prediction, we expect an improvement of user communication time by over 90%

Incentivized