You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sentinel/connect-aws-s3-waf.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Use the Amazon Web Services (AWS) S3-based Web Application Firewall
4
4
author: yelevin
5
5
ms.author: yelevin
6
6
ms.topic: how-to
7
-
ms.date: 08/18/2024
7
+
ms.date: 11/26/2024
8
8
appliesto:
9
9
- Microsoft Sentinel in the Azure portal
10
10
- Microsoft Sentinel in the Microsoft Defender portal
@@ -69,19 +69,21 @@ To simplify the onboarding process, the **Amazon Web Services S3 WAF** connector
69
69
70
70
To run the script to set up the AWS environment, use the following steps:
71
71
72
-
1.From the Microsoft Sentinel navigation menu, select **Data connectors**.
72
+
1.In the Azure portal, from the Microsoft Sentinel navigation menu, expand **Configuration** and select **Data connectors**.
73
73
74
-
1. Select **Amazon Web Services S3 WAF**from the data connectors gallery.
74
+
In the Defender portal, from the quick launch menu, expand **Microsoft Sentinel > Configuration**and select **Data connectors**.
75
75
76
-
If you don't see the connector, install the Amazon Web Services solution from the **Content Hub** in Microsoft Sentinel, or update the solution to the latest version.
76
+
1. Select **Amazon Web Services S3 WAF** from the list of data connectors.
77
+
78
+
If you don't see the connector, install the Amazon Web Services solution from the **Content hub** under **Content management** in Microsoft Sentinel, or update the solution to the latest version.
77
79
78
80
1. In the details pane for the connector, select **Open connector page**.
79
81
80
82
:::image type="content" source="media/connect-aws-s3-waf/find-aws-waf-connector.png" alt-text="Screenshot of data connectors gallery.":::
81
83
82
84
1. In the **Configuration** section, under **1. AWS CloudFormation Deployment**, select the [AWS CloudFormation Stacks](https://aka.ms/awsCloudFormationLink#/stacks/create) link. This opens the AWS console in a new browser tab.
83
85
84
-
1. Return to the Microsoft Sentinel tab. Select **Download** under *Template 1: OpenID Connect authentication deployment* to download the template that creates the OIDC web identity provider. The template is downloaded as a JSON file to your designated downloads folder.
86
+
1. Return to the tab of the portal where you have Microsoft Sentinel open. Select **Download** under *Template 1: OpenID Connect authentication deployment* to download the template that creates the OIDC web identity provider. The template is downloaded as a JSON file to your designated downloads folder.
85
87
86
88
> [!NOTE]
87
89
> If you have the older AWS S3 connector, and therefore you already have an OIDC web identity provider, you can skip this step.
@@ -118,7 +120,11 @@ Follow the instructions on the AWS Console page for creating a new stack.
118
120
119
121
1. Choose a name for the stack.
120
122
121
-
1. Where prompted, enter your Microsoft Sentinel Workspace ID. You can find it in **Microsoft Sentinel** > **Configuration** > **Settings** > **Workspace settings**.
123
+
1. Where prompted, enter your Microsoft Sentinel Workspace ID. To find your Workspace ID:
124
+
125
+
- In the Azure portal, in the Microsoft Sentinel navigation menu, expand **Configuration** and select **Settings**. Select the **Workspace settings** tab, and find the Workspace ID on the Log Analytics workspace page.
126
+
127
+
- In the Defender portal, in the quick launch menu, expand **System** and select **Settings**. Select **Microsoft Sentinel**, then select **Log Analytics settings** under **Settings for `[WORKSPACE_NAME]`**. Find the Workspace ID on the Log Analytics workspace page, which opens in a new browser tab.
122
128
123
129
1. Advance through the rest of the process and create the stack.
0 commit comments