Due to limited discovery cloud asset discovery capabilities in ServiceNow many customers choose to use Cloudaware CMDB to populate or enrich cloud resources in ServiceNow via Cloudaware. For a complete gap analysis of discoverable objects in ServiceNow vs Cloudaware click here.
Decide On The Integration Approach
There are two approaches to integrating Cloudaware and ServiceNow - push and pull. These approaches have unique pros and cons.
Push Approach
Using a push approach, responsibility for most of the integration work is in the Cloudaware corner. Cloudaware is responsible for pushing assets and configuration into ServiceNow in a timely manner. Customer’s main responsibility is to provide Cloudaware with access and define a custom class to contain Cloudaware data. Sample class definition can be found here. The disadvantage of the push approach is the customer is now continually dependent on Cloudaware for any schema modifications in the custom Class. Should customer want to change frequency or the types of attributes that Cloudaware sends to ServiceNow, it will have to request such changes from Cloudaware. Cloudaware handles these requests with the same priority as all other customer related service requests.