A Docker image with relevant Node versions for AWS Lambda and AWS CLI
1.6K
Lambda-compatible NodeJS images with AWS CLI installed.
Whenever a new NodeJS version is released, an instance of commit-on-release creates an empty commit in the corresponding branch (v16 and v18, v20) so that a new image is published to Docker Hub by a Github Action workflow.
Instead of using e.g. node:20 and installing awscli, jq, and zip every time the pipeline runs, just switch out the name of the image to sleavely/node-awscli:20.x or another appropriate version tag.
In bitbucket-pipelines.yml:
image: sleavely/node-awscli:20.x
pipelines:
default:
- step:
name: Deploy to test environment
script:
- npm ci
- npm run build-app-test
- aws s3 sync ./build s3://$(WEBHOSTING_BUCKET_NAME)/
In .circleci/config.yml:
version: 2
jobs:
deploy:
docker:
- image: sleavely/node-awscli:20.x
steps:
- checkout
- run: npm ci
- run: npm run build-app-test
- run: aws s3 sync ./build s3://$(WEBHOSTING_BUCKET_NAME)/
In .github/worksflows/deploy.yml:
name: Build and deploy
on:
push:
branches:
- main
jobs:
deploy:
runs-on: ubuntu-latest
container:
image: sleavely/node-awscli:20.x
steps:
- uses: actions/checkout@v3
- run: npm ci
- run: npm run build-app-test
- run: aws s3 sync ./build s3://$(WEBHOSTING_BUCKET_NAME)/
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
WEBHOSTING_BUCKET_NAME: my-awesome-bucket
Content type
Image
Digest
sha256:7257105ad…
Size
549.5 MB
Last updated
over 2 years ago
docker pull ljay/node-awscli