Supabase- Developer Guide

Gain the knowledge to install and configure Supabase on AWS using our step-by-step deployment guide. This in-depth resource guides you through the entire process from provisioning your cloud environment to securely deploying and optimizing Supabase for scalability, high availability, and performance on AWS. Whether you’re creating a DevOps command center or a secure team collaboration hub, this guide is designed to help you deploy Supabase efficiently and effectively within your cloud infrastructure.

Prerequisites

Before you get started with the Supabase AMI, ensure you have the following prerequisites:

• Basic knowledge of AWS services, including EC2 instances and CloudFormation.
• An active AWS account with appropriate permissions.
• Enough vCPU limit to create an instance(Follow https://meetrix.io/articles/how-to-increase-aws-quota/ blog to ensure this)

Launching the AMI

Step 1: Find and Select 'Supabase' AMI

1. Log in to your AWS Management Console.
2. Navigate to the 'Supabase' in  AWS Marketplace.

Step 2:  Initial Setup & Configuration

1. Click the "Continue to Subscribe" button.
2. After subscribing, you will need to accept the terms and conditions. Click on "Accept Terms" to proceed.
3. Please wait for a few minutes while the processing takes place. Once it's completed, click on "Continue to Configuration".
4. Select the "CloudFormation script to deploy Supabase" as the fulfilment option and choose your preferred region on the "Configure this software" page. Afterward, click the "Continue to Launch" button.
5. From the "Choose Action" dropdown menu in "Launch this software" page, select "Launch CloudFormation" and click "Launch" button.

Create CloudFormation Stack

Step1: Create stack

1. Ensure the "Template is ready" radio button is selected under "Prepare template".
2. Click "Next".

Step2: Specify stack options

1. Provide a unique "Stack name".
2. Provide the "Admin Email" for SSL generation.
3. For "DeploymentName", enter a name of your choice.
4. Provide a public domain name for "DomainName" (Supabase will automatically try to setup SSL based on provided domain name, if that domain hosted on Route53. Please make sure your domain name hosted on route53. If its unsuccessful then you have to setup SSL manually).
5. Choose an instance type, "InstanceType" (Recommended: t3.medium).
6. Select your preferred "keyName".
7. Set "SSHLocation" as "0.0.0.0/0".
8. Keep "SubnetCidrBlock" as "10.0.0.0/24".
9. Keep "VpcCidrBlock" as "10.0.0.0/16".
10. Click "Next".

Step3: Configure stack options

1. Choose "Roll back all stack resources" and "Delete all newly created resources" under the "Stack failure options" section.
2. Click "Next".

Step4: Review

1. Review and verify the details you've entered.

2. Tick the box that says, "I acknowledge that AWS CloudFormation might create IAM resources with custom names".

3. Click "Submit".

Afterward, you'll be directed to the CloudFormation stacks page.

Please wait for 5-10 minutes until the stack has been successfully created.

Update DNS

Step1: Copy IP Address

Copy the public IP labeled "PublicIp" in the "Outputs" tab.

Step2: Update DNS

1. Go to AWS Route 53 and navigate to "Hosted Zones".
2. From there click on Create record.

3. Add record name and then paste the copied "PublicIp" into the "value" textbox.

4. Click "Save".

Access Supabase

You can setup the Supabase application through the "DashboardUrl" or "DashboardUrlIp" provided in the "Outputs" tab. This will allow you to create an Admin account and all the future accounts will be created through the Admin panel.

(If you encounter a "502 Bad Gateway error", please wait for about 5 minutes before refreshing the page)

Please enter the SupabaseDashboardUsername and SupabaseDashboardPassword that you have provided. Ensure both are stored securely for future reference

Generate SSL Manually

Supabase will automatically try to setup SSL based on provided domain name, if that domain hosted on Route53. If its unsuccessful then you have to setup SSL manually.

Step1: Copy IP Address

1. Proceed with the instructions outlined in the above "Update DNS" section, if you have not already done so.
2. Copy the Public IP address indicated as "PublicIp" in the "Outputs" tab.

Step2: Log in to the server

1. Open the terminal and go to the directory where your private key is located.
2. Paste the following command into your terminal and press Enter: ssh -i <your key name> ubuntu@<Public IP address>.

3. Type "yes" and press Enter. This will log you into the server.

Step3: Generate SSL

Paste the following command into your terminal and press Enter and follow the instructions:

sudo /root/certificate_generate_standalone.sh

Admin Email is acquiring for generate SSL certificates.

Check Server Logs

Step1: Log in to the server

1. Open the terminal and go to the directory where your private key is located.
2. Paste the following command into your terminal and press Enter:
   ssh -i <your key name> ubuntu@<Public IP address>

3. Type "yes" and press Enter. This will log you into the server.

Step2: Check the logs

sudo docker ps

Select the correct container and check logs
sudo docker logs e8

Shutting Down Supabase

1. Click the link labeled "Instance" in the "Resources" tab to access the EC2 instance. You will be directed to the Supabase instance in EC2.

2. Select the Supabase instance by marking the checkbox and click "Stop instance" from the "Instance state" dropdown. You can restart the instance at your convenience by selecting "Start instance".

Remove Supabase

Delete the stack that has been created in the AWS Management Console under 'CloudFormation Stacks' by clicking the 'Delete' button.

Upgrades

When there is an upgrade, we will update the product with a newer version. You can check the product version in AWS Marketplace. If a newer version is available, you can remove the previous version and launch the product again using the newer version. Remember to back up the necessary server data before removing.

Troubleshoot

1. If you face the following error, please follow https://meetrix.io/articles/how-to-increase-aws-quota/ blog to increase the vCPU quota.

2. If you face the following error (do not have sufficient <instance_type> capacity...) while creating the stack, try changing the region or try creating the stack at a later time.

3. If you face the below error when you try to access the API dashboard, please wait 5-10 minutes and then try.

4. Check whether the instance storage is full.

• Log into the server and run the below command

              df -h

             root volume

• If the root volume is between 90-100%, it is better to resize EBS volume. Please follow AWS documentation to increase the EBS volume.
• Then reboot the instance and restart the llama service.

Conclusion

The Meetrix Supabase Deployment Guide offers step-by-step instructions to help you securely and seamlessly deploy Supabase on AWS. Designed for DevOps engineers, system administrators, and IT leaders, this guide empowers your team to build a scalable, self-hosted communication platform. Unlock real-time collaboration, automation, and integration capabilities tailored for high-trust environments all with clarity and confidence.

Technical Support

Reach out to Meetrix Support (aws@meetrix.io)  for assistance with Supabase issues.