Perimattic Managed Reverse Proxy Manager on AWS

This AMI runs a web-based reverse proxy manager on Ubuntu 24.04 LTS: create proxy hosts that forward a domain name to an internal application, redirections, streams and access lists from a web interface, without editing proxy configuration files. Release 2.16.0 is pinned and baked into the AMI, so first start does not depend on a registry. Data and certificates are kept on the instance (SQLite).

How this instance is laid out (please read)

Ports 80 and 443 belong to the Apache that publishes the management interface over HTTPS with its own Let's Encrypt certificate. The sites you create in the manager are served on this instance's port 8080 (HTTP) and port 8443 (HTTPS), so open those two ports in the security group as well and point your DNS or a load balancer at them. Because port 80 is not the manager's, Let's Encrypt HTTP validation inside the manager does not work: use DNS validation in the manager (with your own DNS provider credentials) or upload your own certificates. Unknown host names on 8080 get a plain 404 and unknown names on 8443 get no TLS handshake. If you need the managed sites on ports 80 and 443 themselves, this layout is not the right fit.

What Perimattic adds

Administrator created for you: a fresh install of the manager shows a page that lets whoever reaches it first create the administrator account. During first-login setup this AMI creates that account through the manager's own API (your admin email and a random 24-character password generated on your server) before anything is published, and checks that the password works, that a wrong password and the well-known default login admin@example.com  / changeme are refused, that nobody else can create a user and that anonymous API requests are refused. The management interface itself listens only on the loopback interface; it is reachable through Apache over HTTPS. The tests also create a proxy host, send a request for it through port 8080 to a service on the machine, and remove it again.

Pinned and tested: the application version is fixed, not 'latest', so a rebuild never changes the server behind your back. Patched base: Ubuntu 24.04 LTS built through an automated EC2 Image Builder pipeline, with security updates applied at build time.

What you should know

The manager's container runs as root inside its own container, as upstream builds it. The API status document and the API schema answer without a login by design, and the web interface shows user avatars through a third-party avatar service chosen by the application. The manager used about 110 to 210 MB of memory in our tests, so a t3.small (2 GB) is the recommended starting size.

Licence and attribution

Built on the open-source Nginx Proxy Manager (MIT licence). The image is unmodified. Not affiliated with, endorsed by, or sponsored by its author or by F5, Inc.; NGINX is a trademark of F5, Inc.

Getting Started Launch the AMI and open ports 22, 80, 443, 8080 and 8443 in the security group SSH in and answer the setup prompts (domain and admin email) Open https://your-domain/  and sign in with your admin email and the password printed at the end of setup Create your first proxy host; it is served on port 8080 or 8443

A domain name with an A record pointing at the instance is required for the management interface, because it is served over HTTPS.

This AMI is built and supported by Perimattic.

Book a free setup consultation at https://cal.com/gaurav-pareek-perimattic/marketplace-setup-consultations  or email us at aws-support@perimattic.com .

Support Managed and supported by Perimattic, a cloud infrastructure company with 13+ years of experience serving global clients. We offer free setup assistance, custom integrations, infrastructure consulting, and 24/7 support.