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

[...] is changing the way our internal support staff (not only in the IT field) work and enhancing the experience for employees seeking IT assistance through ServiceNow IT Operation Management. We have moved the usual and personalized IT tools and functions from [...] service-desk to ServiceNow IT Operations Management. These advancements have sparked innovation in various aspects of our IT support management, such as enhancing accessibility, managing incidents, optimizing IT workflows and procedures, enforcing service level agreements (SLAs), incorporating AI/ML technology, utilizing virtual agents, streamlining automation, and sharing knowledge throughout the support team via data visualization, monitoring, and reporting. In brief, our collaboration with ServiceNow IT Operations Management is enhancing the effectiveness of our internal system and benefiting our shared clients.

Incentivized

• 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

• In platform expertise and workflows, so we don't allows have to build everything from scratch.
• Tight integration within ServiceNow (especially ITSM) but also brings information and data in from other sources, so I don't feel we are stuck in a proprietary hole.
• Increased investment in AIOps and automation
• Relatively fast time to value with out-of-the-box capabilities and automation.

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

Incentivized

• With the introduction of AIOps, we hope triaging outage impact can become more proactive
• The UI could be greatly enhanced and simplified for daily operations
• ServiceNow API access licenses are usually very limited bottlenecking use cases to build dashboards out from it

Incentivized

We achieved in financial what we are aiming for, as our targets are fulfilled, we solved many issues using ServiceNow, Creation of knowledge article improved, Ticket system got customized, overall survey from the customer is 4 out of 5, customization is done without any hustle and integration was very easy.

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

We wanted it integrated with ITSM and ITBM. Prioir to that we used JIRA for agile development and SysAid for ticketing. So we started with converting SysAid. We went live with Vanilla ITSM. Then we could have a basis for ITOM. However, we needed to migrated from JIRA to ITSM. Only then we felt mature enough to examine ITOM, which required quite a lot of resources. You need networking, motoring, IT and Cyber security team members in your project!!

Incentivized

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

Incentivized

• Makes it MUCH easier to understand impact between application and server
• Makes it easier to understand impact from a change and what all it affects

Incentivized