Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

License

NotificationsYou must be signed in to change notification settings

aws/aws-lambda-base-images

 
 

Repository files navigation

AWS provided base images for Lambda contain all the required components to run your functions packaged as container images on AWS Lambda. These images are published to theLambda public ECR repository andDockerHub. To learn more about how to use these images, check out the AWS documentation on how toCreate an image from an AWS base image for Lambda.

Each image contains Amazon Linux system libraries, the language runtime for a given programming language, dependencies, certificates, AWS SDK (Node.js, Python, and Ruby only) and the Lambda Runtime Interface Client (RIC).The RIC integrates with theLambda Runtime API to receive function invoke requests from the Lambda service. It then calls your function handler code, and returns the response to the Lambda service.These images are very similar to the AWS Lambda managed runtimes, although we may choose to optimize the container images by changing the components or included dependencies.

Maintenance policy

Consistent with the AWS Lambdashared responsibility model, Lambda provides regular updates to managed runtimes and container base images with security patches and other updates. As with any security patching, there is typically a short interval between a CVE being published and the corresponding security patch being applied. It is therefore normal for security scans of Lambda base images to report new CVEs from time to time. These CVEs are typically patched in our next update cycle.

You can file issues in this repository to flag issues or send feedback to the Lambda Runtimes team. However, please do not create a public GitHub issue to request information on CVE patching status. Any such issues will be closed. If you require information relating to the patching status of specific CVEs in Lambda runtime images, please contactAWS Support.

What we're doing here

As soon as new AWS Lambda base images are available, an automated process snapshots the layers and configuration used to create these images and publishes them to this repository. A separate branch is used for each image.

To avoid ballooning the respository size, we force-push the branches that contain the tarballs. As a result, content may disappear without warning. The older versions of our images remain present on DockerHub and Amazon ECR.

Usage

Requirements

To re-create the AWS Lambda base images, make sure you have the following pre-requisites set up:

Building an image

First, clone this repository:

git clone https://github.com/aws/aws-lambda-base-images

Then, checkout the branch relevant to the Lambda base image you want to build.

eg. to build thenodejs18.x image, start by checking out thenodejs18.x branch:

git checkout nodejs18.x

Finally you can build your image as such:

docker build -t nodejs18.x:local -f Dockerfile.nodejs18.x .

This will use the Dockerfile atDockerfile.nodejs18.x and tag the newly-built image asnodejs18.x:local.

Licence

This project is licensed under the Apache-2.0 License.

About

No description, website, or topics provided.

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

[8]ページ先頭

©2009-2025 Movatter.jp