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/defender-for-cloud/quickstart-onboard-aws.md
+50-5Lines changed: 50 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Connect your AWS account to Microsoft Defender for Cloud
3
3
description: Defend your AWS resources with Microsoft Defender for Cloud
4
4
ms.topic: quickstart
5
-
ms.date: 06/15/2022
5
+
ms.date: 06/19/2022
6
6
zone_pivot_groups: connect-aws-accounts
7
7
ms.custom: mode-other
8
8
---
@@ -87,7 +87,7 @@ You can learn more from the product manager about Microsoft Defender for Cloud's
87
87
> [!NOTE]
88
88
> To enable the Azure Arc auto-provisioning, you'll need an **Owner** permission on the relevant Azure subscription.
89
89
90
-
- If you want to manually install Azure Arc on your existing and future EC2 instances, use the [EC2 instances should be connected to Azure Arc](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/231dee23-84db-44d2-bd9d-c32fbcfb42a3) recommendation to identify instances that do not have Azure Arc installed.
90
+
- If you want to manually install Azure Arc on your existing and future EC2 instances, use the [EC2 instances should be connected to Azure Arc](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/231dee23-84db-44d2-bd9d-c32fbcfb42a3) recommendation to identify instances that don't have Azure Arc installed.
91
91
92
92
- Additional extensions should be enabled on the Arc-connected machines.
93
93
- Microsoft Defender for Endpoint
@@ -154,7 +154,7 @@ If you have any existing connectors created with the classic cloud connectors ex
154
154
155
155
- (Optional) Select **Configure**, to edit the configuration as required.
156
156
157
-
1. By default the **Containers** plan is set to **On**. This is necessary to have Defender for Containers protect your AWS EKS clusters. Ensure you have fulfilled the [network requirements](./defender-for-containers-enable.md?pivots=defender-for-container-eks&source=docs&tabs=aks-deploy-portal%2ck8s-deploy-asc%2ck8s-verify-asc%2ck8s-remove-arc%2caks-removeprofile-api#network-requirements) for the Defender for Containers plan.
157
+
1. By default the **Containers** plan is set to **On**. This is necessary to have Defender for Containers protect your AWS EKS clusters. Ensure you've fulfilled the [network requirements](./defender-for-containers-enable.md?pivots=defender-for-container-eks&source=docs&tabs=aks-deploy-portal%2ck8s-deploy-asc%2ck8s-verify-asc%2ck8s-remove-arc%2caks-removeprofile-api#network-requirements) for the Defender for Containers plan.
158
158
159
159
> [!Note]
160
160
> Azure Arc-enabled Kubernetes, the Defender Arc extension, and the Azure Policy Arc extension should be installed. Use the dedicated Defender for Cloud recommendations to deploy the extensions (and Arc, if necessary) as explained in [Protect Amazon Elastic Kubernetes Service clusters](defender-for-containers-enable.md?tabs=defender-for-container-eks).
@@ -170,7 +170,7 @@ If you have any existing connectors created with the classic cloud connectors ex
170
170
171
171
1. Download the CloudFormation template.
172
172
173
-
1. Using the downloaded CloudFormation template, create the stack in AWS as instructed on screen. If you are onboarding a management account, you'll need to run the CloudFormation template both as Stack and as StackSet. Connectors will be created for the member accounts up to 24 hours after the onboarding.
173
+
1. Using the downloaded CloudFormation template, create the stack in AWS as instructed on screen. If you're onboarding a management account, you'll need to run the CloudFormation template both as Stack and as StackSet. Connectors will be created for the member accounts up to 24 hours after the onboarding.
174
174
175
175
1. Select **Next: Review and generate**.
176
176
@@ -346,6 +346,51 @@ For other operating systems, the SSM Agent should be installed manually using th
346
346
-[Install SSM Agent for a hybrid environment (Windows)](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-install-managed-win.html)
347
347
-[Install SSM Agent for a hybrid environment (Linux)](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-install-managed-linux.html)
348
348
349
+
### For the CSPM plan, what IAM permissions are needed to discover AWS resources?
350
+
351
+
The following IAM permissions are needed to discover AWS resources:
352
+
353
+
| DataCollector | AWS Permissions |
354
+
|--|--|
355
+
| API Gateway | apigateway:GET|
356
+
| Application Auto Scaling | application-autoscaling:Describe*|
357
+
| Auto scaling | autoscaling-plans:Describe* <br> autoscaling:Describe*|
@@ -359,4 +404,4 @@ You can check out the following blogs:
359
404
Connecting your AWS account is part of the multicloud experience available in Microsoft Defender for Cloud. For related information, see the following page:
360
405
361
406
-[Security recommendations for AWS resources - a reference guide](recommendations-reference-aws.md).
362
-
-[Connect your GCP projects to Microsoft Defender for Cloud](quickstart-onboard-gcp.md)
407
+
-[Connect your GCP projects to Microsoft Defender for Cloud](quickstart-onboard-gcp.md)
0 commit comments