Overview
This AMI runs Misskey, the open-source federated microblogging server, on Ubuntu 24.04 LTS. Misskey speaks ActivityPub, so accounts here can follow and be followed by accounts on other compatible servers such as Mastodon, once your domain is set up. The vendor image of Misskey 2026.11.0 is pinned and baked into the AMI, so first start does not depend on a registry. PostgreSQL stores your data and Valkey (the BSD-licensed Redis-compatible server) backs its job queue, both inside the instance and not reachable from outside.
What Perimattic adds
The sole administrator account is created for you during first-login setup, through Misskey's own one-time setup API, which is itself gated by a random setup password generated on your server; nothing is published through Apache until this finishes. A random 24-character administrator password is generated at the same time. Misskey ships with public sign-up closed by default, and this AMI leaves it that way: setup verifies that a stranger cannot sign up, cannot re-run the one-time setup, and that a wrong password is refused, before confirming the real credentials work. Apache provides HTTPS with a free Let's Encrypt certificate for your domain.
Limits you should know
Misskey may lazily create its own internal system.proxy account the first time certain backend services run; this is normal upstream behaviour (it caches remote content on behalf of local users), it carries no password and cannot be created, claimed or signed into by anyone, and setup and ongoing checks confirm it stays that way. Being a federation server, it can send and receive traffic from other servers once your domain resolves; outbound requests to private, loopback and link-local addresses are blocked by Misskey's own default protection. In our tests the application used roughly 400 to 450 MB of memory, with PostgreSQL using 60 to 80 MB and Valkey under 15 MB alongside it, so a t3.medium (4 GB) is the recommended starting size. Misskey does not send email in this setup.
Licence and attribution
Built on the open-source Misskey (AGPL-3.0 licence), unmodified vendor image. Not affiliated with, endorsed by, or sponsored by its authors; Misskey 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 as the username and password printed at the end of setup Review Settings > Instance before inviting anyone or enabling federation features you have not configured
A domain name with an A record pointing at the instance is required, because the site is served over HTTPS and because ActivityPub federation depends on your domain being reachable.
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
- Misskey 2026.11.0 (AGPL-3.0) pinned and pre-installed: federated, ActivityPub-based microblogging with PostgreSQL storage and a Valkey-backed job queue.
- Secure first login: the sole administrator is created through Misskey's own setup-password-gated API with a random 24-character password; public sign-up stays closed, and the one-time setup endpoint cannot be reused. 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: Misskey 2026.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.
- The sole administrator is created during first-login setup through Misskey's own setup-password-gated API; setup verifies the one-time setup endpoint cannot be reused, public sign-up stays closed, a wrong password is refused and the real credentials work.
- Misskey 2026.11.0 (AGPL-3.0, unmodified vendor image) with PostgreSQL 17 and Valkey 8, neither reachable from outside the instance.
- Outbound requests to private, loopback and link-local addresses are blocked by Misskey's own default protection; no proxy is configured.
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 application used roughly 400 to 450 MB in our tests, with PostgreSQL and Valkey alongside it.
-
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 Misskey
-
Point a domain at the instance
Create a DNS A record (for example social.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 and the one-time setup password on your server
- Starts Misskey and creates the sole administrator through its setup-password-gated API, then checks that the one-time setup cannot be reused, that public sign-up stays closed, that a wrong password is refused and that the real credentials work
- Configures Apache as an HTTPS reverse proxy (with WebSocket) 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 Misskey
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). Review Settings > Instance before inviting anyone.
-
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
Uploaded files are kept in /opt/app/files and the PostgreSQL data in /opt/app/postgres: back up or snapshot both before upgrades. Misskey may lazily create its own internal, passwordless system.proxy account the first time certain backend services run; this is expected upstream behaviour, not a sign-up.
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.