visibility into your cloud infrastructure is critical in optimizing your cloud spend and also for managing your operations security bring your own licensing and compliance servicenow's discovery feature provides visibility to these resources from major cloud providers like aws azure google cloud and ibm cloud the discovery feature also supports event driven discovery where events from the cloud provider keep the cmdb up to date the discovery feature also gives you visibility into container orchestration layers like kubernetes and aws ecs services there are two types of cloud discovery service account discovery finds resources in a service account by collecting metadata using the cloud provider's apis these apis push information in response to cloud events so this type of discovery keeps your cmdb updated for ephemeral cloud objects in near real time ip-based discovery enriches the metadata from service account discovery with deeper data like the file system installed software and process information ipb-based discovery also detects enterprise applications like oracle and sql databases and apache this data supports a variety of servicenow workflows discovery also uses cloud tags to add metadata on the application cost center and environment and the service mapping feature uses these tags to create application service maps automatically discovery supports aws organization azure management groups and google resource hierarchy which helps you identify master to member account relationships [Music] setting up discovery is easy on the discovery home page we can see our current discovery schedules discovered devices cloud service accounts and any discovery errors vue cloud resources shows the cloud resources for all your providers these tabs show more details sorted by provider back on the discovery homepage clicking here shows our current discovery schedules adding a discovery schedule takes just a few easy steps we start by clicking here to add a schedule here we'll choose the provider we want to use aws for the schedule name we'll call it aws discovery in this scenario an account has already been created so we'll select that one and then run the test which will check the account credentials are accurate once the service account has been validated we'll get verification since this is a master account we'll refresh the sub accounts once that's done we'll click next the next step is to choose which regions we want to discover by default all regions are selected but we want to choose specific regions so we'll deactivate the default option and select the specific regions we want here we have the default option to discover virtual machines by ip address but for our scenario let's disable it this way vms will be discovered through ssh or powershell finally we'll set our discovery to run every night at 2 am and we're done once the discovery is complete we can see the results here on the cloud resources dashboard we can see all the data for aws and our other cloud providers we can use filters to view data from specific regions here we can dig deeper and get a topological view of the discovered data with multi-cloud discovery on the now platform you can have near real-time discovery in just a few easy steps give it a try for more information see our product documentation knowledge base or podcast or ask a question in the servicenow community