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
+67-69Lines changed: 67 additions & 69 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,20 +8,18 @@ ms.custom: mode-other
8
8
---
9
9
# Connect your AWS accounts to Microsoft Defender for Cloud
10
10
11
-
With cloud workloads commonly spanning multiple cloud platforms, cloud security services must do the same.
11
+
With cloud workloads commonly spanning multiple cloud platforms, cloud security services must do the same. Microsoft Defender for Cloud protects workloads in Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
12
12
13
-
Microsoft Defender for Cloud protects workloads in Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
13
+
To protect your AWS-based resources, you can connect an AWS account with either:
14
14
15
-
To protect your AWS-based resources, you can connect an account with one of two mechanisms:
15
+
-**Native cloud connector** (recommended) - Provides an agentless connection to your AWS account that you can extend with Defender for Cloud's Defender plans to secure your AWS resources:
16
16
17
-
-**Classic cloud connectors experience** - As part of the initial multicloud offering, we introduced these cloud connectors as a way to connect your AWS and GCP projects. If you've already configured an AWS connector through the classic cloud connectors experience, we recommend deleting these connectors (as explained in [Remove classic connectors](#remove-classic-connectors)), and connecting the account again using the newer mechanism. If you don't do this before creating the new connector through the environment settings page, do so afterwards to avoid seeing duplicate recommendations.
17
+
-[**Cloud Security Posture Management (CSPM)**](overview-page.md) assesses your AWS resources according to AWS-specific security recommendations and reflects your security posture in your secure score. The [asset inventory](asset-inventory.md) gives you one place to see all of your protected AWS resources. The [regulatory compliance dashboard](regulatory-compliance-dashboard.md) shows your compliance with built-in standards specific to AWS, including AWS CIS, AWS PCI DSS, and AWS Foundational Security Best Practices.
18
+
-[**Microsoft Defender for Servers**](defender-for-servers-introduction.md) brings threat detection and advanced defenses to [supported Windows and Linux EC2 instances](supported-machines-endpoint-solutions-clouds-servers.md?tabs=tab/features-multicloud).
19
+
-[**Microsoft Defender for Containers**](defender-for-containers-introduction.md) brings threat detection and advanced defenses to [supported Amazon EKS clusters](supported-machines-endpoint-solutions-clouds-containers.md).
20
+
-[**Microsoft Defender for SQL**](defender-for-sql-introduction.md) brings threat detection and advanced defenses to your SQL Servers running on AWS EC2, AWS RDS Custom for SQL Server.
18
21
19
-
-**Environment settings page** (recommended) - This page provides a greatly improved, simpler, onboarding experience (including auto provisioning). This mechanism also extends Defender for Cloud's enhanced security features to your AWS resources:
20
-
21
-
-**Defender for Cloud's CSPM features** extend to your AWS resources. This agentless plan assesses your AWS resources according to AWS-specific security recommendations and these are included in your secure score. The resources will also be assessed for compliance with built-in standards specific to AWS (AWS CIS, AWS PCI DSS, and AWS Foundational Security Best Practices). Defender for Cloud's [asset inventory page](asset-inventory.md) is a multicloud enabled feature helping you manage your AWS resources alongside your Azure resources.
22
-
-**Microsoft Defender for Containers** brings threat detection and advanced defenses to your Amazon EKS clusters. This plan includes Kubernetes threat protection, behavioral analytics, Kubernetes best practices, admission control recommendations and more. You can view the full list of available features in [Defender for Containers feature availability](supported-machines-endpoint-solutions-clouds-containers.md).
23
-
-**Microsoft Defender for Servers** brings threat detection and advanced defenses to your Windows and Linux EC2 instances. This plan includes the integrated license for Microsoft Defender for Endpoint, security baselines and OS level assessments, vulnerability assessment scanning, adaptive application controls (AAC), file integrity monitoring (FIM), and more. You can view the full list of available features in the [feature availability table](supported-machines-endpoint-solutions-clouds-servers.md?tabs=tab/features-multicloud).
24
-
-**Microsoft Defender for SQL** brings threat detection and advanced defenses to your SQL Servers running on AWS EC2, AWS RDS Custom for SQL Server. This plan includes the advanced threat protection and vulnerability assessment scanning. You can view the [full list of available features](defender-for-sql-introduction.md).
22
+
-**Classic cloud connector** - Requires configuration in your AWS account to create a user that Defender for Cloud can use to connect to your AWS environment. If you have classic cloud connectors, we recommend that you [delete these connectors](#remove-classic-connectors) and use the native connector to reconnect to the account. Using both the classic and native connectors can produce duplicate recommendations.
25
23
26
24
For a reference list of all the recommendations Defender for Cloud can provide for AWS resources, see [Security recommendations for AWS resources - a reference guide](recommendations-reference-aws.md).
27
25
@@ -32,7 +30,6 @@ This screenshot shows AWS accounts displayed in Defender for Cloud's [overview d
32
30
You can learn more by watching this video from the Defender for Cloud in the Field video series:
33
31
-[New AWS connector](episode-one.md)
34
32
35
-
36
33
::: zone pivot="env-settings"
37
34
38
35
## Availability
@@ -44,9 +41,10 @@ You can learn more by watching this video from the Defender for Cloud in the Fie
44
41
|Required roles and permissions:|**Contributor** permission for the relevant Azure subscription. <br> **Administrator** on the AWS account.|
45
42
|Clouds:|:::image type="icon" source="./media/icons/yes-icon.png"::: Commercial clouds<br>:::image type="icon" source="./media/icons/no-icon.png"::: National (Azure Government, Azure China 21Vianet)|
46
43
47
-
48
44
## Prerequisites
49
45
46
+
The native cloud connector requires:
47
+
50
48
- Access to an AWS account.
51
49
52
50
-**To enable the Defender for Containers plan**, you'll need:
@@ -105,27 +103,11 @@ You can learn more by watching this video from the Defender for Cloud in the Fie
105
103
106
104
## Connect your AWS account
107
105
108
-
Follow the steps below to create your AWS cloud connector.
106
+
**To connect your AWS account to Defender for Cloud with a native connector**:
109
107
110
-
### Remove 'classic' connectors
108
+
1. If you have any classic connectors, [remove them](#remove-classic-connectors).
111
109
112
-
If you have any existing connectors created with the classic cloud connectors experience, remove them first:
113
-
114
-
1. Sign in to the [Azure portal](https://portal.azure.com).
115
-
116
-
1. Navigate to **Defender for Cloud** > **Environment settings**.
117
-
118
-
1. Select the option to switch back to the classic connectors experience.
119
-
120
-
:::image type="content" source="media/quickstart-onboard-gcp/classic-connectors-experience.png" alt-text="Switching back to the classic cloud connectors experience in Defender for Cloud.":::
121
-
122
-
1. For each connector, select the three dot button **…** at the end of the row, and select **Delete**.
123
-
124
-
1. On AWS, delete the role ARN, or the credentials created for the integration.
125
-
126
-
### Create a new connector
127
-
128
-
**To create a new connector**:
110
+
Using both the classic and native connectors can produce duplicate recommendations.
129
111
130
112
1. Sign in to the [Azure portal](https://portal.azure.com).
131
113
@@ -179,6 +161,22 @@ If you have any existing connectors created with the classic cloud connectors ex
179
161
180
162
Defender for Cloud will immediately start scanning your AWS resources and you'll see security recommendations within a few hours. For a reference list of all the recommendations Defender for Cloud can provide for AWS resources, see [Security recommendations for AWS resources - a reference guide](recommendations-reference-aws.md).
181
163
164
+
### Remove 'classic' connectors
165
+
166
+
If you have any existing connectors created with the classic cloud connectors experience, remove them first:
167
+
168
+
1. Sign in to the [Azure portal](https://portal.azure.com).
169
+
170
+
1. Navigate to **Defender for Cloud** > **Environment settings**.
171
+
172
+
1. Select the option to switch back to the classic connectors experience.
173
+
174
+
:::image type="content" source="media/quickstart-onboard-gcp/classic-connectors-experience.png" alt-text="Switching back to the classic cloud connectors experience in Defender for Cloud.":::
175
+
176
+
1. For each connector, select the three dot button **…** at the end of the row, and select **Delete**.
177
+
178
+
1. On AWS, delete the role ARN, or the credentials created for the integration.
179
+
182
180
::: zone-end
183
181
184
182
@@ -353,44 +351,44 @@ The following IAM permissions are needed to discover AWS resources:
353
351
354
352
| DataCollector | AWS Permissions |
355
353
|--|--|
356
-
| API Gateway | apigateway:GET|
357
-
| Application Auto Scaling | application-autoscaling:Describe*|
358
-
| Auto scaling | autoscaling-plans:Describe* <br> autoscaling:Describe*|
0 commit comments