Lambda source code updating issue during its container image building via cdk

I am making a lambda function through DockerImageFunction with DockerImageCode.fromImageAsset() from aws-cdk-lib/aws-lambda. The Dockerfile contains a collection of codec tools, and the lambda handler function code. Moreover, those codec tools takes 5 min to build, and hardly ever needs to be updated. The problem is that there are lot of lambda functions use the same codec tools, and the same codec tools get rebuilded everytime my lambda handler function code has been commited. Is there a way to craete those codec tools first, and for those lambda functions which need the tools during image building, just import it? Thanks!

Themen

Serverlos Kalkulation Entwicklertools DevOps

Tags

AWS Lambda Entwicklertools DevOps

Sprache

English

strange-folk-df787

gefragt vor 2 Jahren845 Aufrufe

1 Antwort

Neueste
Die meisten Stimmen
Die meisten Kommentare

Sind diese Antworten hilfreich? Stimmen Sie der richtigen Antwort zu, damit die Community von Ihrem Wissen profitieren kann.

Akzeptierte Antwort

You could create a base image that contains all your shared dependencies (i.e. codec tools) and then reference this base image in the Dockerfile on your lambda functions. The base image should be built as a pre-requisite step and pushed to an ECR repository.

ogaumond

beantwortet vor 2 Jahren

EXPERTE

Giovanni Lauria

überprüft vor einem Monat

strange-folk-df787
vor 2 Jahren
Would you mind pointing out how exactly to create a base image and then reference it in the lambda? I was making the base image by the DockerImageAsset from aws-cdk-lib/aws-ecr-assets, and then using asset.imageUri to reference it when creating a lambda, like the following:

new DockerImageFunction(this, "lambda-handler", {code: DockerImageCode.fromImageAsset(path.join("/dockerfile/path/"), {buildArgs: { CODEC_SOURCE: asset.imageUri} })})

But I got an Error said:Cannot use tokens in keys or values of "buildArgs" since they are needed before deployment.

Thanks!
ogaumond
vor 2 Jahren
The error you get from CDK is because the imageUri is only known at execution time, but the buildArgs are needed at synth time. You may need to separate the build of the base image in a separate process to have the base image pushed to a known ECR registry that can then be referenced from the lambda stack. The following construct could be used to publish the base image to ECR: https://github.com/cdklabs/cdk-ecr-deployment

Relevanter Inhalt

Wie verwende ich Container-Images mit Lambda?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie behebe ich die Fehler „Invalid permissions on Lambda function“ (Ungültige Berechtigungen für die Lambda-Funktion) von API Gateway-REST-APIs?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie mache ich meine Lambda-Funktion idempotent?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie kann ich den Fehler “Lambda does not have permission to access the ECR image...” (Lambda hat keine Berechtigung, auf das ECR-Image zuzugreifen...) für eine Lambda-Funktion mit einem Container-Image beheben?
AWS OFFICIALAktualisiert vor einem Jahr