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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure MID Server for AWS KMS access

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

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure MID Server properties to enable Key Management Service (KMS) key 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/DZ1qVBl~rfTV9JTZFLlAkg "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 AWS KMS key to encrypt sensitive credentials. For more information, see [Create a Customer Managed AWS KMS Key](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2150362#awskey).
{#config-mid-server-aws-kms-access__ul_bn5_vkv_zfc}

Role required: discovery_admin

## About this task

Using a dedicated key enhances security by verifying that applicative credentials are encrypted and securely retrieved at runtime, without being exposed in plain text. This step is optional and only necessary if you plan to
use applicative credentials during discovery. To configure the MID Server to support secure credential handling during SSM Agent discovery, set the mid.discovery.aws_ssm.kms_key_name property to the name of the AWS KMS key. Then, set the mid.discovery.aws_ssm.kms_key_region property to the region where the key is located.

## Procedure

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

*[\>]: and then