Using CodeArtifact as a dependency caching layer only

Question

# Background
Our team is currently using Codebuild/codepipeline for CI/CD. We are looking to speed-up CI/CD run-times by caching NPM downloads via CodeArtifact. We're not looking to make use of any CodeBuild caching solutions e.g. local cache as in the future we will be moving our CI/CD to different toolchain. However, we will still need a caching layer for our dependencies.

# Use Case
We want to use CodeArtifact as the caching layer for our NPM dependencies (another option could be JFrog). However, we won't be pushing any artifacts to CodeArtifact, just simply downloading publicly available dependencies from the NPM registry via CodeArtifact leveraging the caching capabilities of CodeArtifact.

# Question
Is our use-case of simply using CodeArtifact as a NPM caching layer appropriate and usable across different CI/CD solutions? For example, if it will work with CodeBuild today, will it work equally as well with BitBucket pipelines?

Answer

> Is our use-case of simply using CodeArtifact as a NPM caching layer appropriate and usable across different CI/CD solutions?

Yes, this will work. The only thing to remember is that you will need AWS credentials to be able to authenticate with CodeArtifact. Looks like there are some guidelines for doing this here: https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-aws-with-s3/.

Using CodeArtifact as a dependency caching layer only

Background

Use Case

Question

Relevant content