|
1 | 1 | ---
|
2 |
| -title: Migrate AWS Lambda workloads to Azure Functions |
| 2 | +title: Migrate AWS Lambda Workloads to Azure Functions |
3 | 3 | description: Learn how to migrate workloads from AWS Lambda to Azure Functions. Compare functionality and optimize workloads on Azure.
|
4 | 4 | author: MadhuraBharadwaj-MSFT
|
5 | 5 | ms.author: mabhar
|
@@ -48,22 +48,22 @@ To have a comprehensive strategy, you must combine the recommendations presented
|
48 | 48 |
|
49 | 49 | The first step is to conduct a detailed discovery process to evaluate your existing AWS Lambda workload. The goal is to understand which AWS features and services your workload relies on. Compile a comprehensive inventory of your AWS Lambda functions by using AWS tooling like service-specific SDKs, APIs, and CloudTrail to assess the workload on AWS. You should understand the following key aspects of your AWS Lambda inventory:
|
50 | 50 |
|
51 |
| -- Use cases. |
52 |
| -- Configurations. |
53 |
| -- Security and networking setups. |
54 |
| -- Tooling, monitoring, logging, and observability mechanisms. |
55 |
| -- Dependencies. |
56 |
| -- Reliability objectives and current reliability status. |
57 |
| -- Cost of ownership. |
58 |
| -- Performance targets and current performance. |
| 51 | +- Use cases |
| 52 | +- Configurations |
| 53 | +- Security and networking setups |
| 54 | +- Tooling, monitoring, logging, and observability mechanisms |
| 55 | +- Dependencies |
| 56 | +- Reliability objectives and current reliability status |
| 57 | +- Cost of ownership |
| 58 | +- Performance targets and current performance |
59 | 59 |
|
60 | 60 | ## Perform premigration planning
|
61 | 61 |
|
62 | 62 | Before you start migrating your workload, you must map AWS Lambda features to Azure Functions to ensure compatibility and develop a migration plan. Then you can select key workloads for a proof of concept.
|
63 | 63 |
|
64 | 64 | You also need to [map the AWS services](/azure/architecture/aws-professional) that Lambda depends on to the equivalent dependencies in Azure. For example, Azure Functions has a dependency on Azure Blob Storage in the same way that Lambda requires Amazon S3.
|
65 | 65 |
|
66 |
| -## Map AWS Lambda features to Azure Funtions |
| 66 | +## Map AWS Lambda features to Azure Functions |
67 | 67 |
|
68 | 68 | The following tables compare AWS Lambda concepts, resources, and properties with their corresponding equivalents on Azure Functions.
|
69 | 69 |
|
@@ -622,7 +622,7 @@ Deploy workloads by using the [VS Code](/azure/azure-functions/functions-develop
|
622 | 622 |
|
623 | 623 | - Continuous integration and continuous deployment (CI/CD) pipelines: Set up a CI/CD pipeline by using services like GitHub Actions, Azure DevOps, or another CI/CD tool.
|
624 | 624 |
|
625 |
| - For more information, see [Continuous delivery by using GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) or [Continuous delivery with Azure Pipelines](/azure/azure-functions/functions-how-to-azure-devops). |
| 625 | + For more information, see [Continuous delivery by using GitHub Actions](/azure/azure-functions/functions-how-to-github-actions) or [Continuous delivery with Azure Pipelines](/azure/azure-functions/functions-how-to-azure-devops). |
626 | 626 |
|
627 | 627 | ## Explore sample migration scenarios
|
628 | 628 |
|
|
0 commit comments