Skip to content

Commit f804d57

Browse files
committed
typos
1 parent 7853792 commit f804d57

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/azure-functions/migration/migrate-aws-lambda-to-azure-functions.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Migrate AWS Lambda workloads to Azure Functions
2+
title: Migrate AWS Lambda Workloads to Azure Functions
33
description: Learn how to migrate workloads from AWS Lambda to Azure Functions. Compare functionality and optimize workloads on Azure.
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
@@ -48,22 +48,22 @@ To have a comprehensive strategy, you must combine the recommendations presented
4848

4949
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:
5050

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
5959

6060
## Perform premigration planning
6161

6262
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.
6363

6464
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.
6565

66-
## Map AWS Lambda features to Azure Funtions
66+
## Map AWS Lambda features to Azure Functions
6767

6868
The following tables compare AWS Lambda concepts, resources, and properties with their corresponding equivalents on Azure Functions.
6969

@@ -622,7 +622,7 @@ Deploy workloads by using the [VS Code](/azure/azure-functions/functions-develop
622622

623623
- 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.
624624

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).
626626

627627
## Explore sample migration scenarios
628628

0 commit comments

Comments
 (0)