The Now Platform® Washington DC release is live. Watch now!
on 06-15-2018 04:01 PM
CloudWatch provides a wealth of configurable monitoring features, and an easy way to send that information virtually anywhere by using AWS SNS (Simple Notification Service).
ServiceNow routes incidents to the right people in your organization who need to take action when something meaningful happens in your AWS environment.
This post demonstrates how to integrate AWS SNS topics to send messages to ServiceNow, open an incident when a CloudWatch alarm is triggered, and test your configuration with a sample CloudWatch alarm.
CloudWatch Alarms: https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/event-management/t...
CloudWatch metrics (included with Operational Intelligence):https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/event-management/t...
We will use a free ServiceNow developer instance to do our work. If you already have one, feel free to use your own.
Before AWS SNS is allowed to send messages to ServiceNow, you must confirm the subscription on ServiceNow. At this point, AWS has already sent a handshake request, and it’s awaiting confirmation inside your ServiceNow instance.
Now let’s do something meaningful whenever AWS SNS sends an alarm. In this case, we want open an incident when CloudWatch notifies you of a budget threshold being crossed. ServiceNow provides a script “Handler” that is invoked when SNS sends an alarm message. To configure a handler to create an incident, follow the instructions below:
var incident = new GlideRecord("incident");
incident.initialize();
incident.short_description = "SNS Alarm: "+message.AlarmName;
incident.description = "AWS Account ID: " + message.AWSAccountId + "\nRegion: " + message.Region + "\nDescription: " + message.NewStateReason;
incident.insert();
To test this integration, a CloudWatch alarm is going to be created and tripped to trigger an SNS message, which will create an incident in ServiceNow.
For example before trigger:
Alarms->Select Alarm->Modify
This blog demonstrated one way of integrating ServiceNow with CloudWatch, by creating an incident whenever AWS billing exceeds a threshold. The principle can be extended to any type of SNS topic which notifies ServiceNow whenever anything meaningful happens inside AWS cloud environment. Within ServiceNow’s SNS Handlers, you can create any type of ServiceNow record you like; it could kick off an automated workflow, or create Events/Alerts/Notifications, or even automatically orchestrate some kind of remediation.
Below diagram shows some of the automation you can perform using this integration pattern.
Grant Hulbert is a senior Technology Alliance Architect for Servicenow, and manages technology relationships with ServiceNow’s global strategic alliance partner engineers
Itai David Njanji is a certified Solutions Architect at AWS and leads the Operations Integrations practice on tooling strategy between AWS services and third party tools such as ServiceNow.
Special thanks to Ben Yukich, who wrote the ServiceNow source code for this integration
Learn more about the authors on Linkedin Itai David Njanji Grant Hulbert Ben Yukich
Thank you for the easy to follow article!
its not working for me,can you help me on this ?
It is not working.I created the SNS topic & subscription in AWS but I am not able to view any thing in SNS Subscription in Servicenow.
When I open the endpoint in browser I get error GET method not supported for API
I have created Create SNS Memory Utilization Alarm Incident and used the code
var incident = new GlideRecord("incident");
incident.initialize();
incident.short_description = "SNS Alarm: "+message.AlarmName;
incident.description = "AWS Account ID: " + message.AWSAccountId + "\nRegion: " + message.Region + "\nDescription: " + message.NewStateReason;
incident.insert();
In the incident in description it displays AWS account Id,Region and description of the reason but I need to get the Instance ID for which the alarm is created .What needs to be added to the above script.
Are you verifying the message signature at all? Had a quick look through the code and couldn't see any signing going on, but might be missing something. 🙂
In "Configure ServiceNow" step 4 when I try to install the application from https://github.com/byukich/x_snc_aws_sns
I have a failure with this message error "Repository authentication failed, check credentials. Make sure the user has both read and write access".
My ServiceNow version is Orlando (and it doesn't work even on an ootb developer instance). As asked I let the User name and Password fields empty.
Someone else have this trouble ?
How can I fix this trouble ?
Try to clone the repo into your own github. Then follow the steps of importing it into ServiceNow from your own github with your username/password also being entered
you have to create your own Github account and clone the Source from github.
now you have to use your own GutHub account credentials here to import all the updates.
This does not work for me, its asking for credentials
You cover a lot of things but it's not working for me, here are some steps you can follow.
1. Set up an Amazon CloudWatch Alarm to detect when certain conditions are met.
2. Configure the Amazon CloudWatch Alarm to send alerts to an Amazon SNS topic.
3. Set up an Amazon SNS subscription to send notifications to ServiceNow.
4. Create an event listener in ServiceNow to receive notifications from the Amazon SNS topic.
5. Create an Automated Action in ServiceNow based on the CloudWatch Alarm to automatically create a new incident when the alarm is triggered.
If you want to get more help or are stuck anywhere and you have no option you must contact our affiliation Urtasker https://www.urtasker.com/amazon-account-management/ , we gave professional services for sellers.