---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Set up requirements in AWS

# Set up your AWS Management Console for the AWS Inspector integration {#ariaid-title1}

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

Complete the following setup steps in your AWS Management Console environment before you install and configure the AWS Integration for Security Exposure Management Integration in your ServiceNow AI Platform® instance.

## Before you begin

Role required: AWS account and credentials

## Procedure

1. Navigate to the AWS Management Console and sign in.
2. Navigate to IAM (Identity and Access Management).
3. Create an IAM user or use an existing IAM user with programmatic access.
4. Attach the `AmazonInspector2ReadOnlyAccess` policy to the user or role to provide access to the Inspector List Findings v2 API.
5. If you're using cross-account access, create an IAM role with a trust policy and note the Role ARN.
6. Generate and securely store the Access Key ID and Secret Access Key.  
   These credentials are required when you configure the AWS Integration for Security Exposure Management Integration in your ServiceNow AI Platform® instance.
   {#aws-inspector-setup__table_fbz_jbp_53c__entry__2}

   | Field | Description |
   |-|-|
   | Access key | AWS access key ID for the IAM user. |
   | Secret Key | AWS secret access key (encrypted). |
   | Role ARN | ARN of the IAM role for STS AssumeRole. |
   | Region | AWS region(s) you want to import findings from. |
   [Table 1. AWS Credential fields]

   {#aws-inspector-setup__table_fbz_jbp_53c}  
   Note:  
   The integration uses AWS Signature Version 4 (SigV4) for request signing. When using Role ARN, the integration first calls AWS STS AssumeRole to obtain temporary security credentials (valid for
   3600 seconds).