|
1 | 1 | --- |
2 | | -title: AWS Lambda to Azure Functions Migration Discover Stage |
3 | | -description: Learn about the steps that you need to take during the discover stage of your AWS Lambda to Azure Functions migration. |
| 2 | +title: Discover workloads to migrate from AWS Lambda to Azure Functions |
| 3 | +description: Learn how to conduct a detailed discovery process to inventory current AWS Lambda workloads, including their configuration, dependencies, and usage patterns. |
4 | 4 | author: MadhuraBharadwaj-MSFT |
5 | 5 | ms.author: mabhar |
6 | 6 | ms.service: azure-functions |
7 | 7 | ms.topic: how-to |
8 | 8 | ms.date: 03/18/2025 |
9 | | -#customer intent: As a developer, I want to learn about the discover stage of migration so that I can migrate serverless applications from AWS Lambda to Azure Functions efficiently. |
| 9 | +#customer intent: As a developer, I want to evaluate existing AWS Lambda workloads so that I can migrate serverless applications to Azure Functions efficiently. |
10 | 10 | --- |
11 | 11 |
|
12 | | -# AWS Lambda to Azure Functions migration discover stage |
| 12 | +# Discover workloads to migrate from AWS Lambda to Azure Functions |
13 | 13 |
|
14 | | -In this stage, you will conduct a detailed discovery process to inventory the current workloads, including their configuration, dependencies, and usage patterns. |
| 14 | +In this stage, you conduct a detailed discovery process to evaluate existing AWS Lambda workloads, including their configuration, dependencies, and usage patterns. |
15 | 15 |
|
16 | | -## Discover Your Current Workload |
| 16 | +## Evaluate your current workload |
17 | 17 |
|
18 | | -Compile a comprehensive inventory of your AWS Lambda functions using familiar AWS tooling like service specific SDKs, APIs, CloudTrail etc. to assess the workloads on AWS. Your inventory should include the following key aspects: |
| 18 | +Compile a comprehensive inventory of your AWS Lambda functions by using familiar AWS tooling like service-specific SDKs, APIs, and CloudTrail to assess the workloads on AWS. You should understand the following key aspects of your inventory: |
19 | 19 |
|
20 | | -- Understanding the Use Cases: |
21 | | - - Identify the primary business or technical purposes each Lambda function serves. |
22 | | - - Categorize functions based on their use cases, such as event-driven workflows, data processing, real-time analytics, or API backends. |
| 20 | +- Use cases |
| 21 | + - Identify the primary business or technical purposes that each Lambda function serves. |
| 22 | + - Categorize functions based on their use cases, such as event-driven workflows, data processing, real-time analytics, or API back ends. |
23 | 23 |
|
24 | | - - Understanding the Configuration: |
25 | | - - Document configuration settings for each function, including memory allocation, timeout settings, and environment variables. |
26 | | - - Note versioning details, aliases, and any deployment-specific configurations, such as language runtime and architecture (e.g., x86 or ARM). |
| 24 | + - Configuration |
| 25 | + - Document configuration settings for each function, including memory allocation, time-out settings, and environment variables. |
| 26 | + - Note versioning details, aliases, and any deployment-specific configurations, such as language runtime and architectures like x86 or ARM. |
27 | 27 |
|
28 | | -- Understanding Security and Networking Setup: |
29 | | - - Assess IAM roles and policies associated with each function to ensure proper access control. |
30 | | - - Identify VPC configurations, including subnets, security groups, and NAT gateway dependencies, if applicable. |
| 28 | +- Security and networking setup |
| 29 | + - Assess the identity and access management roles and policies associated with each function to ensure proper access control. |
| 30 | + - Identify virtual private cloud configurations, including subnets, security groups, and NAT gateway dependencies, if applicable. |
31 | 31 |
|
32 | | -- Understanding the Tooling: |
33 | | - - List the CI/CD tools and deployment frameworks used, such as AWS SAM, Serverless Framework, or custom pipelines. |
34 | | - - Document build and packaging tools, including testing frameworks and staging workflows. |
| 32 | +- Tooling |
| 33 | + - List the continuous integration and continuous delivery tools and deployment frameworks that each function uses, such as AWS SAM, Serverless Framework, or custom pipelines. |
| 34 | + - Document build and packaging tools, including testing frameworks and staging workflows. |
35 | 35 |
|
36 | | -- Understanding Monitoring, Logging, and Observability: |
37 | | - - Evaluate the monitoring and logging mechanisms currently in place, such as AWS CloudWatch, X-Ray, or third-party tools. |
| 36 | +- Monitoring, logging, and observability mechanisms |
| 37 | + - Evaluate the current monitoring and logging mechanisms, such as Amazon CloudWatch, AWS X-Ray, or partner tools. |
38 | 38 | - Identify log retention policies and patterns for troubleshooting. |
39 | | - - Document metrics and alerts being tracked, such as error rates, invocation counts, or duration trends. |
| 39 | + - Document tracked metrics and alerts, such as error rates, invocation counts, and duration trends. |
40 | 40 |
|
41 | | -- Understanding dependencies |
42 | | - - Determine all AWS services (e.g., DynamoDB, S3, API Gateway) and third-party tools your Lambda functions rely on, documenting their configurations, interactions, and data flows. |
43 | | - - Map interdependencies between Lambda functions, such as shared resources or invocation chains, and evaluate potential bottlenecks or latency issues. |
44 | | - - Assess service limits, operational considerations, and monitoring tools (e.g., CloudWatch, X-Ray) to ensure a comprehensive understanding of dependency impact. |
| 41 | +- Dependencies |
| 42 | + - Determine which AWS services, like DynamoDB, S3, or API Gateway, and partner tools that your Lambda functions rely on. Document their configurations, interactions, and data flows. |
| 43 | + - Map interdependencies, such as shared resources or invocation chains, between Lambda functions and evaluate potential bottlenecks or latency problems. |
| 44 | + - Assess service limits, operational considerations, and monitoring tools like CloudWatch and X-Ray. Ensure that you understand how these dependencies affect the workload. |
45 | 45 |
|
46 | | -By the end of this stage, you will have a comprehensive inventory of your AWS Lambda functions, including their use cases, configurations, security and networking setups, tooling, monitoring, logging, observability, and dependencies. This detailed inventory will serve as the foundation for the next stage, where you will assess the readiness and suitability of these functions for migration to Azure Functions. |
| 46 | +By the end of this stage, you should have a comprehensive inventory of your AWS Lambda functions, including their use cases, configurations, security and networking setups, tooling, monitoring, logging, and observability mechanisms, and dependencies. This detailed inventory is the foundation for the next stage, where you assess the readiness and suitability of these functions for migration to Azure Functions. |
47 | 47 |
|
48 | 48 | ## Next step |
49 | 49 |
|
|
0 commit comments