Your firewall must allow access to the endpoints listed below. Without these rules configured, your systems cannot authenticate with the Minimus registry or pull images.
Connectivity requirements
Outbound traffic
You’ll need to open your firewall to allow outbound traffic to the Minimus gallery and registry. These are the requirements:
| DNS Names | Ports | Protocols |
|---|
| Minimus Console | https://images.minimus.io/ | 443 | TCP |
| Minimus registry | reg.mini.dev | 443 | TCP |
| Alternate registry address (for pulling image layers) | https://us-east1-docker.pkg.dev/artifacts-downloads/namespaces/prod-375107/repositories/minimus/ | 443 | TCP |
| Authentication service | auth.mini.dev | 443 | TCP |
| Google Artifact Registry | *.pkg.dev | 443 | TCP |
Inbound traffic
If you are using Minimus actions, you’ll need to open your firewall to allow inbound traffic from the following IP addresses:
- 34.139.95.89
- 34.74.18.163
- 34.73.139.186
The TCP port will depend on your webhook, for example: 443/TCP.
Pull token
Pulling images from the Minimus registry requires authentication with a valid pull token. Learn more
Supported regions
Minimus is hosted on GCP us-east1 (South Carolina). About Google Cloud regions.
Sync to self-hosted registry
If you want your teams to continue pulling images from your private, self-hosted registry, this can be done. Set up the sync service between Minimus and your private registry to give your team access to the latest updates without leaving your private registry and without changing internal processes. Learn more
IP Addresses Used
Minimus uses Google Cloud as our cloud provider, which may allocate IPs dynamically for the Google APIs and Services. Customers who need to track the IPs used by Google services can leverage the scripts provided by Google in the Google Cloud Platform Documentation. Last modified on April 13, 2026
