---
title: Configuring access to CI data on your AWS account
description: To ensure secure and reliable communications, the Discovery process communicates with your cloud provider accounts and cloud resources through one or more MID Servers. You can set up the MID Servers on your network or in one of your cloud networks.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-asset-management/cloud-cost-management/aws-midserver-config-cloudin.html
release: australia
product: Cloud Cost Management
classification: cloud-cost-management
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Configure Cloud Cost Management for AWS, Configure, Cloud Cost Management, IT Asset Management, Asset Management]
---

# Configuring access to CI data on your AWS account

To ensure secure and reliable communications, the Discovery process communicates with your cloud provider accounts and cloud resources through one or more MID Servers. You can set up the MID Servers on your network or in one of your cloud networks.

## Requirements

**Important:** This configuration process applies only if you use the Discovery application to discover cloud resources. Skip this process if you use a different method for discovering resources.

AWS: There must be an internal network connection between the MID Servers and the AWS Cloud API endpoints: \*.amazonaws.com.

## Detailed instructions

See [Setup AWS service accounts](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-operations-management/setup-aws-service-accounts.md).

## MID Server settings for Cloud Cost Management

**Note:** MID Server minimum memory size should be 4 GB.

<table id="table_t5k_dvd_1jb"><thead><tr><th>

Setting

</th><th>

Value

</th></tr></thead><tbody><tr><td>

Supported Applications

</td><td>

Cloud Actions

</td></tr><tr><td>

Capabilities

</td><td>

The **ALL** setting includes all required applications and capabilities. Alternatively, you can specify the following settings:

**Note:** You can specify the following settings for any number of MID Servers. If you specify multiple MID Servers, then Discovery, billing data download operations, and actions that are recommended by Cloud Cost Management are assigned to one of the MID Servers at random.

 Option 1: To use this MID Server only for AWS, specify both of the following values:

-   Cloud Actions
-   AWS

 Option 2: To use this MID Server for all providers, specify the following values:

-   Cloud Actions
-   AWS
-   Azure

</td></tr></tbody>
</table>## Using a proxy server

You can use a proxy server for the Cloud Cost Management MID Server. See [Proxy server configuration for your Cloud Cost Management MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/cloud-cost-management/aws-mid-proxy-cloudin.md).

**Related topics**  


[MID Servers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_MIDServerConfiguration.md)

[Install a MID Server on Windows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-install-prereqs.md)

[Install a MID Server on Linux](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_InstallAMIDServerOnLinux.md)