Overview
Registry service active, loopback-only listener
The registry and nginx services reporting active under systemd, with the registry binary bound to loopback 127.0.0.1:5000 only and nginx serving the network on ports 80 and 443.
Registry service active, loopback-only listener
Authentication enforced, no anonymous access
Authenticated docker login, push and pull
Catalog and dedicated data-volume storage
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
Docker Registry is the reference open source container image registry, built on the CNCF Distribution project that Docker Hub and most private registries are built on. It is a stateless, highly scalable server-side application that stores and distributes OCI and Docker container images. This image delivers it fully installed and running under systemd, so a working private registry endpoint is serving over HTTPS within minutes of launch, with no manual setup required to start pushing and pulling images.
Unlike a bare deployment, this image is configured to be secure by default and is deliberately not an open push or pull target. The registry process itself binds to loopback only and is never exposed to the network; an nginx front end terminates TLS on port 443 and enforces HTTP Basic authentication on the registry API. There is no default password baked into the image: a unique admin credential is generated on this instance's first boot, stored as a bcrypt htpasswd entry and in a root-only credentials file, and never shipped inside the image. Anonymous requests to the registry API receive HTTP 401 and carry no images, so only the per-instance credential can push or pull. A self-signed TLS certificate covering the instance's public IP is regenerated on first boot, and the operating system ships fully patched with unattended security updates enabled.
Image blobs are written to a dedicated, independently resizable data volume mounted separately from the operating system disk, so pushed images survive and scale independently of the root volume, and the storage backend can later be switched to an object store such as Amazon S3 for larger deployments. Use this registry to host private application images for your CI/CD pipelines, to keep a controlled internal cache of base and release images, to run an air-gapped or on-network registry close to your workloads, or to mirror and distribute images across a private fleet. The current release available is version 3.1.1.
This is a repackaged open source software product with additional charges for cloudimg support services. The CNCF Distribution registry is distributed under the Apache License 2.0. cloudimg is not affiliated with or endorsed by Docker, Inc. or the Cloud Native Computing Foundation. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Highlights
- Reference private container image registry built on the CNCF Distribution project, preinstalled and serving OCI and Docker images over an authenticated HTTPS endpoint under systemd within minutes of launch
- Secure by default and never an open push target - the registry binds to loopback only behind an nginx TLS front end, a unique admin credential is generated on first boot and never baked into the image, and anonymous push and pull are rejected with HTTP 401
- Image blobs stored on a dedicated, independently resizable data volume separate from the OS disk, a fully patched OS with unattended security updates, and 24/7 cloudimg support, ready to switch to object storage for scale
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
- ...
Dimension | Description | Cost/hour |
|---|---|---|
m5.large Recommended | m5.large | $0.08 |
t3.micro | t3.micro instance type | $0.04 |
t2.micro | t2.micro instance type | $0.04 |
c6in.8xlarge | c6in.8xlarge instance type | $0.24 |
t2.2xlarge | t2.2xlarge instance type | $0.24 |
g7.48xlarge | g7.48xlarge instance type | $0.24 |
m6a.8xlarge | m6a.8xlarge instance type | $0.24 |
m6in.24xlarge | m6in.24xlarge instance type | $0.24 |
m8idb.4xlarge | m8idb.4xlarge instance type | $0.24 |
c8ib.24xlarge | c8ib.24xlarge instance type | $0.24 |
Vendor refund policy
Refunds available on request.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release of Docker Registry powered by the CNCF Distribution project as a ready-to-use private container image registry, with a per-instance admin credential generated on first boot, TLS enabled, no anonymous access, and image blobs on a dedicated resizable data volume.
Additional details
Usage instructions
Connect via SSH on port 22 as the default login user for your operating system variant (for the Ubuntu 24.04 variant the user is ubuntu). Retrieve the generated registry credentials with: sudo cat /root/registry-credentials.txt - this holds the per-instance admin username and password generated on first boot, the HTTPS endpoint, and the path to the self-signed TLS certificate. The registry API is served over HTTPS on port 443 (nginx TLS + HTTP Basic auth) and proxies to the registry binary on loopback 127.0.0.1:5000; the instance security group opens ports 22 (SSH), 80 (redirect + health probe) and 443 (registry). There is no anonymous access - every push and pull requires the credential. From a client, first trust the self-signed certificate (copy /etc/nginx/tls/registry.crt to /etc/docker/certs.d/<instance-ip>/ca.crt), then: docker login <instance-public-ip> -u admin, docker tag alpine:latest <instance-public-ip>/alpine:latest, and docker push <instance-public-ip>/alpine:latest. Verify the API and list repositories with: curl -u admin:<pass> --cacert registry.crt https://<instance-public-ip>/v2/_catalog. An unauthenticated health probe is available at https://<instance-public-ip>/healthz. Image blobs are stored on the dedicated data volume at /var/lib/registry; for production, front the registry with your own domain and a CA-signed certificate and switch the storage backend to Amazon S3 in /etc/docker/registry/config.yml. The services run under systemd: systemctl status registry nginx.
Resources
Vendor resources
Support
Vendor support
cloudimg provides 24/7 technical support for this product by email and live chat. Our engineers help with deployment, configuration, updates, performance tuning and troubleshooting; critical issues receive a one hour average response. Contact support@cloudimg.co.uk .
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.