Skip to content

Commit 87b869a

Browse files
committed
Update migrate compute intro article
1 parent fa17913 commit 87b869a

File tree

2 files changed

+27
-17
lines changed

2 files changed

+27
-17
lines changed

articles/migrate/tutorial-migrate-aws-virtual-machines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ ms.custom:
1313
- aws-to-azure
1414
---
1515

16-
# Discover, assess, and migrate Amazon Web Services (AWS) VMs to Azure
16+
# Discover, assess, and migrate Amazon Web Services (AWS) EC2 instances to Azure
1717

18-
This tutorial shows you how to discover, assess, and migrate Amazon Web Services (AWS) virtual machines (VMs) to Azure VMs by using Azure Migrate: Server Assessment and the Migration and modernization tool.
18+
This tutorial shows you how to discover, assess, and migrate Amazon Web Services (AWS) EC2 instances to Azure VMs by using Azure Migrate: Server Assessment and the Migration and modernization tool.
1919

2020
> [!NOTE]
2121
> You migrate AWS VMs to Azure by treating them as physical servers.

articles/migration/migrate-compute-from-aws.md

Lines changed: 25 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -3,35 +3,45 @@ title: Migrate Compute from Amazon Web Services (AWS)
33
description: Concepts, how-tos, best practices for moving compute from AWS to Azure.
44
author: robbyatmicrosoft
55
ms.author: robbymillsap
6-
ms.date: 01/28/2025
6+
ms.date: 03/25/2025
77
ms.topic: conceptual
88
---
99

1010
# Migrate compute from Amazon Web Services (AWS)
1111

12-
Many workloads contain compute components, such as virtual machines, container hosts, or PaaS services. These compute components host your custom code or commercial off the shelf (COTS) solutions. Microsoft Azure has guidance to help you migrate your application platform.
12+
The articles listed on this page outline scenarios for migrating Amazon Web Services (AWS) compute services to Azure. These cloud resources offer the processing power, memory, and storage necessary for running computational tasks. The migration process involves transitioning these services from AWS to Azure, with a focus on maintaining feature parity.
1313

14-
## Azure service awareness
14+
The scenarios cover common compute types, such as virtual machines (VMs), web applications, and serverless services. For example, a typical migration scenario might involve moving an AWS Lambda to Azure Functions.
1515

16-
If you haven't yet selected your application platform in Azure, review the [Azure for AWS professionals guide](/azure/architecture/aws-professional/), which has a service mapping available for compute. This is a list that maps similar services between the two cloud providers.
16+
## Component comparison
1717

18-
See, the [Azure compute services map](/azure/architecture/aws-professional/compute).
18+
Start the process by comparing AWS compute services used in the workload to their closest Azure counterparts. This helps identify the most suitable Azure services for your migration needs.
1919

20-
## Scenarios and component guides
20+
* [Compare compute services on Azure and AWS](/azure/architecture/aws-professional/compute)
2121

22-
Microsoft publishes guidance for select services to help architects, developers, and database administrators plan their migration efforts. Use these guides, combined with guidance available for your other components, to assess, plan, and perform your migration.
22+
> [!NOTE]
23+
> This comparison should not be considered an exact representation of the functionality provided by these services in your workload.
2324
24-
### TODO: Organize and present key migration content available for this technology area
25+
## Migration scenarios
26+
27+
Refer to the following scenarios as examples for framing your migration process:
28+
29+
| Scenario | Key services | Description |
30+
|----------|--------------|-------------|
31+
| [Migrate AWS event-driven workloads to Azure](/azure/aks/eks-edw-overview) | Amazon Elastic Kubernetes Service (AKS) to Azure Kubernetes Service (AKS) | This scenario involves migrating an EKS event-driven workload with KEDA nad Karpenter to AKS. |
32+
| [Migrate EKS web application workloads to AKS](/azure/aks/eks-web-overview) | Amazon Elastic Kubernetes Service (AKS) to Azure Kubernetes Service (AKS) | This scenario involves migrating an EKS web application to AKS. |
33+
| [Migrate Amazon EC2 instances to Azure](/azure/migrate/tutorial-migrate-aws-virtual-machines) | Amazon EC2 instances -> Azure VMs | This scenario involves migrating AWS EC2 instances to Azure VMs. |
34+
35+
The following list provides additional articles for migrating compute services. These scenarios are platform-agnostic but provide generic guidance for landing the service on Azure.
36+
37+
* [Migrate machines as physical servers to Azure](/azure/migrate/tutorial-migrate-physical-virtual-machines)
38+
* [Assess Hyper-V VMs for migration to Azure](/azure/migrate/tutorial-assess-hyper-v)
2539

2640
## Related workload components
2741

28-
Your workload contains other components as well that will need to migrate with your compute. Microsoft has similar guidance for:
42+
Compute services make up only part of your workload. Explore other components that are part of the migration process:
2943

30-
- [Databases, Data, and AI](./migrate-databases-from-aws.md)
3144
- [Storage](./migrate-storage-from-aws.md)
32-
- Identity and access management (IAM)
33-
- Networking
34-
- Messaging and integration
35-
- Security
45+
- [Databases](./migrate-databases-from-aws.md)
3646

37-
Use the table of contents to explore other topics related to your workload's architecture.
47+
Use the table of contents to explore other articles related to your workload's architecture.

0 commit comments

Comments
 (0)