Fully Managed, Secured, and Optimized Docker Registry

1. Launch an Instance

From AWS Marketplace, click Continue to Subscribe, then Continue to Configuration, and launch the AMI.

2. Choose the Recommended Instance Type

Select t2.medium or higher for a smooth Docker Registry deployment. Container registry workloads benefit from adequate CPU/RAM - larger instance types improve image push/pull performance and concurrent operations.

3. Configure Security Group

Allow inbound traffic on the following ports:

• 22 (SSH) - For secure terminal access
• 80 (HTTP) - Required temporarily for SSL validation
• 443 (HTTPS) - Secure access to Docker Registry via domain

4. Connect to the Instance

Use SSH to connect: ssh -i <your-key.pem> ubuntu@<public-ip>

5. First-Boot Setup (Guided)

On first login, an interactive guided setup will automatically start:

• Detects public IP
• Prompts for domain name mapping to Docker Registry
• Validates DNS A-record propagation
• Asks for admin email for SSL certificate registration
• Generates a strong secure admin password (bcrypt-hashed)
• Stores credentials in /opt/app/.env and /opt/app/admin_password.txt
• Creates Apache reverse proxy configuration with dual authentication
• Requests & installs a free Let's Encrypt SSL certificate
• Deploys Docker Registry using Docker Compose
• Displays access URL & login credentials after completion

6. DNS Configuration Required

Before (or during) setup, add this DNS A-record:

registry.yourdomain.com <your-instance-public-IP>

Setup continues only when major resolvers confirm valid mapping.

7. Automatic SSL Setup

After DNS validation:

• Enables HTTPS access to Docker Registry
• Auto-installs a valid TLS certificate
• Redirects HTTP to HTTPS for security
• Configures security headers (HSTS, X-Frame-Options, etc.)

8. Verify Registry & Remove Port 5000

Test from your local machine: docker login https://registry.yourdomain.com  Username: admin Password: <generated-password>

If login succeeds, your registry is working via your domain.

IMPORTANT SECURITY STEP: Once confirmed working properly on domain, remove port 5000 from your security group: AWS Console > EC2 > Security Groups > Edit Inbound Rules > Delete port 5000 (if present) > Save

The registry runs on localhost:5000 and is accessed through Apache on port 443. Removing port 5000 ensures secure HTTPS-only access.

9. Access & Retrieve Credentials

Credentials saved in: sudo cat /opt/app/admin_password.txt sudo cat /opt/app/.env

Default user: Username: admin Password: <generated-password>

10. Push an Image

docker tag myapp:latest registry.yourdomain.com/myapp:latest docker push registry.yourdomain.com/myapp:latest

11. Pull an Image

docker pull registry.yourdomain.com/myapp:latest

12. Managing the Registry

View containers: sudo docker ps View logs: sudo docker logs registry Restart: cd /opt/app && sudo docker-compose restart Stop: cd /opt/app && sudo docker-compose down Start: cd /opt/app && sudo docker-compose up -d

Persistent volumes preserve images across restarts.

13. Authentication Details

This registry uses DUAL-LAYER authentication:

• Apache Basic Auth (first layer)
• Docker Registry htpasswd (second layer)

Both layers use the same admin credentials.

14. Data Persistence

Images stored in: /opt/app/data Authentication files: /opt/app/auth/.htpasswd Mounted as Docker volumes ensuring persistence.

Thank you for subscribing. Your instance is ready to go!

Need Support or Customization? Whether you're facing setup issues or need custom features, Perimattic's expert team is here to help:

Email us: aws-support@perimattic.com  WhatsApp: +91-92142 66896 Learn more: <www.perimattic.com >

We offer: Free setup assistance Custom development & integrations Infrastructure consulting Automation & AI solutions With 13+ years of experience serving global clients, we ensure your deployment runs smoothly and scales with your needs.

Let's build something great together!