---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Install and configure MID Servers to access cloud environments

# Install and configure MID Servers to access cloud environments {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Install and configure the MID Servers correctly to enable ITOM products to access to the cloud resources.

## Before you begin

Role required: discovery_admin or sn_cmp.cloud_admin (for Cloud Provisioning and Governance)

## About this task

<br />

## Procedure

1. For IP-based discovery, [Installing the MID Server](https://www.servicenow.com/docs/access?context=mid-server-installation&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) on a server inside the cloud environment, inside a Virtual Private Cloud (VPC).  
   For example, if you are configuring access to AWS service accounts using IAM roles, install the MID Server at the Amazon EC2 instance.  
   Important:  
   If you configure AWS credentials at ServiceNow AI Platform, the location of the MID Server doesn't matter.
   If your organization has multiple VPC segments, deploy the MID Servers in a manage-mentor transit VPC.
2. Activate IP-based discovery jobs to access the compute layer using agentless credentials.
3. Configure the MID Server with the capabilities necessary for the cloud environment you are planning to discover.  
   You can select the <kbd class="ph userinput">ALL</kbd> capability or configure specific capabilities for tighter security.

   Add Cloud Management in supported application in MID Server for Cloud Provisioning and Governance requests to be processed.
   {#mid-server-configuration-cloud__table_m3g_rw5_3pb__entry__3}

   | Cloud environment | MID Server capability required by Cloud Discovery | MID Server capability required by Cloud Provisioning and Governance |
   |-|-|-|
   | Amazon AWS Cloud | <kbd class="ph userinput">AWS</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | <kbd class="ph userinput">AWS</kbd> or <kbd class="ph userinput">Cloud Management</kbd> |
   | Microsoft Azure Cloud | <kbd class="ph userinput">Azure</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | <kbd class="ph userinput">Azure</kbd> or <kbd class="ph userinput">Cloud Management</kbd> |
   | Google Cloud | <kbd class="ph userinput">Google</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | <kbd class="ph userinput">Google</kbd> or <kbd class="ph userinput">Cloud Management</kbd> |
   | IBM Cloud Platform | <kbd class="ph userinput">IBM</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | N/A |
   | Oracle Cloud Infrastructure (OCI) | <kbd class="ph userinput">OCI</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | N/A |
   | OpenStack | <kbd class="ph userinput">OpenStack</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | N/A |
   | Red Hat Virtualization (RHV) | <kbd class="ph userinput">RHV</kbd> or <kbd class="ph userinput">Cloud Management</kbd> or <kbd class="ph userinput">ALL</kbd> | N/A |
   [ ]

   {#mid-server-configuration-cloud__table_m3g_rw5_3pb}
4. If the MID Servers must go through an unauthenticated proxy server to access cloud resources, modify the agent\\conf\\wrapper-override.conf file, as follows:  

       wrapper.java.additional.1=-Dhttp.proxySet=true
                wrapper.java.additional.2=-Dhttp.proxyHost=<proxyHost> 
                wrapper.java.additional.3=-Dhttp.proxyPort=<proxyPort> 
                wrapper.java.additional.4=-DuseProxy=true

5. If you're using an authenticated proxy server, configure the MID Server parameters in the config.xml file.  
   For a description of the parameter values, see the Proxy server parameters section in [MID Server parameters](https://www.servicenow.com/docs/access?context=mid-server-parameters&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).
* **[Proxy server configuration for MID Servers used for Cloud Discovery and Cloud Provisioning and Governance](https://servicenow-prod.fluidtopics.net/1UI82D42sKngs~0SC3QBRw)**   
  You can configure the MID Server for Cloud Provisioning and Governance to use a proxy server. Using a proxy server supports all cloud-based activities such as running Discovery, billing downloads, provisioning virtual machines, and running life-cycle operations on virtual machines.
* **[Cloud Request Retry Configuration](https://servicenow-prod.fluidtopics.net/5kvYuIsaxuss5qq0E21yDA)**   
  If a request is throttled by a cloud provider during Discovery, Cloud Request Retry Configuration provides a customizable method to retry requests. Discovery and Service Mapping Patterns includes a retry configuration for AWS and Azure. You can customize the included configuration or create your own.

**Related reference**   

* [Proxy server configuration for MID Servers used for Cloud Discovery and Cloud Provisioning and Governance](https://servicenow-prod.fluidtopics.net/1UI82D42sKngs~0SC3QBRw "You can configure the MID Server for Cloud Provisioning and Governance to use a proxy server. Using a proxy server supports all cloud-based activities such as running Discovery, billing downloads, provisioning virtual machines, and running life-cycle operations on virtual machines.")