AWS Event Driven Discovery

[Raj Abhishek]

Hi,

I have a requirement form customer where we have to discover the resources form AWS cloud. As customer feedback I got 2 question

1)if we can use the Event driven discovery to update the CMDB with the resources and its VM details. 

I have a doubt that how this discovery will discover the existing resources as Event driven discovery uses Event from AWS config services to send SNS notification to snow cloud REST API in order to update the CMDB. So as unless there is a change made in any of the resources it won't get discovered right?

2) Is there any Alternate method to get the OS details apart from horizontal discovery?

Your Help is very much appreciated.

Thankyou.

[Ratnakar7]

Hi @Raj Abhishek ,

1. Your understanding of event-driven discovery is correct. The discovery process is triggered by events that are generated by AWS Config and sent to an SNS topic. The Snow Cloud REST API is then notified of the event and updates the CMDB accordingly. This means that the discovery process is event-driven and not continuous. It relies on changes made to resources within AWS to trigger the discovery process. However, you can configure the discovery schedule to run at regular intervals in order to pick up any changes that have been made since the last discovery.

2. There are several ways to get OS details apart from horizontal discovery. One option is to use the AWS Systems Manager to collect inventory data from instances. This can provide detailed information about the OS, installed applications, patches, and other configuration details. Another option is to use AWS Inspector to gather information about the security and compliance of your instances. Additionally, you can use the AWS CLI or SDK to query the metadata service on an instance to retrieve information about the instance's operating system and network configuration.

If my response was helpful in resolving the issue, please consider accepting it as a solution by clicking on the ✅Accept solution button and giving it a thumbs up 👍. This will benefit others who may have a similar question in the future.

Thank you!

Ratnakar

[Raj Abhishek]

Hi @Ratnakar7 
Thankyou for your response. I am trying to implement the event driven discovery. We setup the SNS topic over AWS. But, while creating the subscription for instance, the endpoint i provided is throwing error(refer to below SS).

I followed this document:  Configure the AWS Config service to send event notifications to the ServiceNow instance

I created a user and provided the below mentioned roles: rest_service, snsc_internal, sn_cmp.cloud_event_integration
I used below two endpoint URLs :
1. [https://newly_created_user:user_password@instancename.service-now.com/api/now/cloud_event] This endpoint is throwing the error shown in above SS.

2. [https://newly_created_user:user_password@instancename.service-now.com/api/now/table/sn_cmp_cloud_event] This endpoint is also throwing the same error as above.

I researched little bit bit and found out that Amazon SNS doesn't support private HTTPS(s) endpoint.(refer to below SS)

Could you please help me to find the fix for the error knowing what am I missing here and how can I generate publicly available URL. Also, if there is any other way to do the Event based discovery, pls share that too.
Your help would be very much appreciated.
Thankyou

[Raj Abhishek]

Hi,

I got the solution for the above mentioned issue. 
This issue is due to the usage of special characters like square brackets [ ] or flower brackets { } in the password. so, I created user's password with no special characters which resolved the issue and i was able to get the AWS event. The first event which I received is 'subscription confirmation' event. 
Now at this point, I am not sure whether I have to accept the subscription confirmation event in order to receive the other AWS cloud events  or not because currently I haven't received any other event apart from Subscription confirmation event.

Can you please tell what could be the possible issue here?

Thankyou.

[Ratnakar7]

Hi @Raj Abhishek ,

When you're setting up event notifications in AWS, don't be surprised to receive a subscription confirmation event. This is just a way for AWS to make sure you're subscribed to the SNS topic. However, to receive other cloud events from AWS, you'll need to follow the instructions in the subscription confirmation message and confirm your subscription. Once that's done, you'll start getting the cloud events you want at your endpoint, like the Snow Cloud REST API. But what if you don't receive any other events besides the confirmation? There could be a configuration problem or maybe the events you're looking for simply haven't occurred yet. Make sure you've set everything up properly to receive the events you want, and keep an eye on the AWS environment to see if those events happen and trigger the notifications you're after.

Thanks,

Ratnakar