Overview
This AMI runs a self-hosted identity and access management platform with PostgreSQL 17 on Ubuntu 24.04 LTS: an identity provider for OpenID Connect, OAuth 2.0 and SAML single sign-on, with organisations, users, roles, a management console, a separate login interface (password, passkeys and multi-factor options) and gRPC, gRPC-web and REST APIs. The upstream vendor images, release 4.20.1, are pinned together with PostgreSQL 17.11 and baked into the AMI, so first start does not depend on a registry.
What Perimattic adds
First administrator created for you, self-registration off: during first-login setup this AMI starts the platform with its first-instance settings, which create the one administrator (your email address as the login name and a random 24-character password generated on your server), and sets the login policy so that nobody can register themselves. A fresh install otherwise ships a documented default administrator login; none exists here, and setup checks that it is refused. Setup also checks that a wrong password and a stranger's login are refused, that anonymous API requests are refused and that the registration page offers no form. The master key (exactly 32 characters), the login interface's cookie secret and the database passwords are generated per instance; the machine token that the login interface uses is moved into a root-only file and its bootstrap file is deleted. There are no default or shared credentials in the image, and usage telemetry is off.
HTTPS and HTTP/2: Apache is configured as a reverse proxy and a free Let's Encrypt certificate is requested for your domain with certbot. The platform needs cleartext HTTP/2 behind the proxy, so setup enables Apache's HTTP/2 proxy module and routes the login interface separately. The tests prove the console, the login interface, OIDC discovery, a complete administrator sign-in (authorization code with PKCE) and a gRPC-web call through Apache. Both services listen only on the loopback interface and PostgreSQL is reachable only inside the Docker network.
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
No mail server is configured, so verification codes, invitations and password-reset emails do not work until you add your own SMTP provider in the console (the administrator's address is pre-verified). Native gRPC clients were not tested through Apache; gRPC-web, Connect and REST were. Keep a copy of the master key in /opt/app/.env: a restored database cannot be used without it.
The platform is light for what it does: about 215 to 235 MB of memory for the server, 170 to 180 MB for the login interface and 100 to 140 MB for PostgreSQL in our tests, so a t3.medium (4 GB) is the recommended starting size; production use with many users needs more.
Licence and attribution
Built on the open-source ZITADEL (AGPL-3.0; some directories are under Apache-2.0 and MIT, including the login interface, which is MIT). The images are unmodified and the source is at github.com/zitadel/zitadel. Not affiliated with, endorsed by, or sponsored by ZITADEL AG; ZITADEL is a trademark of its owner. PostgreSQL is released under the PostgreSQL License.
Getting Started Launch the AMI and open ports 22, 80 and 443 in the security group SSH in and answer the setup prompts (domain and admin email) Open https://your-domain/ui/console and sign in with your email address and the password printed at the end of setup Add your SMTP provider, then create organisations, projects, applications and users
A domain name with an A record pointing at the instance is required, because the site 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.
Highlights
- Self-hosted OIDC, OAuth 2.0 and SAML identity provider 4.20.1 (AGPL-3.0) with PostgreSQL 17.11, pinned and pre-installed. Add your own SMTP provider for email.
- Secure first login: the first administrator is created with a random 24-character password and a per-instance master key; self-registration is off; no default login exists; HTTPS through Apache and Let's Encrypt.
- Built on patched Ubuntu 24.04 LTS and supported by Perimattic: free setup assistance at aws-support@perimattic.com.
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
- ...
Dimension | Cost/hour |
|---|---|
t3.medium Recommended | $0.03 |
t3.micro | $0.03 |
c3.2xlarge | $0.03 |
c3.4xlarge | $0.03 |
c3.8xlarge | $0.03 |
c3.large | $0.03 |
c3.xlarge | $0.03 |
c4.2xlarge | $0.03 |
c4.4xlarge | $0.03 |
c4.8xlarge | $0.03 |
Vendor refund policy
For any questions or concerns, please contact: Perimattic.com Email: aws-support@perimattic.com
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.
- Application: Identity and Access Platform 4.20.1 (container image pinned, baked into the AMI).
- Base: Ubuntu 24.04 LTS, fully patched at build time, built by an automated EC2 Image Builder pipeline.
- TLS: Apache reverse proxy with a Let's Encrypt certificate requested by certbot at first login.
- Credentials are generated on the instance at first login; none are present in the image.
- The first administrator is created by the platform's first-instance settings with a random 24-character password generated at first login, self-registration is off, and setup verifies that the password works, that a wrong password, a stranger and the documented default login are refused and that anonymous API requests are refused. The master key and cookie secret are generated per instance; the login machine token is kept in a root-only file.
- Application: upstream identity platform release 4.20.1 (AGPL-3.0; Apache-2.0 and MIT parts; unmodified official images) with PostgreSQL 17.11 (all pinned). Cleartext HTTP/2 between Apache and the platform; telemetry off. See the product description for the licence and attribution notice.
- No SMTP is configured. Native gRPC clients were not tested through Apache.
- Database: reachable only inside the Docker network.
Additional details
Usage instructions
-
Launch an Instance
From AWS Marketplace, click Continue to Subscribe and then Continue to Configuration to launch the AMI.
-
Choose the Recommended Instance Type
t3.medium (4 GB of memory) is the recommended starting size: the server used about 215 to 235 MB, the login interface 170 to 180 MB and PostgreSQL 100 to 140 MB in our tests (about 900 MB for the whole host). Add your own SMTP provider for email.
-
Configure Security Group
Allow inbound traffic on the following ports:
- 22 (SSH) - terminal access for setup
- 80 (HTTP) - needed to validate your domain for the TLS certificate
- 443 (HTTPS) - access to Identity and Access Platform
-
Point a domain at the instance
Create a DNS A record (for example auth.example.com) pointing to the instance's public IP before you log in.
-
Connect to the Instance
ssh -i <your-key.pem> ubuntu@<public-ip>
-
First-Login Setup
The first SSH login runs a guided setup:
- Prompts for your domain and admin email and checks the DNS A record
- Generates a random 24-character administrator password, two database passwords, a 32-character master key and the login interface's cookie secret on your server
- Starts PostgreSQL and the platform, which creates the first administrator, then starts the login interface; the one-time machine token is moved into a root-only file
- Checks that the password works, that a wrong password, a stranger and the documented default login are refused, that anonymous API requests are refused and that self-registration is off
- Configures Apache as an HTTPS reverse proxy (HTTP/2 to the platform) and requests a Let's Encrypt certificate
- Prints the URL and the administrator credentials; they are also stored in /opt/app/access.txt (root only)
If a step fails, fix the problem shown and log in again: the setup resumes where it stopped.
-
Access Identity and Access Platform
Open https://<your-domain>/ui/console and sign in with your email address and the generated password (view it again with: sudo cat /opt/app/access.txt). Add your SMTP provider in the console before relying on email.
-
Credentials
Generated on your server, never shared between customers. View them again with:
sudo cat /opt/app/access.txt
-
Manage the Services
cd /opt/app sudo docker compose ps sudo docker compose restart
Data is in the PostgreSQL database in /opt/app/postgres: back up all of /opt/app (including the master key in /opt/app/.env) or snapshot the volume before upgrades. No SMTP server is configured: add your own provider in the console for verification codes, invitations and password resets. Self-registration is off; administrators create users. This listing relies on factual use of the upstream name in the attribution notice only; the product is not affiliated with its vendor.
Thank you for subscribing.
Need Support or Customization? Perimattic's team can help with setup issues, custom features and integrations:
Email us: aws-support@perimattic.com WhatsApp: +91-92142 66896 Learn more: <www.perimattic.com >
We offer free setup assistance, custom development and integrations, and infrastructure consulting.
Resources
Vendor resources
Support
Vendor support
Support by Perimattic
Perimattic provides 24/7 support for all AWS Marketplace products. Our team has 13+ years of cloud infrastructure expertise serving global clients.
Contact Channels: Email: aws-support@perimattic.com WhatsApp: +91-92142 66896 Website: <www.perimattic.com >
What We Help With: Initial setup and configuration assistance (free) Troubleshooting connectivity, performance, and backup issues Custom development and integrations Infrastructure consulting and architecture review Migration planning from other solutions Automation solutions and scaling guidance
Instance Sizing Guidance: t2.medium or t3.medium: Development environments, small applications m5.large: Production workloads with moderate traffic m5.xlarge: High-traffic production deployments and larger datasets
For workload-specific sizing recommendations, contact our team for a free consultation.
Refunds and Issues: If you experience any issues or need to request a refund, contact us at aws-support@perimattic.com and we will respond promptly.
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.
Similar products


