From 5dc69d27a25aa09a2b8d67ffaa5fc34371a9e66c Mon Sep 17 00:00:00 2001 From: Kelvin Tay <50355555+mt-kelvintaywl@users.noreply.github.com> Date: Fri, 25 Jun 2021 09:05:50 +0900 Subject: [PATCH] Update 2019-06-13-introducing-openfaas-for-lambda.md I just noticed a tiny typo in the naming of AWS ECR service; hope this was the correct intention. Signed-off-by: Kelvin --- _posts/2019-06-13-introducing-openfaas-for-lambda.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2019-06-13-introducing-openfaas-for-lambda.md b/_posts/2019-06-13-introducing-openfaas-for-lambda.md index 384b1ff0..90004d14 100644 --- a/_posts/2019-06-13-introducing-openfaas-for-lambda.md +++ b/_posts/2019-06-13-introducing-openfaas-for-lambda.md @@ -87,7 +87,7 @@ as a Pod along with the existing OpenFaaS core serviecs. I then used the [AWS SD ### Deploy a function -OpenFaaS functions are built into immutable Docker or OCI-format images, which are then stored in a registry such as the Amazon Container Registry (ACR). The first challenge I had was how to transform layers in my Docker image into an AWS Lambda package. +OpenFaaS functions are built into immutable Docker or OCI-format images, which are then stored in a registry such as the Amazon Elastic Container Registry (ECR). The first challenge I had was how to transform layers in my Docker image into an AWS Lambda package. This is how I decided to approach the problem. There is also potential to use Lambda layers in the future, but for now the provider creates a single layer or archive per function.