AWS Config vs. ServiceNow IT Service Management

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.

Incentivized

I think [ServiceNow IT Service Management is] best suited for very straight-forward customer support type ticketing. If the problem can't be solved by the customer support team, then the ticket likely is a larger issue (ie: a bug) and then likely a Jira ticket would need to be created for more robust documentation.

Incentivized

• It can help you define rules for provisioning and configuring of your AWS. We use it for this purpose.
• It maintains configuration history. So you can use the AWS Management Console, API, or CLI to obtain details of past configurations
• It gives you a configuration snapshot of all of your AWS resources and you can store it in AWS S3.
• You can integrate it with AWS CloudTrail to correlate configuration changes to particular events in your account.

Incentivized

• When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
• I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
• Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
• To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.

Incentivized

• Vendor lock-in, no easy migration path for example if you want to move some workloads to Azure, you'd not be able to lift and shift.
• Only at an AWS resource perspective - cannot do desired state configuration at an OS level (which makes sense but be good if you could even as a separate feature within AWS Config).

Incentivized

• ServiceNow knowledgebase is limited for self-learning on how to use their features.
• ServiceNow sometimes has a very linear approach to some workflows or assignments where there could only be one child/parent relationship.
• The ServiceNow features for Project Management serves its function is rather cumbersome. The dependencies aspect or predecessors or successors options are rather limited. It is more focused on hours planned vs hours worked then dependencies.
• ServiceNow customer support is hit or miss. They could serve to have more self-help step by step articles.
• ServiceNow needs to have a better export or import features for their Project Management module.

Incentivized

To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.

The Geneva version has improved overall usability a lot, but would still be overwhelming for new users. Much like SAP or other large-scale applications- it can be very daunting when you get the first glance of all the modules, but you'll get the hang of it after some training and strong discipline.

Incentivized

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

The performance has never been an issue for us, the dashboard gives us real-time monitoring and the alert sends us the notification within less than a minute of it happening, this applies to all of the monitored resources on AWS. However we can't (or probably haven't figured out how to) integrate with any other third party services, so we can't really evaluate how it integrates with other services

Incentivized

For a massive system, page loads are reasonably quick, including searches.

Incentivized

I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.

Incentivized

To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.

ServiceNow implements its solutions for customers using the Start Now Implementation Methodology. The StartNow (STrategicAlignment and drive Rapid Transformation) Implementation Methodology include five deployment stages Plan, Discover, Prepare, Deploy, and Operate. Follow these steps for smooth implementation.

Incentivized

Despite the comparison it is not really apples to apples, the main purpose of the service is quite similar which is to monitor your application or services. In terms of AWS services, AWS Config provides more options to monitor and log your service on the infrastructure level which is very useful on that level and overall will give you more information about what is currently happening. Meanwhile PaperTrail is more suited to monitor and log your service and could only give you information on the application level.

Incentivized

This software was used previously. the software was not easy to configure like servicenow and the visual dashboards and the ui experience was less appealing compared to ServiceNow. ServiceNow offers a lot pf features which can be used across the industry. Gives better integration options compared to Remedy. CMDB and Service Watch are great tools offered by ServiceNow which is lacking on Remedy

ServiceNow works as an enterprise solution.

Incentivized

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

Incentivized

• We don't currently have a CMDB, so we are leveraging ServiceNow to build one using their ITSM and ITOM tools. This is a huge gap for us as a company and it will be a big win once this is in place.
• The core help desk functions are comparable to most other tools on the market, but SN does a great job of integrating that data with other modules like Problem, Change and Event Management to provide a truly integrated solution.
• The tool is expensive, so you will need to try to do as much as you can with the platform. We currently use other systems for HAM and SAM but will be including these in our ServiceNow instance in the future to help maximize our ROI.

Incentivized