April 15, 2024
Voiced by Polly

Beginning at this time, 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 means that you can outline how packages are up to date by inner builders or from upstream repositories. Now you can enable or block inner builders to publish packages or enable or block upstream updates for a bunch of packages.

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

CodeArtifact helps on-demand importing of packages from public repositories akin 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 embody dozens of packages. Giant enterprise purposes may need a whole lot of dependencies. These packages assist builders pace up the event and testing course of by offering code that solves frequent programming challenges akin to community entry, cryptographic features, or knowledge format manipulation. These packages could be produced by different groups in your group or maintained by third events, akin to open supply initiatives.

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

Here’s a diagram displaying totally different potentialities to show a bundle to your builders.

CodeArtifact Multi Repository

When managing a repository, it’s essential to outline how packages could 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 widely known bundle beneath a barely totally different title. For instance, as an alternative 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 evening to kind npm set up cofee-script as an alternative of npm set up coffee-script to inject malicious code into your methods.

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

Till at this time, repository directors needed to handle these necessary safety settings bundle by bundle. With at this time’s replace, repository directors can outline these three safety parameters for a bunch of packages without delay. The packages are recognized by their kind, their namespace, and their title. This new functionality operates on the area degree, not the repository degree. It permits directors to implement a rule for a bundle group throughout all repositories of their area. They don’t have to take care of bundle origin controls configuration in each repository.

Let’s see intimately the way it works
Think about that I handle an inner bundle repository with CodeArtifact and that I need to distribute solely the variations of the AWS SDK for Python, often known as 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 inner builders.

CodeArtifact - Create a repo

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

CodeArtifact - Create a repo - package flowBy default, when a developer authenticates in opposition to 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.

CodeArtifact - pip installCodeArtifact - list of packages after a pip install

Now, think about I need 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 inner repository.

With the brand new functionality that we launched at this time, I can now apply this configuration for a bunch 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 parts: bundle format, an elective namespace, and title.

Listed below are a number of examples of patterns that you need to use for every of the allowed mixtures:

  • All bundle codecs: /*
  • A selected 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 title prefix: /npm/aws-amplify/ui~
  • Package deal format, namespace, and title: /maven/org.apache.logging.log4j/log4j-core$

I invite you to learn the documentation to study all the probabilities.

In my instance, there isn’t any idea of namespace for Python packages, and I would like the group to incorporate all packages with names beginning with boto3 coming from pypi. Due to this fact, I write /pypi//boto3~.

CodeArtifact - package group definition

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 need to authorize solely bundle updates from my inner staging listing.

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

CodeArtifact - package group security configuration

As soon as outlined, builders are unable to put in totally different bundle variations than those licensed within the python-aws repository. Once 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 isn’t accessible within the upstream staging repo, and there may be block rule that forestalls fetching packages or bundle updates from exterior upstream repositories.

Code ARtifact - installation is denied when using a package version not already present in the repository

Equally, let’s think about your administrator desires to guard your group from dependency substitution assaults. All of your inner Python bundle names begin along with your firm title (mycompany). The administrator desires to dam builders for unintentionally 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 inner upstream=block. With this configuration, inner 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, akin 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 offered, at no extra price. It lets you higher management how packages and bundle updates land in your inner repositories. It helps to forestall numerous provide chain assaults, akin to typosquatting or dependency confusion. It’s one extra configuration which you could add at this time into your infrastructure-as-code (IaC) instruments to create and handle your CodeArtifact repositories.

Go and configure your first bundle group at this time.

— seb