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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,7 @@ make public ARCH=arm64 VERSION=v1.0.0 AWS_REGION=eu-west-1 AWS_LAYER_VERSION=1
122
122
There are a number of ways to add the published layer to your Lambda Function:
123
123
124
124
1.[Using the AWS CLI](#using-the-aws-cli).
125
-
2.[Using a Lambda container image build stage](#using-a-lambda-container-image-build-stage).
125
+
2.[Using An AWS Lambda Docker Build](#using-an-aws-lambda-docker-build).
126
126
3.[Using Terraform](#using-terraform).
127
127
128
128
You will need to ascertain the layer ARN of the Lambda Layer containing the Firetail Lambda Extension that you wish to use. If you are not publishing your own Firetail Extension Lambda Layer, you may use the Lambda Layer published publicly by Firetail.
@@ -153,7 +153,7 @@ make add AWS_REGION=eu-west-1 LAYER_ARN=your-layer-arn FUNCTION_NAME=your-functi
153
153
154
154
155
155
156
-
#### Adding the Firetail Extension to a AWS Lambda Docker build
156
+
#### Using An AWS Lambda Docker Build
157
157
158
158
If your lambda is using a container image, you can add the layer to the image from within your Dockerfile. Relevant documentation can be found in [this AWS Compute Blog post](https://aws.amazon.com/blogs/compute/working-with-lambda-layers-and-extensions-in-container-images/).
0 commit comments