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/migration/migrate-networking-from-aws.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,14 +30,13 @@ Use the following migration guides as examples to help structure your migration
30
30
31
31
| Scenario | Key services | Description |
32
32
|--|--|--|
33
-
|[Connect AWS and Azure using a BGP-enabled VPN gateway](/azure/architecture/aws-professional/networking?branch=main)| AWS virtual private gateway to Azure VPN gateway | Demonstrates how to setup a BGP-enabled connection between Azure and Amazon Web Services (AWS). |
33
+
|[Connect AWS and Azure using a BGP-enabled VPN gateway](/azure/vpn-gateway/vpn-gateway-howto-aws-bgp)| AWS virtual private gateway to Azure VPN gateway | Demonstrates how to setup a BGP-enabled connection between Azure and Amazon Web Services (AWS). |
34
34
35
35
## Related workload components
36
36
37
37
Networking makes up only part of your workload. Explore other components that you might migrate:
38
38
39
-
-[Compute](./migrate-compute-from-aws.md)
40
-
-[Databases and data](./migrate-databases-from-aws.md)
41
-
-[Storage](./migrate-storage-from-aws.md)
42
-
43
-
Use the table of contents to explore other articles that relate to your workload's architecture.
title: Migrate security services from Amazon Web Services (AWS)
3
+
description: Learn about replatforming security services from AWS to Microsoft Cloud to support the security requirements of the workload. Discover key similarities and differences between AWS and Microsoft.
4
+
ms.author: joflore
5
+
author: MicrosoftGuyJFlo
6
+
ms.date: 05/01/2025
7
+
ms.topic: conceptual
8
+
ms.collection:
9
+
- migration
10
+
- aws-to-azure
11
+
---
12
+
# Migrate security services from Amazon Web Services (AWS)
13
+
14
+
This article describes scenarios that you can use to migrate Amazon Web Services (AWS) security services to Microsoft Azure. These cloud services provide foundational security elements necessary for monitoring other services and applications built in the cloud. The migration process involves transitioning services while focusing on maintaining or enhancing functionality.
15
+
16
+
These scenarios might cover tasks like migrating your security and information and event management (SIEM) solution to Azure.
17
+
18
+
## Migration scenarios
19
+
20
+
Use the following migration guides as examples to help structure your migration strategy.
21
+
22
+
| Scenario | Key services | Description |
23
+
|--|--|--|
24
+
|[Migrate your SIEM in AWS to Microsoft Sentinel](/azure/sentinel/migration)| SIEM data in AWS -> Microsoft Sentinel | Plan the different phases of your SIEM data migration from AWS. |
25
+
26
+
## Related workload components
27
+
28
+
Security services make up only part of your cloud workload. Explore other components you might migrate:
29
+
30
+
-[Compute](migrate-compute-from-aws.md)
31
+
-[Databases](migrate-databases-from-aws.md)
32
+
-[Storage](migrate-storage-from-aws.md)
33
+
-[Networking](migrate-networking-from-aws.md)
34
+
35
+
Migrating security scenarios require identity to be a central service. Compare [AWS identity services](/azure/architecture/aws-professional/security-identity) used in the workload to their closest Azure counterparts.
Copy file name to clipboardExpand all lines: articles/migration/migrate-storage-from-aws.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Storage services are foundational components of most enterprise workloads. The m
19
19
20
20
## Component comparison
21
21
22
-
Start the migration process by comparing the AWS storage service that's used in the workload with the closest Azure counterpart. The goal is to identify the most suitable Azure services for your workload. For more information, see [Comparing AWS and Azure storage services](/azure/architecture/.aws-professional/storage).
22
+
Start the migration process by comparing the AWS storage service that's used in the workload with the closest Azure counterpart. The goal is to identify the most suitable Azure services for your workload. For more information, see [Comparing AWS and Azure storage services](/azure/architecture/aws-professional/storage).
23
23
24
24
> [!NOTE]
25
25
> This comparison isn't an exact representation of the functionality that these services provide in your workload.
@@ -38,7 +38,7 @@ Use the following migration guides as examples to help structure your migration
38
38
39
39
Storage makes up only part of your workload. Explore other components that you might migrate:
40
40
41
-
-[Compute](./migrate-compute-from-aws.md)
42
-
-[Databases and data](./migrate-databases-from-aws.md)
43
-
44
-
Use the table of contents to explore other articles that relate to your workload's architecture.
0 commit comments