Overview
This AMI runs a self-hosted backend-as-a-service platform, version 2.7.1, on Ubuntu 24.04 LTS: a database and auth service, file storage, serverless Functions and Sites, and realtime subscriptions for your own applications, managed from a web console. The vendor images are pinned and baked into the AMI, so first start does not depend on a registry.
What Perimattic adds
Your one console account is created for you on your own server during setup, through the application's own account API, before the site is reachable; the console is permanently limited to that single account, so no stranger can claim it. Apache provides HTTPS with a free Let's Encrypt certificate in front of the application.
Limits you should know
Serverless Functions and Sites run buyer-authored code in per-execution containers that the platform creates itself, so the two helper containers that manage this have access to the host's Docker socket; a compromised function execution could, in principle, affect the host, not just its own container. This instance runs four database engines by default (MariaDB, MongoDB, a Postgres build and ClickHouse for usage statistics) plus Valkey for caching, all private to the instance. No SMTP server is configured, so password-reset and invitation emails are not sent until you add one.
Licence and attribution
Built on the open-source Appwrite (BSD-3-Clause), unmodified except for configuration. Not affiliated with, endorsed by, or sponsored by Appwrite; Appwrite is a trademark of its owner.
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/ and sign in with the username and password printed at the end of setup Create your first project from the console and connect your application
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
- A self-hosted backend-as-a-service platform, version 2.7.1 (open-source), pinned and pre-installed: database, auth, storage, serverless functions and realtime for your own applications.
- Secure first login: your one console account is created for you on first boot before the site is published, and the console is permanently limited to that single account. 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
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: Backend-as-a-Service Platform 2.7.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.
- Only one console account ever exists: it is created once, through the application's own account API on your server, before the site is published, and setup verifies a second claim attempt (same email or a different one) is refused and that nothing account-specific is readable anonymously through the published domain.
- Serverless Functions and Sites execute buyer code in per-execution containers created by the platform; the executor and orchestrator containers (and only those) hold the host's Docker socket to do this, a disclosed, accepted tradeoff rather than an oversight.
- MongoDB 8.2.5 is pinned (newer than this pipeline's usual MongoDB ceiling) after confirming it boots cleanly on this pipeline's Ubuntu 24.04 base with no kernel incompatibility.
- Measured on a t3.xlarge across two full fresh-boot and reboot test cycles: the 20-container stack used about 3.3 GB combined, with ClickHouse (about 700 MB) and MongoDB (about 370 MB) the largest single containers.
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.xlarge (16 GB of memory) is the recommended size: the 20-container default stack (four databases, ClickHouse, the console, realtime, workers, schedulers and the Functions/Sites executor) used about 3.3 GB combined in testing, with ClickHouse (roughly 700 MB) and MongoDB (roughly 370 MB) the largest single containers; the rest is headroom for buyer Functions and Sites execution, which run in their own per-execution containers on top of this.
-
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 Backend-as-a-Service Platform
-
Point a domain at the instance
Create a DNS A record (for example backend.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 password and separate secrets for each database, the executor and the job queue on your server
- Starts the databases, caches and helper services, then the application itself, the console, workers, schedulers, the Functions/Sites executor and Traefik
- Claims the one console account through the application's own account API before Apache publishes anything, then checks a second claim attempt is refused and that nothing account-specific is readable anonymously
- Configures Apache as an HTTPS reverse proxy and requests a Let's Encrypt certificate
- Prints the URL, username and password; 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 Backend-as-a-Service Platform
Open https://<your-domain>/ and sign in with the username and password printed at the end of setup (view them again with: sudo cat /opt/app/access.txt). Create a project from the console and connect your application using the project's API endpoint and keys.
-
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
This instance runs four database engines by default (MariaDB for relational data, a Postgres build for vectors, MongoDB for documents and ClickHouse for usage statistics) plus Valkey for caching, none reachable from outside the instance. Back up or snapshot all of /opt/app and this instance's Docker volumes together (stop the stack first for a consistent copy). Security note: the Functions/Sites executor and its orchestrator have access to the host's Docker socket so they can run buyer-authored code in per-execution containers; that is how the vendor's own image ships this feature.
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.