Beginning at present, directors of bundle repositories can handle the configuration of a number of packages in a single single place with the brand new AWS CodeArtifact bundle group configuration functionality. A bundle group permits you to outline how packages are up to date by inside builders or from upstream repositories. Now you can enable or block inside builders to publish packages or enable or block upstream updates for a gaggle of packages.

CodeArtifact is a completely managed bundle repository service that makes it simple for organizations to securely retailer and share software program packages used for utility growth. You should use CodeArtifact with widespread construct instruments and bundle managers comparable to NuGet, Maven, Gradle, npm, yarn, pip, twine, and the Swift Package deal Supervisor.

CodeArtifact helps on-demand importing of packages from public repositories comparable to npmjs.com, maven.org, and pypi.org. This enables your group’s builders to fetch all their packages from one single supply of reality: your CodeArtifact repository.

Easy purposes routinely embrace dozens of packages. Massive enterprise purposes may need lots of of dependencies. These packages assist builders pace up the event and testing course of by offering code that solves frequent programming challenges comparable to community entry, cryptographic capabilities, or knowledge format manipulation. These packages is likely to be produced by different groups in your group or maintained by third events, comparable to open supply initiatives.

To reduce the dangers of provide chain assaults, some organizations manually vet the packages which are obtainable in inside repositories and the builders who’re approved to replace these packages. There are 3 ways to replace a bundle in a repository. Chosen builders in your group may push bundle updates. That is sometimes the case to your group’s inside packages. Packages may also be imported from upstream repositories. An upstream repository is likely to be one other CodeArtifact repository, comparable to a company-wide supply of authorised packages or exterior public repositories providing widespread open supply packages.

Here’s a diagram displaying totally different prospects to reveal a bundle to your builders.

When managing a repository, it’s essential to outline how packages might be downloaded and up to date. Permitting bundle set up or updates from exterior upstream repositories exposes your group to typosquatting or dependency confusion assaults, for instance. Think about a nasty actor publishing a malicious model of a well known bundle underneath a barely totally different identify. For instance, as a substitute of coffee-script, the malicious bundle is cofee-script, with just one “f.” When your repository is configured to permit retrieval from upstream exterior repositories, all it takes is a distracted developer working late at night time to sort npm set up cofee-script as a substitute of npm set up coffee-script to inject malicious code into your methods.

CodeArtifact defines three permissions for the three attainable methods of updating a bundle. Directors can enable or block set up and updates coming from inside publish instructions, from an inside upstream repository, or from an exterior upstream repository.

Till at present, repository directors needed to handle these vital safety settings bundle by bundle. With at present’s replace, repository directors can outline these three safety parameters for a gaggle of packages without delay. The packages are recognized by their sort, their namespace, and their identify. This new functionality operates on the area stage, not the repository stage. It permits directors to implement a rule for a bundle group throughout all repositories of their area. They don’t have to keep up bundle origin controls configuration in each repository.

Let’s see intimately the way it works
Think about that I handle an inside bundle repository with CodeArtifact and that I wish to distribute solely the variations of the AWS SDK for Python, also called boto3, which were vetted by my group.

I navigate to the CodeArtifact web page within the AWS Administration Console, and I create a python-aws repository that may serve vetted packages to inside builders.

This creates a staging repository along with the repository I created. The exterior packages from pypi will first be staged within the pypi-store inside repository, the place I’ll confirm them earlier than serving them to the python-aws repository. Right here is the place my builders will hook up with obtain them.

By default, when a developer authenticates towards CodeArtifact and kinds pip set up boto3, CodeArtifact downloads the packages from the general public pypi repository, phases them on pypi-store, and copies them on python-aws.

Now, think about I wish to block CodeArtifact from fetching bundle updates from the upstream exterior pypi repository. I would like python-aws to solely serve packages that I authorised from my pypi-store inside repository.

With the brand new functionality that we launched at present, I can now apply this configuration for a gaggle of packages. I navigate to my area and choose the Package deal Teams tab. Then, I choose the Create Package deal Group button.

I enter the Package deal group definition. This expression defines what packages are included on this group. Packages are recognized utilizing a mixture of three elements: bundle format, an elective namespace, and identify.

Listed here are just a few examples of patterns that you need to use for every of the allowed combos:

• All bundle codecs: /*
• A particular bundle format: /npm/*
• Package deal format and namespace prefix: /maven/com.amazon~
• Package deal format and namespace: /npm/aws-amplify/*
• Package deal format, namespace, and identify prefix: /npm/aws-amplify/ui~
• Package deal format, namespace, and identify: /maven/org.apache.logging.log4j/log4j-core$

I invite you to learn the documentation to be taught all the chances.

In my instance, there is no such thing as a idea of namespace for Python packages, and I would like the group to incorporate all packages with names beginning with boto3 coming from pypi. Subsequently, I write /pypi//boto3~.

Then, I outline the safety parameters for my bundle group. On this instance, I don’t need my group’s builders to publish updates. I additionally don’t need CodeArtifact to fetch new variations from the exterior upstream repositories. I wish to authorize solely bundle updates from my inside staging listing.

I uncheck all Inherit from mum or dad group containers. I choose Block for Publish and Exterior upstream. I go away Enable on Inside upstream. Then, I choose Create Package deal Group.

As soon as outlined, builders are unable to put in totally different bundle variations than those approved within the python-aws repository. After I, as a developer, attempt to set up one other model of the boto3 bundle, I obtain an error message. That is anticipated as a result of the newer model of the boto3 bundle will not be obtainable within the upstream staging repo, and there’s block rule that forestalls fetching packages or bundle updates from exterior upstream repositories.

Equally, let’s think about your administrator desires to guard your group from dependency substitution assaults. All of your inside Python bundle names begin along with your firm identify (mycompany). The administrator desires to dam builders for by accident downloading from pypi.org packages that begin with mycompany.

Administrator creates a rule with the sample /pypi//mycompany~ with publish=enable, exterior upstream=block, and inside upstream=block. With this configuration, inside builders or your CI/CD pipeline can publish these packages, however CodeArtifact is not going to import any packages from pypi.org that begin with mycompany, comparable to mycompany.foo or mycompany.bar. This prevents dependency substitution assaults for these packages.

Package deal teams can be found in all AWS Areas the place CodeArtifact is obtainable, at no further price. It lets you higher management how packages and bundle updates land in your inside repositories. It helps to stop numerous provide chain assaults, comparable to typosquatting or dependency confusion. It’s one further configuration that you may add at present into your infrastructure-as-code (IaC) instruments to create and handle your CodeArtifact repositories.

Go and configure your first bundle group at present.

— seb