Question

A development team builds Node.js microservices and installs npm packages during their AWS CodeBuild stage. They want a private repository to store their own internal packages while also being able to pull public packages from the npm public registry, so that all dependencies are resolved through a single endpoint that can be cached and controlled. Which AWS service and configuration meets this requirement with the least operational overhead?

Accepted Answer

Create an AWS CodeArtifact repository with an upstream connection to the public npm registry, and configure npm in CodeBuild to authenticate against the CodeArtifact repository endpoint.

Answer

Store all internal packages as objects in an Amazon S3 bucket and use a lifecycle policy to periodically sync public npm packages into the bucket.

Answer

Push internal packages as container images to Amazon ECR and pull public npm packages directly from the npm registry during each build.

Answer

Run a self-managed private npm registry on an Amazon EC2 instance and manually mirror public packages using a scheduled cron job.