Overview
This AMI runs Parse Server, the open-source backend framework for mobile and web apps, with MongoDB 7.0 on Ubuntu 24.04 LTS. It gives your applications a REST API (and the Parse client SDKs' protocol) for objects, users, sessions and roles, backed by a database you control. The upstream vendor images, Parse Server 9.11.0 and MongoDB 7.0.45, are pinned and baked into the AMI, so first start does not depend on a registry.
What Perimattic adds
No shared or default keys: at first login this AMI generates, on your server, a random application id, a REST API key, a master key, a read-only master key and the database passwords (24 characters each). Parse Server is started with clients unable to create classes, and custom object ids switched off. There are no default or shared credentials in the image. Apache provides HTTPS with a free Let's Encrypt certificate for your domain.
Limits you should know
There is no admin web page in this image: you manage classes, data and permissions through the REST API or the Parse SDKs, using the master key. Only GET /parse/health answers without the application id and a key. Clients cannot create classes; you create each class first with the master key and set its class-level permissions, because a new class is open to read and write for every holder of the REST key until you restrict it. Anyone who holds the REST key can also sign up users, as in any Parse backend. The master keys work from any address over HTTPS by default; the allowed addresses can be limited in /opt/app/.env. Cloud Code files, push providers, file storage adapters and email adapters are not configured. Data is stored in /opt/app/mongo on the root volume (mode 700), so choose the root EBS volume size for your data and take EBS snapshots for backup.
In our tests Parse Server used about 150 MB and MongoDB about 290 MB of memory when empty, and a t3.small (2 GB) passed all tests. A t3.medium (4 GB) is the recommended starting size for real workloads.
Licence and attribution
Parse Server is released under the Apache License 2.0. MongoDB 7.0 is released under the Server Side Public License (SSPL) version 1; the unmodified upstream image is used. Built on the open-source Parse Server (Apache-2.0). Not affiliated with, endorsed by, or sponsored by the Parse Platform project; Parse 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) Copy the application id and the keys printed at the end of setup Call https://your-domain/parse/schemas with the headers X-Parse-Application-Id and X-Parse-Master-Key, then create your classes
A domain name with an A record pointing at the instance is required, because the API 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
- Parse Server 9.11.0 (Apache-2.0) with MongoDB 7.0.45 (SSPL), pinned and pre-installed: a REST API backend for apps on your own server.
- Secure first login: a random application id, REST key, master key, read-only master key and database passwords are generated on your server; requests without the id and a key are refused; MongoDB has authentication on and no published port.
- 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: Parse Server 9.11.0 (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.
- Parse Server has no accounts of its own: a random application id, REST key, master key and read-only master key are generated at first login; setup verifies that requests without the id and a key are refused, that clients cannot read the schema or create classes, and that the read-only master key cannot write, before the site is published.
- Application: Parse Server 9.11.0 (Apache-2.0) with MongoDB 7.0.45 (SSPL), unmodified upstream images, pinned. MongoDB has authentication on and publishes no port.
- No admin web page is included; clients cannot create classes.
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. Empty, Parse Server used about 150 MB and MongoDB about 290 MB (about 800 to 880 MB for the whole host); a t3.small (2 GB) passed all tests. Size up with your data and traffic.
-
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 Parse Server
-
Point a domain at the instance
Create a DNS A record (for example api.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 application id, REST API key, master key, read-only master key and two database passwords on your server
- Starts MongoDB with authentication on, creates the application's database user, then starts Parse Server
- Checks that requests without the application id and a key are refused, that the REST key cannot read the schema or create a class, that the master key works, that the read-only master key cannot write and that MongoDB refuses unauthenticated connections
- Configures Apache as an HTTPS reverse proxy and requests a Let's Encrypt certificate
- Prints the server URL, the application id and the keys; 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 Parse Server
Call https://<your-domain>/parse/schemas with the headers 'X-Parse-Application-Id: <id>' and 'X-Parse-Master-Key: <master key>' (view the id and keys again with: sudo cat /opt/app/access.txt). Create your classes with the master key; client apps then use the application id and the REST API key.
-
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 /opt/app/mongo: back up /opt/app (including /opt/app/.env, which holds the keys) or snapshot the volume before upgrades. The master keys are for server-side use only: never put them in a client app. To limit the addresses that may use them, set MASTER_ALLOWED_IPS in /opt/app/.env and run: cd /opt/app && sudo docker compose up -d. There is no admin web page; use the REST API with the master key.
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.