Skip to content

Commit df7adfc

Browse files
JnHsJnHs
committed
Multicloud connector content
1 parent 92ead42 commit df7adfc

File tree

12 files changed

+547
-6
lines changed

12 files changed

+547
-6
lines changed

‎articles/azure-arc/index.yml

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -158,14 +158,18 @@ additionalContent:
158158
summary: Establish patterns for building hybrid architectures.
159159
url: /azure/cloud-adoption-framework/scenarios/hybrid/enterprise-scale-landing-zone
160160
# Card
161-
- title: App Service, Functions, and Logic Apps on Azure Arc (preview)
162-
summary: Run App Service, Functions, and Logic Apps on Azure Arc-enabled Kubernetes clusters.
163-
url: /azure/app-service/overview-arc-integration
164-
# Card
165161
- title: Azure Kubernetes Service (AKS) enabled by Azure Arc
166162
summary: Extend AKS to your on-premises environment.
167163
url: https://learn.microsoft.com/en-us/azure/aks/hybrid/aks-hybrid-options-overview
168164
# Card
165+
- title: Multicloud connector enabled by Azure Arc (preview)
166+
summary: Connect non-Azure public cloud resources to centralize management and governance in Azure.
167+
url: ./multicloud-connector/overview.md
168+
# Card
169+
- title: App Service, Functions, and Logic Apps on Azure Arc (preview)
170+
summary: Run App Service, Functions, and Logic Apps on Azure Arc-enabled Kubernetes clusters.
171+
url: /azure/app-service/overview-arc-integration
172+
# Card
169173
- title: Azure IoT Operations Preview – enabled by Azure Arc
170174
summary: Azure IoT Operations is a unified data plane for the edge that helps organizations deploy the industrial metaverse.
171175
url: /azure/iot-operations/

‎articles/azure-arc/multicloud-connector/breadcrumb/toc.yml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
- name: Azure
2+
tocHref: /azure
3+
topicHref: /azure/index
4+
items:
5+
- name: Azure Arc
6+
tocHref: /azure/azure-arc
7+
topicHref: /azure/azure-arc
8+
items:
9+
- name: Multicloud connector
10+
tocHref: /azure/azure-arc/multicloud-connector
11+
topicHref: /azure/azure-arc/multicloud-connector

‎articles/azure-arc/multicloud-connector/connect-to-aws.md

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
---
2+
title: "Connect to AWS with the multicloud connector in the Azure portal"
3+
description: "Learn how to add an AWS cloud by using the multicloud connector enabled by Azure Arc."
4+
ms.topic: how-to
5+
ms.date: 06/11/2024
6+
---
7+
8+
# Connect to AWS with the multicloud connector in the Azure portal
9+
10+
The multicloud connector enabled by Azure Arc lets you connect non-Azure public cloud resources to Azure by using the Azure portal. Currently, AWS public cloud environments are supported.
11+
12+
As part of connecting an AWS account to Azure, you deploy a CloudFormation template to the AWS account. This template creates all of the required resources for the connection.
13+
14+
> [!IMPORTANT]
15+
> Multicloud connector enabled by Azure Arc is currently in PREVIEW.
16+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
17+
18+
## Prerequisites
19+
20+
To use the multicloud connector, you need the appropriate permissions in both AWS and Azure.
21+
22+
### AWS prerequisites
23+
24+
To create the connector and to use multicloud inventory, you need the following permissions in AWS:
25+
26+
- **AmazonS3FullAccess**
27+
- **AWSCloudFormationFullAccess**
28+
- **IAMFullAccess**
29+
30+
For Arc onboarding, there are [additional prerequisites that must be met](onboard-multicloud-vms-arc.md#prerequisites).
31+
32+
When you upload your CloudFormation template, additional permissions will be requested, based on the solutions that you selected:
33+
34+
- For **Inventory**, we request **Global Read** permission to your account.
35+
- For **Arc Onboarding**, our service requires **EC2 Write** access in order to install the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview).
36+
37+
### Azure prerequisites
38+
39+
To use the multicloud connector in an Azure subscription, you need the **Contributor** built-in role.
40+
41+
If this is the first time you're using the service, you need to [register these resource providers](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider), which requires **Contributor** access on the subscription:
42+
43+
- Microsoft.HybridCompute
44+
- Microsoft.HybridConnectivity
45+
- Microsoft.AwsConnector
46+
47+
> [!NOTE]
48+
> The multicloud connector can work side-by-side with the [AWS connector in Defender for Cloud](/azure/defender-for-cloud/quickstart-onboard-aws). If you choose, you can use both of these connectors.
49+
50+
## Add your public cloud in the Azure portal
51+
52+
To add your AWS public cloud to Azure, use the Azure portal to enter details and generate a CloudFormation template.
53+
54+
1. In the Azure portal, navigate to **Azure Arc**.
55+
1. Under **Management**, select **Multicloud connectors (preview)**.
56+
1. In the **Connectors** pane, select **Create**.
57+
1. On the **Basics** page:
58+
59+
1. Select the subscription and resource group in which to create your connector resource.
60+
1. Enter a unique name for the connector and select a [supported region](overview.md#supported-regions).
61+
1. Provide the ID for the AWS account that you want to connect, and indicate whether it's a single account or an organization account.
62+
1. Select **Next**.
63+
64+
1. On the **Solutions** page, select which solutions you'd like to use with this connector and configure them. Select **Add** to enable **[Inventory](view-multicloud-inventory.md)**, **[Arc onboarding](onboard-multicloud-vms-arc.md)**, or both.
65+
66+
:::image type="content" source="media/add-aws-connector-solutions.png" alt-text="Screenshot showing the Solutions for the AWS connector in the Azure portal.":::
67+
68+
- For **Inventory**, you can modify the following options:
69+
70+
1. Choose the **AWS Services** for which you want to scan and import resources. By default, all available services are selected.
71+
1. Choose whether or not to enable periodic sync. By default, this is enabled so that the connector will scan your AWS account regularly. If you uncheck the box, your AWS account will only be scanned once.
72+
1. If **Enable periodic sync** is checked, confirm or change the **Recur every** selection to specify how often your AWS account will be scanned.
73+
1. Choose which regions to scan for resources in your AWS account. By default, all available regions are selected.
74+
1. When you have finished making selections, select **Save** to return to the **Solutions** page.
75+
76+
- For **Arc onboarding**:
77+
78+
1. Select a **Connectivity method** to determine whether the Connected Machine agent should connect to the internet via a public endpoint or by proxy server. If you select **Proxy server**, provide a **Proxy server URL** to which the EC2 instance can connect.
79+
1. Choose whether or not to enable periodic sync. By default, this is enabled so that the connector will scan your AWS account regularly. If you uncheck the box, your AWS account will only be scanned once.
80+
1. If **Enable periodic sync** is checked, confirm or change the **Recur every** selection to specify how often your AWS account will be scanned.
81+
1. Choose which regions to scan for EC2 instances in your AWS account. By default, all available regions are selected.
82+
83+
1. On the **Authentication template** page, download the CloudFormation template that you'll upload to AWS. This template is created based on the information you provided in **Basics** and the solutions you selected. You can [upload the template](#upload-cloudformation-template-to-aws) right away, or wait until you finish adding your public cloud.
84+
85+
1. On the **Tags** page, enter any tags you'd like to use.
86+
1. On the **Review and create** page, confirm your information and then select **Create**.
87+
88+
If you didn't upload your template during this process, follow the steps in the next section to do so.
89+
90+
## Upload CloudFormation template to AWS
91+
92+
After you've saved the CloudFormation template generated in the previous section, you need to upload it to your AWS public cloud. If you upload the template before you finish connecting your AWS cloud in the Azure portal, your AWS resources will be scanned immediately. If you complete the **Add public cloud** process in the Azure portal before uploading the template, it will take a bit longer to scan your AWS resources and make them available in Azure.
93+
94+
### Create stack
95+
96+
Follow these steps to create a stack and upload your template:
97+
98+
1. Open the AWS CloudFormation console and select **Create stack**.
99+
1. Select **Template is ready**, then select **Upload a template file**. Select **Choose file** and browse to select your template. Then select **Next**.
100+
1. In **Specify stack details**, enter a stack name. Leave the other options set to their default settings and select **Next**.
101+
1. In **Configure stack options**, leave the options set to their default settings and select **Next**.
102+
1. In **Review and create**, confirm that the information is correct, select the acknowledgment checkbox, and then select **Submit**.
103+
104+
### Create StackSet
105+
106+
If your AWS account is an organization account, you also need to create a StackSet and upload your template again. To do so:
107+
108+
1. Open the AWS CloudFormation console and select **StackSets**, then select **Create StackSet**.
109+
1. Select **Template is ready**, then select **Upload a template file**. Select **Choose file** and browse to select your template. Then select **Next**.
110+
1. In **Specify stack details**, enter `AzureArcMultiCloudStackset` as the StackSet name, then select **Next**.
111+
1. In **Configure stack options**, leave the options set to their default settings and select **Next**.
112+
1. In **Set deployment options**, enter the ID for the AWS account where the StackSet will be deployed, and select any AWS region to deploy the stack. Leave the other options set to their default settings and select **Next**.
113+
1. In **Review**, confirm that the information is correct, select the acknowledgment checkbox, and then select **Submit**.
114+
115+
## Confirm deployment
116+
117+
After you complete the **Add public cloud** option in Azure, and you upload your template to AWS, your connector and selected solutions will be created. On average, it takes about one hour for your AWS resources to become available in Azure. If you upload the template after creating the public cloud in Azure, it may take a bit more time before you see the AWS resources.
118+
119+
AWS resources are stored in a resource group using the naming convention `aws_yourAwsAccountId`. Scans will run regularly to update these resources, based on your **Enable periodic sync** selections.
120+
121+
## Next steps
122+
123+
- Query your inventory with [the multicloud connector **Inventory** solution](view-multicloud-inventory.md).
124+
- Learn how to [use the multicloud connector **Arc onboarding** solution](onboard-multicloud-vms-arc.md).
125+
126+

‎articles/azure-arc/multicloud-connector/index.yml

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
### YamlMime:Landing
2+
3+
title: Multicloud connector enabled by Azure Arc (preview) # < 60 chars
4+
summary: Connect non-Azure public cloud resources to Azure for centralized management and governance. # < 160 chars
5+
6+
metadata:
7+
title: Multicloud connector enabled by Azure Arc (preview)
8+
description: Connect non-Azure public cloud resources to Azure for centralized management and governance.
9+
ms.service: azure-arc
10+
ms.topic: landing-page
11+
ms.date: 06/11/2024
12+
13+
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
14+
15+
landingContent:
16+
# Cards and links should be based on top customer tasks or top subjects
17+
# Start card title with a verb
18+
# Card (optional)
19+
- title: About
20+
linkLists:
21+
- linkListType: overview
22+
links:
23+
- text: What is Multicloud connector enabled by Azure Arc?
24+
url: overview.md
25+
26+
- title: Get started
27+
linkLists:
28+
- linkListType: deploy
29+
links:
30+
- text: Connect a public cloud to Azure
31+
url: connect-to-aws.md
32+
33+
- title: Solutions
34+
linkLists:
35+
- linkListType: how-to-guide
36+
links:
37+
- text: View and manage multicloud inventory
38+
url: view-multicloud-inventory.md
39+
- linkListType: how-to-guide
40+
links:
41+
- text: Onboard VMs to Azure Arc
42+
url: onboard-multicloud-vms-arc.md

‎articles/azure-arc/multicloud-connector/media/add-aws-connector-solutions.png

71 KB
Loading

‎articles/azure-arc/multicloud-connector/onboard-multicloud-vms-arc.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
title: Onboard VMs to Azure Arc through the multicloud connector
3+
description: Learn how to enable the Arc onboarding solution with the multicloud connector enabled by Azure Arc.
4+
ms.topic: how-to
5+
ms.date: 06/11/2024
6+
---
7+
8+
# Onboard VMs to Azure Arc through the multicloud connector
9+
10+
The **Arc onboarding** solution of the multicloud connector auto-discovers VMs in a [connected public cloud](connect-to-aws.md), then installs the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) to onboard the VMs to Azure Arc. Currently, EC2 instances in AWS public cloud environments are supported.
11+
12+
This simplified experience lets you use Azure management services, such as Azure Monitor, providing a centralized way to manage Azure and AWS VMs together.
13+
14+
> [!IMPORTANT]
15+
> Multicloud connector enabled by Azure Arc is currently in PREVIEW.
16+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
17+
18+
You can enable the **Arc onboarding** solution when you [connect your public cloud to Azure](connect-to-aws.md).
19+
20+
## Prerequisites
21+
22+
In addition to the [general prerequisites](connect-to-aws.md#prerequisites) for connecting a public cloud, be sure to meet the requirements for the **Arc onboarding** solution. This includes requirements for each EC2 instance that will be onboarded to Azure Arc.
23+
24+
- You must have **AmazonEC2FullAccess** permissions in your public cloud.
25+
- EC2 instances must meet the [general prerequisites for installing the Connected Machine agent](../servers/prerequisites.md).
26+
- EC2 instances must have the SSM agent installed. Most EC2 instances have this preconfigured.
27+
- EC2 instances must have a tag with the key of `arc` (case-sensitive) and empty value. This tag can be assigned manually or via a policy.
28+
- The **ArcForServerSSMRole** IAM role [attached on each EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#attach-iam-role). This role attachment must be done after you upload your Cloud Formation Template in the Connector creation steps.
29+
30+
## AWS resource representation in Azure
31+
32+
After you connect your AWS cloud and enable the **Arc onboarding** solution, the Multicloud Connector creates a new resource group with the naming convention `aws_yourAwsAccountId`.
33+
34+
When EC2 instances are connected to Azure Arc, representations of these machines appear in this resource group. These resources are placed in Azure regions, using a [standard mapping scheme](resource-representation.md#region-mapping). You can filter for which Azure regions you would like to scan for. By default, all regions are scanned, but you can choose to exclude certain regions when you [configure the solution](connect-to-aws.md#add-your-public-cloud-in-the-azure-portal).
35+
36+
## Connectivity method
37+
38+
When creating the [**Arc onboarding** solution](connect-to-aws.md#add-your-public-cloud-in-the-azure-portal), you select whether the Connected Machine agent should connect to the internet via a public endpoint or by proxy server. If you select **Proxy server**, you must provide a **Proxy server URL** to which the EC2 instance can connect.
39+
40+
For more information, see [Connected machine agent network requirements](../servers/network-requirements.md?tabs=azure-cloud).
41+
42+
## Periodic sync options
43+
44+
The periodic sync time that you select when configuring the **Arc onboarding** solution determines how often your AWS account is scanned and synced to Azure. By enabling periodic sync, any time there is a newly discovered EC2 instance that meets the prerequisites, the Arc agent will be installed automatically.
45+
46+
If you prefer, you can turn periodic sync off when configuring this solution. If you do so, new EC2 instances won't be automatically onboarded to Azure Arc, as Azure won't be able to scan for new instances.
47+
48+
## Next steps
49+
50+
- Learn more about [managing connected servers through Azure Arc](../servers/overview.md).
51+
- Learn about the [Multicloud Connector **Inventory** solution](view-multicloud-inventory.md).

0 commit comments

Comments
 (0)