Configure MID Server for AWS S3 access
Configure MID Server properties to enable Simple Storage Service (S3) access from the ServiceNow AI Platform® when performing Systems Manager (SSM) Agent discovery.
Antes de Iniciar
- 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.
- 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.
- You created a custom S3 bucket with necessary access enabled for the IAM roles. For more information, see Setting up an S3 Bucket and Setting up a Policy for accessing the S3 Bucket.
Role required: discovery_admin
Por Que e Quando Desempenhar Esta Tarefa
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.
Procedimento
- Navigate to .
- In the Name field, enter mid.discovery.aws_ssm.s3_bucket_name.
- Double-click the Value field to perform inline editing.
- Enter the name of the S3 bucket.
-
Select the check mark (
) icon.
- In the Name field, enter mid.discovery.aws_ssm.s3_bucket_region.
- Double-click the Value field to perform inline editing.
- Enter the name of the region where the S3 bucket is located.
-
Select the check mark () icon.