Welcome to the NocoBase AWS Deployment Guide. Seamlessly integrate NocoBase with AWS to enable secure, scalable, no-code data workflows and team collaboration. NocoBase gives your organization the ability to build internal tools, manage relational data, and automate business processes without sacrificing control over infrastructure.

With this guide, you will deploy a production-ready NocoBase instance using the AWS Marketplace AMI, configure DNS and SSL, and manage the application lifecycle with best-practice operational steps.

Prerequisites

Before you get started with the NocoBase 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 this guide to ensure this.)

Launching the AMI

Step 1: Find and Select "NocoBase" AMI

  1. Log in to your AWS Management Console.
  2. Navigate to the 'NocoBase' 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.
  1. Please wait for a few minutes while the processing takes place. Once it's completed, click on "Continue to Configuration".
  2. Select the "CloudFormation script to deploy NocoBase" as the fulfilment option and choose your preferred region on the "Configure this software" page. Afterward, click the "Continue to Launch" button.
  1. From the "Choose Action" dropdown menu in "Launch this software" page, select "Launch CloudFormation" and click "Launch" button.

Create CloudFormation Stack

Step 1: Create stack

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

Step 2: Specify stack options

Provide the necessary parameters for your NocoBase deployment. These settings define how your instance will be configured.

Parameter Description
Stack name A unique name for your CloudFormation stack (e.g., my-nocobase-deployment).
Admin Email The email address for generating SSL certificates with Let's Encrypt.
DeploymentName A name for your deployment, of your choice.
DomainName Your public domain name (e.g., nocobase.yourdomain.com). SSL will be set up automatically if the domain is hosted on Route 53. If unsuccessful, SSL must be set up manually.
InstanceType The EC2 instance type. We recommend t3.small or larger for optimal performance.
KeyName The name of your EC2 key pair for SSH access.
SSHLocation The IP address range for SSH access. Defaults to 0.0.0.0/0 (open to all). For better security, restrict this to your IP.
SubnetCidrBlock The CIDR block for the subnet. Defaults to 10.0.0.0/24.
VpcCidrBlock The CIDR block for the VPC. Defaults to 10.0.0.0/16.

Step 3: 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".

Step 4: Review

  1. Review and verify the details you've entered.
  2. Review CloudFormation Stack parameters
  3. Tick the box that says, "I acknowledge that AWS CloudFormation might create IAM resources with custom names".
  4. Acknowledge IAM resource creation
  5. 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.

CloudFormation Stack Creation

Update DNS

Step 1: Copy IP Address

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

Copy Public IP

Step 2: Update DNS

  1. Go to AWS Route 53 and navigate to "Hosted Zones". Click on the correct hosted zone.
  2. From there, click on "Create record".
  3. Create AWS Route 53 Record
  4. Add the record name and then paste the copied "PublicIp" into the "value" textbox.
  5. Click "Save".

Access NocoBase

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

NocoBase Dashboard URL

502 Bad Gateway Error?

If you encounter a "502 Bad Gateway" error, the application is likely still starting up. Please wait about 5 minutes and then refresh the page.

502 Bad Gateway error page

Important: During stack creation, you will be prompted to create the NocoBase Dashboard Email for your NocoBase deployment. The email address and password you enter at this stage will be used to manage your entire workspace. Choose a strong password and store your credentials securely, as they are essential for future access and ongoing team management.

Create Admin Account

Generate SSL Manually

Step 1: Copy IP Address

NocoBase will automatically try to setup SSL based on the provided domain name if that domain is hosted on Route 53. If its unsuccessful, you have to setup SSL manually. Proceed with the instructions outlined in the above "Update DNS" section, if you have not already done so. Copy the Public IP address indicated as "PublicIp" in the "Outputs" tab.

Copy Public IP

Step 2: 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>
Log in to the server
  1. Type "yes" and press Enter. This will log you into the server.

Step 3: 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

Step 1: 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>
Log in to the server
  1. Type "yes" and press Enter. This will log you into the server.

Step 2: Check the logs

sudo docker ps

Select the correct container and check logs:

sudo docker logs 0b
sudo docker logs a5
Check NocoBase container logs

Shutting Down NocoBase

  1. Click the link labeled "Instance" in the "Resources" tab to access the EC2 instance; you will be directed to the NocoBase instance in EC2.
  2. Access the EC2 instance
  3. Select the NocoBase 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".
  4. Stop the NocoBase instance

Remove NocoBase

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 backup the necessary server data before removing.

Troubleshoot

1. vCPU Quota Error

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

vCPU Quota Error

2. Insufficient Capacity Error

If you face the 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.

Insufficient Capacity Error

3. API Dashboard Access Error

If you face a 502 Bad Gateway error when you try to access the NocoBase dashboard, please wait 5-10 minutes and then try.

502 Bad Gateway Error

4. Storage Full Error

Check whether the instance storage is full.

Log into the server and run the below command:

df -h
Checking disk usage with df -h

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 NocoBase service.

Conclusion

The Meetrix NocoBase Deployment Guide is your definitive resource for integrating NocoBase into AWS with ease. Designed for DevOps engineers, system administrators, and IT leaders, it offers clear, step-by-step instructions to achieve a secure and scalable deployment. NocoBase is a robust open-source platform that empowers teams in high-trust environments with real-time collaboration, automation, and flexible integrations. Using this guide, you can unlock NocoBase's full potential, enabling your organization to create efficient, secure, and self-hosted communication systems that grow with your needs.

Technical Support

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

Frequently Asked Questions

Can I use my own domain name with NocoBase?

Yes. NocoBase supports custom domain names. The deployment guide provides instructions for configuring DNS records to point to your NocoBase instance. SSL is automatically set up if your domain is hosted on Route 53.

Is my NocoBase data secure on AWS?

Yes. When you deploy NocoBase on your AWS account, you retain full control over your data, network security, and access policies, ensuring a secure environment for your operations.

What instance types are recommended for NocoBase?

We recommend starting with t3.small for development and testing. For production workloads, choose t3.medium or larger based on your performance needs.

How do I scale my NocoBase deployment?

NocoBase deployments on AWS are flexible. You can increase your EC2 instance type and adjust AWS resources to handle higher workloads; for advanced scaling, consider using load balancing and additional database optimization.

Ready to Launch Your Own NocoBase Instance?

Launch NocoBase with Meetrix and deploy a secure, self-hosted no-code platform for your team.

Deploy NocoBase on AWS Marketplace