ServiceNow's ITOM Discovery enables you to discover cloud services in AWS. Since the London release of the ServiceNow platform, our AWS Cloud Discovery offering has evolved. Servicenow discovery supports both metadata and deep discovery of AWS Cloud.
- Metadata discovery is the discovery of the foundational resources and other details on the metadata.
- Deep discovery is the discovery of OS-level details.
With that being said, here are the options for customers to implement ServiceNow discovery for AWS Cloud.
Option 1:
Cloud Discovery (metadata)-- Iaas/Paas/Faas/CaaS using Cross Assume Role
CaaS (deep discovery) - Using Containerized MID for the deep discovery of EKS clusters and containers
Option 2:
Cloud Discovery (metadata)-- Iaas/Paas/Faas/CaaS using Cross Assume Role
CaaS(deep discovery) - Auto Scheduler (NO Containerized MID) for the deep discovery of EKS clusters and containers
Option 3:
Cloud Discovery (metadata)-- Iaas/Paas/Faas/CaaS using Cross Assume Role
CaaS(deep discovery) - SG Connector (NO Containerized MID)
Option 4:
SG Connector (meta data and deep discovery) - Iaas/Paas/Faas/CaaS and NO MID deployment
Option 5:
Cloud Discovery (metadata)-- Iaas/Paas/Faas/CaaS using Cross Assume Role
CaaS(deep discovery) - Credential Based Discovery (need MID deployment)
Option 6:
Cloud Discovery (meta data)-- Iaas/Paas/Faas/CaaS using cross assume role
CaaS(deep discovery) - Any option from 1-5
IaaS [EC2] (deep discovery) - Deploy ACC in every EC2 and MID in transit VPC
Option 7:
Event Driven Discovery using CloudWatch Events and Simple notification service
Summarizing the above options:
Other Useful links:
AWS Cloud Discovery - docs.
Cross Assume Role Discovery - blog
Cross Assume Role Discovery - Video
Event Driven Discovery - docs
1 Comment
