AWS cloudwatch event integration with ServiceNow

Roopam1
Tera Contributor

There's a requirement to integrate AWS events with ServiceNow for event management. I have used below link to configure the topic in AWS. 

 

link: https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/event-manageme...

 

Also all required roles and user is created in ServiceNow as mentioned in the link. Password does not contain any special character. After creating topic in AWS console it says as pending confirmation. But ServiceNow has not receive any confirmation mail hence unable to receive any alarms from AWS.

 

Appreciate help on this if anyone has successfully achieved the requirement

 

7 REPLIES 7

RemcoLengers
ServiceNow Employee
ServiceNow Employee

I ran into this too @Roopam1  and may have something to get you moving. While I have not fully gotten to the bottom of the desired behaviour I noticed that if I disable the API Access policy you are able to "Confirm" the AWS SNS Subscription.

RemcoLengers_0-1734598373251.png

 

@Roopam1 Some more information surfaced. This is quirk of how AWS SNS sends out these request and how the Servicenow platform responds to this. A change request is filed to come up with a long term solution but for now the workaround it to make sure the "Event Connector Basic Authentication" Is the one with the latest Updated time stamp. So you may need to remove and add it for it to be the latest one added. This was you can leave the API Access policy enabled and have this integration work. (You need the cog wheel to add "Updated" column to the view).

 

RemcoLengers_0-1736184049592.png

 

@RemcoLengerscan you please share steps to achieve this, i am struggling.

RemcoLengers
ServiceNow Employee
ServiceNow Employee

Hi @hanwar2 ,

 

1. Delete the "Event Connector Basic Authentication" with the red x, save the record/update

2. Insert new row and add the "Event Connector Basic Authentication" back. It will have the newest Updated time

 

BTW A resolution is being worked on to fix this issue, it is considered a defect.

 

done!