This product has charges associated with it for hardening, security configuration, and support.
Supabase is an open-source Firebase alternative: a PostgreSQL database with instant REST and GraphQL APIs, an authentication server, realtime subscriptions, and object storage, delivered as a self-hosted docker-compose stack with the Studio dashboard. Unlike bare Supabase AMIs that ship with the public demo JWT secret, the well-known anon/service-role API keys, and the default dashboard password, this Lynxroute build is ready out of the box: every secret and both API keys regenerated per instance at first boot, host Nginx with TLS in front of the Kong gateway, all eleven container images SHA-pinned, UFW firewall pre-configured, on a CIS Level 1 hardened Ubuntu 24.04 LTS base.
Apache-2.0 license - fully auditable, no vendor lock-in.
This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.
WHAT IS SUPABASE
Supabase is an open-source Firebase alternative built on PostgreSQL. It turns a Postgres database into a full application backend: instant RESTful and GraphQL APIs over your tables (PostgREST), a complete authentication and user-management server with email and JWT support (GoTrue), realtime subscriptions over WebSockets, S3-compatible object storage with on-the-fly image transformation, serverless edge functions, and the Supabase Studio dashboard for managing it all from the browser. The self-hosted edition runs as a docker-compose deployment of eleven services - Studio, the Kong API gateway, Auth, REST, Realtime, Storage, imgproxy, postgres-meta, Edge Functions, the Postgres database, and the Supavisor connection pooler. Build a backend for web and mobile apps without writing server code: define tables, get APIs and a typed client instantly, manage users, and subscribe to changes. Apache-2.0 license, no vendor lock-in.
WHAT THIS AMI ADDS
Security hardening:
Every secret regenerated per instance at first boot - the Postgres password, the JWT signing secret, the dashboard password, the Realtime/Supavisor key base, the Vault and postgres-meta encryption keys, and the Storage S3 keys. The publicly known upstream demo values are never used.
Both API keys (anon and service_role) are freshly minted JWTs re-signed from the per-instance JWT secret - the default anon/service-role keys that ship with bare Supabase are public and grant full database access
Host Nginx fronts the Kong API gateway on TCP 443 with a self-signed certificate; HTTP redirects to HTTPS; the Studio dashboard is protected by HTTP basic auth
All eleven container images (Studio, Kong, Auth, REST, Realtime, Storage, imgproxy, postgres-meta, Edge Functions, PostgreSQL, Supavisor) pinned by SHA-256 digest with explicit linux/amd64 platform - reproducible builds, no surprise upgrades on rebuild
Kong, Postgres (5432) and the Supavisor pooler (6543) bind to 127.0.0.1 only - Nginx on 443 is the sole public-facing endpoint by default
UFW firewall pre-configured - only TCP 22, 80, 443 are exposed
fail2ban, AppArmor
CVE scan - every image is scanned for vulnerabilities before release
OS hardening (CIS Level 1):
CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
CIS Conformance Report at /etc/lynxroute/cis-report.html
CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
ARCHITECTURE NOTES
A single host Nginx vhost on TCP 443 terminates TLS and proxies to the Kong gateway, which routes internally to Studio (/), Auth (/auth/v1), REST and GraphQL (/rest/v1, /graphql/v1), Realtime (/realtime/v1, WebSocket), Storage (/storage/v1), and Edge Functions (/functions/v1). Postgres data and uploaded objects persist at /opt/supabase/volumes/db/data and /opt/supabase/volumes/storage - operators can attach an EBS volume there. Direct database access on ports 5432 (session) and 6543 (transaction pooler) is bound to localhost by default; open it explicitly when you need external connections. Replace the self-signed certificate with a CA-signed certificate for production using Certbot, then set SUPABASE_PUBLIC_URL, API_EXTERNAL_URL and SITE_URL in /opt/supabase/.env to your HTTPS hostname so auth callbacks, storage URLs and the Studio dashboard use the new origin.
Highlights
Supabase security baked in: the Postgres password, JWT secret, dashboard password and both API keys (anon + service_role) are regenerated per instance at first boot, host nginx puts TLS in front of the Kong gateway, all eleven images SHA-pinned - unlike bare Supabase AMIs that ship with the public demo JWT secret, the well-known anon/service-role keys, and the default dashboard password.
CIS Level 1 hardened Ubuntu 24.04 LTS: auditd, fail2ban, AppArmor, SSH key-only, IMDSv2 enforced. CVE-scanned before every release. SBOM (CycloneDX) and CIS Conformance Report included.
A full open-source backend: PostgreSQL with instant REST and GraphQL APIs, authentication, realtime subscriptions, object storage, edge functions, and the Studio dashboard. Self-hosted, your data stays in your account. Apache-2.0 license - fully auditable, no vendor lock-in, ever.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Try this product free for 5 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.
You pay by the hour for the compute instance you run this hardened image on. The three options are AWS EC2 instance sizes, not feature tiers. The m6i.large and m6i.xlarge are general-purpose instances, with the xlarge offering more vCPU and memory than the large. The t3.large is a burstable general-purpose instance. Your hourly cost scales with the instance size you pick. Every option ships the same hardened, pre-configured image, so you choose based on the compute capacity your workload needs.
Top-of-mind questions for buyers
Am I charged the hourly software fee when my instance is stopped or paused?
The hourly software fee meters running time only. A fully stopped instance does not accrue the hourly software charge. You may still pay underlying AWS storage fees for the attached volume while the instance is stopped, but those are separate AWS charges, not the software rate.
What exactly does one billable hour cover on the m6i.large, m6i.xlarge, or t3.large?
One billable hour covers one running instance of the size you pick. Each option is an AWS EC2 instance type. The m6i.large and m6i.xlarge are general-purpose sizes with differing vCPU and memory. The t3.large is a burstable general-purpose size. Every image ships the same hardened Ubuntu 24.04 build.
If my workload grows, do I switch instance sizes automatically or manually?
You choose the size manually. There is no automatic tier upgrade. To move from t3.large or m6i.large to m6i.xlarge, you launch or resize to the sized instance you want. Your hourly cost then reflects the new size. The hardened image content stays identical across all three options.
lynxroute.com
Helpful?
Vendor refund policy
We do not offer refunds for this product. AWS infrastructure charges (EC2, EBS, data transfer) are billed separately by AWS and are not refundable by us.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
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
Supabase v2026.07.07
Supabase self-host snapshot updated to 2026.07.07 (Studio dashboard refresh; bundled PostgreSQL kept on 15.x for data-directory compatibility)
Certbot pre-installed - enable HTTPS with one command: sudo certbot --nginx -d yourdomain.com
Rebuilt on the latest CIS Level 1 hardened Ubuntu 24.04 LTS base
Additional details
Usage instructions
Launch instance (t3.large recommended; the bundled stack runs eleven containers and needs about 8 GB RAM)
Open Security Group - restrict TCP 443 to YOUR IP/32 until you have logged in (the anon and service_role API keys in the credentials file grant full API access)
Wait for first-boot initialization to finish - on first launch the stack takes about 2 to 5 minutes (database migrations plus eleven containers). A loading page is shown until the backend is ready, then it switches to the dashboard automatically.
Open https://<PUBLIC_IP> in your browser - accept the self-signed certificate warning, then log in to the Studio dashboard with the basic-auth username and password from the credentials file
Use the API from your application: the project URL is https://<PUBLIC_IP> and the anon and service_role keys are in the credentials file. Example: curl https://<PUBLIC_IP>/rest/v1/ -H "apikey: YOUR_ANON_KEY" -k
API routes (through the Kong gateway on https://<PUBLIC_IP>):
/auth/v1/ Authentication (GoTrue)
/rest/v1/ Auto-generated REST API (PostgREST)
/graphql/v1 GraphQL API
/realtime/v1/ Realtime subscriptions (WebSocket)
/storage/v1/ Object storage
/functions/v1/ Edge functions
Direct Postgres access:
Ports 5432 (session pooler) and 6543 (transaction pooler) are bound to 127.0.0.1 by default. To connect an external client, change the supavisor port binding in /opt/supabase/docker-compose.yml from 127.0.0.1 to 0.0.0.0, run sudo systemctl restart supabase, and open the port in the Security Group. The Postgres password is in /root/supabase-credentials.txt.
Stack management:
cd /opt/supabase && sudo docker compose ps
cd /opt/supabase && sudo docker compose logs -f kong
sudo systemctl restart supabase
Replace the self-signed TLS certificate with a CA-signed certificate for production using Certbot or another ACME client. After the certificate is issued, edit /opt/supabase/.env and set SUPABASE_PUBLIC_URL, API_EXTERNAL_URL and SITE_URL to https with your domain, then sudo systemctl restart supabase so auth callbacks, storage URLs and the dashboard use the new hostname.
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.
Supabase is the Postgres development platform. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, Storage, and Vector embeddings.
This product has charges associated with it for seller support. Supabase on Ubuntu 24.04 is an optimized Amazon Machine Image (AMI) designed to empower developers with a powerful backend-as-a-service platform. This AMI seamlessly integrates PostgreSQL, authentication, and real-time capabilities, making it ideal for building scalable applications. Its pre-configured environment ensures rapid deployment and simplifies the setup process, allowing teams to focus on development rather than infrastructure. Leveraging the latest features of Ubuntu 24.04, this image guarantees enhanced security and performance. Use cases include web and mobile application development, data-driven applications, and collaborative projects requiring real-time data synchronization. Empower your development workflow with this reliable, feature-rich AMI that accelerates project delivery and reduces operational overhead.
This product has a fee associated with the provision and deployment of the application and AMI support. This product is an open-source Firebase alternative that offers a suite of tools designed to help developers build modern web and mobile applications based on the Supabase open source code.
This product has charges associated with it for seller support. Supabase Ubuntu 26 self hosting with Docker offers a powerful solution for developers looking to deploy a fully managed backend quickly and efficiently. Leveraging Docker containers, this AMI simplifies the installation process, allowing you to run Supabase - an open-source Firebase alternative - with ease. Enjoy the flexibility of scalable database management, real-time subscriptions, and a user-friendly API. Ideal for startups and enterprises seeking rapid prototyping or full-scale production environments, this AMI supports various integrations and provides seamless updates. Whether you're building a web application or enhancing an existing project, this self-hosted solution empowers teams to take control of their backend infrastructure while benefiting from the reliability of Ubuntu and the robustness of Docker.
This product has charges associated with it for seller support. Hossted Platform offers an intuitive dashboard and CLI that delivers comprehensive security, monitoring, logging, and applicative insights.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.