Skip to content

Commit 5f4c0f9

Browse files
committed
Learn Editor: Update connect-aws.md
1 parent 65de8ab commit 5f4c0f9

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

articles/sentinel/connect-aws.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,15 @@ ms.topic: how-to
77
ms.date: 01/31/2024
88
---
99

10+
---
11+
title: Connect Microsoft Sentinel to Amazon Web Services to ingest AWS service log data
12+
description: Use the AWS connector to delegate Microsoft Sentinel access to AWS resource logs, creating a trust relationship between Amazon Web Services and Microsoft Sentinel.
13+
author: yelevin
14+
ms.author: yelevin
15+
ms.topic: how-to
16+
ms.date: 01/31/2024
17+
---
18+
1019
# Connect Microsoft Sentinel to Amazon Web Services to ingest AWS service log data
1120

1221
Use the Amazon Web Services (AWS) connectors to pull AWS service logs into Microsoft Sentinel. These connectors work by granting Microsoft Sentinel access to your AWS resource logs. Setting up the connector establishes a trust relationship between Amazon Web Services and Microsoft Sentinel. This is accomplished on AWS by creating a role that gives permission to Microsoft Sentinel to access your AWS logs.
@@ -213,6 +222,8 @@ The following instructions apply for public **Azure Commercial clouds** only. Fo
213222
| **Name** | Example: "*MicrosoftSentinelRole*". | Choose a meaningful name that includes a reference to Microsoft Sentinel. |
214223

215224

225+
1. Edit the new role's trust policy and add another condition:<br>`"sts:RoleSessionName": "MicrosoftSentinel_{WORKSPACE_ID)"`
226+
216227
1. Edit the new role's trust policy and add another condition:<br>`"sts:RoleSessionName": "MicrosoftSentinel_{WORKSPACE_ID)"`
217228

218229
The finished trust policy should look like this:

0 commit comments

Comments
 (0)