Custom Registries

Many teams don't install packages straight from the public registries. Instead they route them through a private registry that acts as a proxy or mirror of a public ecosystem, such as AWS CodeArtifact proxying npm or PyPI. Because those installs go to your private registry's domain rather than the public one, Device Protection needs to know about that domain to inspect the traffic.

Adding a custom registry tells Device Protection to treat that domain as a proxy for a supported public ecosystem. Packages served through it are checked for malware in exactly the same way as packages installed directly from the public registry.

How it works

When you register a custom registry, Device Protection recognizes its domain as a proxy for a public ecosystem. Package installs that flow through that domain are inspected on the device and checked against Aikido's malware signatures, just like installs from the public registry itself. Your existing installation policies apply to these installs too.

Add a custom registry

1. Go to Custom Registries in your Aikido account.
2. Click Add Custom Registry.
3. Select the registry Type (for example, AWS CodeArtifact).
4. Enter the registry Domain (for example, my-org.d.codeartifact.us-east-1.amazonaws.com).
5. Save.

The registry now appears in the list with its type and domain. Use the ⋮ menu on a row to edit or remove it.