Welcome to the Flowise Deployment Guide for AWS! Flowise is an open-source, low-code platform that lets you build powerful LLM-powered applications through a visual drag-and-drop interface. Deploy it on AWS with the Meetrix pre-configured AMI and start building AI chatbots, agents, and LLM workflows in minutes — no complex setup required.

Prerequisites

Before you get started with the Flowise 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/blogs/increase-aws-vcpu-quota/ to ensure this).
  • An SSH key pair created in your target AWS region.
  • A registered domain name (optional but recommended for SSL setup).

Launching the AMI

Step 1: Find and Select the 'Flowise' AMI

  1. Log in to your AWS Management Console.
  2. Navigate to the Flowise product in AWS Marketplace.

Step 2: Initial Setup & Configuration

  1. Click the "Continue to Subscribe" button.
  2. Accept the terms and click "Continue to Configuration".

Step 3: Launching the Instance

  1. Click "Continue to Launch". You will be presented with two service options:
AWS service options: AWS CloudFormation or Amazon EC2
  • AWS CloudFormation — Automated, one-step deployment. (Recommended — this guide follows this path.)
  • Amazon EC2 — Custom deployment using Amazon Machine Image (AMI).

If you select "Amazon EC2", two additional launch methods appear:

Amazon EC2 selected showing Launch from EC2 Console and One-click launch options
  • Launch from EC2 Console — Scalable method with full control over configuration. Selecting this reveals the AMI details panel and a "Launch from EC2" button. Click it to be taken to the EC2 launch wizard. Launch from EC2 Console option with AMI details and Launch button
  • One-click launch from AWS Marketplace — Quick deployment with minimal configuration. Selecting this reveals a configuration form where you set the region, number of instances, instance type (default: t3a.medium), VPC, subnet, security group, and key pair. One-click launch configuration form showing instance type, VPC, subnet, security group, and key pair

    For the security group, click "Create security group" to auto-generate a vendor-recommended group with the required inbound rules: SSH (TCP/22), HTTP (TCP/80), and HTTPS (TCP/443).

    One-click launch configuration form showing instance type, VPC, subnet, security group, and key pair

This guide follows the AWS CloudFormation path. Select "AWS CloudFormation" and click "Launch" to continue.

Create CloudFormation Stack

Step 1: Create Stack

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

Step 2: Specify Stack Details

  1. Provide a unique "Stack name".
  2. Enter a value for "DeploymentName" (e.g., prod).
  3. Provide a public domain for "DomainName". Flowise will automatically try to set up SSL if the domain is hosted on Route53. If unsuccessful, you must set up SSL manually.
  4. Choose an instance type for "InstanceType" (Recommended: t3a.medium).
  5. Enter the Flowise username for login.
  6. Enter the Flowise password for login.
  7. Select your SSH key pair for "KeyName".
  8. Set "SSHLocation" to 0.0.0.0/0 to allow SSH from any IP, or restrict it to your own IP for better security.
  9. Keep "SubnetCidrBlock" as 10.0.0.0/24.
  10. Keep "VpcCidrBlock" as 10.0.0.0/16.
  11. Click "Next".

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 and Submit

  1. Review and verify all the details you have entered.
  2. Reviewing CloudFormation stack parameters for Flowise
  3. Provide the "Admin Email" for SSL generation.
  4. Tick the box that says "I acknowledge that AWS CloudFormation might create IAM resources with custom names".
  5. Acknowledge IAM capabilities in CloudFormation
  6. Click "Submit".

You will be directed to the CloudFormation stacks page. Please wait 5–10 minutes until the stack status shows CREATE_COMPLETE.

Flowise CloudFormation stack successfully created

Update DNS

Step 1: Copy IP Address

Once the stack is created, open the "Outputs" tab of your CloudFormation stack and copy the public IP labeled "PublicIp".

Copying the PublicIp from CloudFormation Outputs tab

Step 2: Update DNS

  1. Go to AWS Route 53 and navigate to "Hosted Zones".
  2. Click Create record.
  3. Add a record name and paste the copied PublicIp into the value textbox.
  4. Click "Save".
Creating a DNS record in AWS Route 53 for Flowise

Access Flowise

Access Flowise using the "DashboardUrl" or "DashboardUrlIp" provided in the Outputs tab.

Flowise DashboardUrl in CloudFormation Outputs

Note

If you receive a "502 Bad Gateway" error, wait approximately 5 minutes and refresh the page. The application may still be initializing.
Flowise login page

Generate SSL Manually

Flowise will automatically try to set up SSL when a Route53-hosted domain is provided. If it fails, follow these steps to generate SSL manually.

Step 1: Copy IP Address

  1. Follow the Update DNS steps above, if not already done.
  2. Copy the Public IP indicated as "PublicIp" in the "Outputs" tab.

Step 2: Log in to the Server

  1. Open the terminal and navigate to the directory where your private key (.pem) file is located.
  2. Run:
ssh -i /path/to/your-key.pem ubuntu@<PublicIp>
  1. Type yes when prompted to accept the host fingerprint.
Logging into Flowise server via SSH

Step 3: Generate SSL

Run the following command and follow the prompts:

sudo bash /root/certificate_generate_standalone.sh

Check Server Logs

Step 1: Log in to the Server

ssh -i /path/to/your-key.pem ubuntu@<PublicIp>
Logging into Flowise server via SSH

Step 2: Check the Logs

sudo docker ps

sudo docker logs <container-id-prefix>
Checking Docker container logs for Flowise

Shutting Down Flowise

  1. In the CloudFormation stack, click the "Resources" tab and find the "Instance" link to navigate to the EC2 instance.
  2. CloudFormation Resources tab showing the EC2 instance
  3. In the EC2 console, select the instance checkbox and choose "Stop instance" from the "Instance state" dropdown. You can restart it at any time by selecting "Start instance".
  4. Stop the Flowise EC2 instance

Remove Flowise

To fully remove the deployment, delete the CloudFormation stack from the AWS Management Console under CloudFormation → Stacks by selecting the stack and clicking the "Delete" button. This will remove all associated AWS resources including the EC2 instance, VPC, and Elastic IP.

Upgrades

When a newer version of the Flowise AMI is published, we will update the product in AWS Marketplace. To upgrade, check the product version in the Marketplace. If a newer version is available, remove the previous deployment and re-launch using the updated AMI. Always back up any custom flows and configurations before removing.

Troubleshoot

  1. vCPU quota exceeded — if you see a quota error during stack creation, follow this guide to request a vCPU quota increase. vCPU limit exceeded error in CloudFormation events
  2. Insufficient instance capacity — if the stack creation fails with an InsufficientInstanceCapacity error, try a different AWS region or retry at a later time. InsufficientInstanceCapacity error in CloudFormation events
  3. 502 Bad Gateway — wait 5 minutes and refresh. If the error persists, SSH into the server and check the container status:
    sudo docker ps
    sudo docker logs <container-id-prefix>
    502 Bad Gateway error on Flowise
  4. Disk usage full — check disk usage to ensure the instance storage is not full. Log into the server and run:
    df -h
    If the root volume is between 90–100% used, increase the EBS volume size following AWS documentation, then reboot the instance.

Conclusion

The Meetrix Flowise Deployment Guide helps you set up a production-ready LLM application builder on AWS quickly and reliably. Whether you're a DevOps engineer, AI developer, or startup founder, this guide provides everything you need to deploy Flowise, configure SSL, and start building intelligent workflows on your own infrastructure.

Technical Support

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

Frequently Asked Questions

What is Flowise?

Flowise is an open-source, low-code platform that allows you to build powerful LLM-powered applications through a visual drag-and-drop interface. It enables you to create AI chatbots, agents, and LLM workflows without complex setup.

What are the prerequisites for deploying Flowise on AWS?

You need basic knowledge of AWS services (EC2, CloudFormation), an active AWS account with appropriate permissions, an SSH key pair in your target region, and sufficient vCPU limits. A registered domain name is optional but recommended for SSL setup.

Which instance type is recommended for Flowise?

t3a.medium is recommended as a baseline for running Flowise on AWS.

How does SSL get configured for Flowise?

Flowise will automatically try to set up SSL if the domain you provide is hosted on Route53. If it fails, you can manually generate SSL by SSHing into the server and running sudo /root/certificate_generate_standalone.sh.

How do I handle upgrades?

When a newer version of the Flowise AMI is published in AWS Marketplace, remove the previous deployment after backing up your custom flows and configurations, then relaunch using the updated AMI.

How do I get technical support?

Reach out to Meetrix Support at <a href='mailto:aws@meetrix.io'>aws@meetrix.io</a> for assistance with Flowise deployment issues.

Ready to Deploy Your Own Flowise Instance?

Get started in minutes with our pre-configured AMI and start building powerful LLM applications on your own AWS infrastructure.

Deploy Flowise from AWS Marketplace