---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure MID Server for AWS S3 access

# Configure MID Server for AWS S3 access {#ariaid-title1}

* Release version: Zurich
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure MID Server properties to enable Simple Storage Service (S3) access from the ServiceNow AI Platform® when performing Systems Manager (SSM) Agent discovery.

## Before you begin

Confirm the following:

* You have at least one MID Server installed and in the Up state. For more information, see [Install and configure MID Servers to access cloud environments](https://www.servicenow.com/docs/GQW0uQE4eOrZuGS0eqXpqQ "Install and configure the MID Servers correctly to enable ITOM products to access to the cloud resources.").
* You have an AWS credential that allows the MID Server to access and make API calls into the AWS environment. For more information, see [AWS Access for MID Server](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2150362#midawsaccess).
* You created a custom S3 bucket with necessary access enabled for the IAM roles. For more information, see [Setting up an S3 Bucket](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2150362#s3bucket) and [Setting up a Policy for accessing the S3 Bucket](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2150362#bucketpolicysetup).
{#configure-mid-server-aws-s3-access__ul_bn5_vkv_zfc}

Role required: discovery_admin

## About this task

Because the SSM Run Command console has a 24,000-character limit, results that exceed this limit must be stored in and retrieved from an S3 bucket. For Put File commands, the S3 bucket also serves as a transfer point between
the MID Server and the AWS environment, enabling file delivery to target devices via SSM. To configure the MID Server to support these S3-based operations, set the mid.discovery.aws_ssm.s3_bucket_name property to the name of the S3 bucket used for SSM Agent discovery. Then, specify the
bucket's region in the mid.discovery.aws_ssm.s3_bucket_region property.

## Procedure

1. Navigate to AllMID ServerProperties.
2. In the Name field, enter <kbd class="ph userinput">mid.discovery.aws_ssm.s3_bucket_name</kbd>.
3. Double-click the Value field to perform inline editing.
4. Enter the name of the S3 bucket.
5. Select the check mark (![check mark icon]()) icon.
6. In the Name field, enter <kbd class="ph userinput">mid.discovery.aws_ssm.s3_bucket_region</kbd>.
7. Double-click the Value field to perform inline editing.
8. Enter the name of the region where the S3 bucket is located.
9. Select the check mark (![check mark icon]()) icon.

*[\>]: and then