選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Creating the AWS Service Management Connector Sync user

焦點模式
Creating the AWS Service Management Connector Sync user - AWS Service Management Connector
此頁面尚未翻譯為您的語言。 請求翻譯

This section describes how to create the AWS Sync user and associate the appropriate IAM permission. To perform this task, you need IAM permissions to create new users. The following steps to create a Sync user and End user are not required if you use the AWS CloudFormation template to deploy the permissions. Review Setting baseline permissions for AWS Service Management Connector for ServiceNow for more information.

Note

The AWS CloudFormation template to set up the AWS configurations of the Connector for ServiceNow creates the Sync user and End user with the required permissions for all the supported integrations.

To create AWS Service Management Connector sync user
  1. Follow the instructions in Creating an IAM user in your AWS account to create a sync user (SMSyncUser). The user needs programmatic and AWS Management Console access to follow the Connector for ServiceNow installation instructions.

  2. Set permissions for your sync user (SMSyncUser). Choose Attach existing policies directly and select:

    • AWSServiceCatalogAdminReadOnlyAccess (AWS managed policy)

    • AmazonSSMReadOnlyAccess (AWS managed policy)

    • AWSConfigUserAccess (AWS managed policy)

    • AWSSupportAccess (AWS managed policy)

  3. Create this policy: ConfigBidirectionalPolicy. Then follow the instructions in Creating IAM Policies, and add this code in the JSON editor:

    { "Version": "2012-10-17", "Statement": [ { "Action": [ "cloudformation:RegisterType", "cloudformation:DescribeTypeRegistration", "cloudformation:DeregisterType", "config:PutResourceConfig" ], "Resource": "*", "Effect": "Allow" } ] }

    The provided AWS Configuration template consists of two policies: ConfigBiDirectionalPolicy and SecurityHubPolicy.

  4. Create this policy: SecurityHubPolicy. Then follow the instructions in Creating IAM policies, and add this code in the JSON editor:

    { "Version": "2012-10-17", "Statement": [ { "Action": [ "sqs:ReceiveMessage", "sqs:DeleteMessage" ], "Resource": "<add sqs ARN here> ", "Effect": "Allow" }, { "Action": [ "securityhub:BatchUpdateFindings" ], "Resource": "*", "Effect": "Allow" } ] }
  5. Create this policy: OpsCenterExecutionPolicy. Then follow the instructions in Creating IAM Policies and add this code in the JSON editor:

    { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ssm:CreateOpsItem", "ssm:GetOpsItem", "ssm:UpdateOpsItem", "ssm:DescribeOpsItems" ], "Resource": "*" } ] }
  6. Create this policy: AWSIncidentBaselinePolicy. Then follow the instructions in Creating IAM Policies and add this code in the JSON editor:

    { "Version": "2012-10-17", "Statement": [ { "Action": [ "ssm-incidents:ListIncidentRecords", "ssm-incidents:GetIncidentRecord", "ssm-incidents:UpdateRelatedItems", "ssm-incidents:ListTimelineEvents", "ssm-incidents:GetTimelineEvent", "ssm-incidents:UpdateIncidentRecord", "ssm-incidents:ListRelatedItems", "ssm:ListOpsItemRelatedItems" ], "Resource": "*", "Effect": "Allow" } ] }
  7. [Optional] Create this policy: AWSChangeManagerCloudtrailPolicy. Then follow the instructions in Creating IAM Policies and add this code in the JSON editor:

    { "Version": "2012-10-17", "Statement": [ { "Action": [ "cloudtrail:DescribeQuery", "cloudtrail:ListEventDataStores", "cloudtrail:StartQuery", "cloudtrail:GetQueryResults" ], "Resource": "*", "Effect": "Allow" } ] }
  8. Create this policy: DescribeWorkSpacesPolicy. Then follow the instructions in Creating IAM Policies and add this code in the JSON editor:

    { "Statement": [ { "Action": ["workspaces:DescribeWorkspaces"], "Effect": "Allow", "Resource": "*" } ], "Version": "2012-10-17" }
  9. Add a policy that allows budgets:ViewBudget on all resources (*).

  10. Review and choose Create User.

  11. Note the access and secret access information. Download the .csv file that contains the user credential information.

Note

To align with best practices, AWS recommends periodically rotating IAM user access keys. For more information, refer to Manage access keys for IAM users.

隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。