Skip to main content


This page provides steps to install Appsmith on a single node EC2 Linux + Networking ECS Cluster using an EC2 instance.


  • Amazon Web Services (AWS) account. If you don't have one, Create an AWS Account.
  • An Amazon EC2 key pair. If you don't have one, Generate an SSH Key pair.
  • An Amazon Security group with ports 80, 443, and 22 accessible. If you don't have one, Create a Security Group
  • To enable port access, add an inbound rule for the port ranges 80, 443, and 22 to the security group you created above.
  • Ensure you have created the security group and the SSH key pair in the same region.
  • You will not be able to use the built-in MongoDB with EFS as it will cause the Appsmith instance to crash. Hence, ensure you have set up and can access an external MongoDB instance hosting MongoDB V5.0 or later. For more information, see External MongoDB.

Create EFS volume

  1. Navigate to the Elastic File System section of the AWS Management Console and click the Create file system button.
  2. Provide a meaningful name to your file system, configure the VPC settings as required, and click Create.
  3. Select the file system you created above from the list and switch to the Network tab.
  4. Click the Manage button, and assign the security group that allows NFS access on port 2049. If you don't have such a security group:
    • Follow the Create a Security Group guide and include an inbound rule for NFS access on port 2049.
    • Once created, attach this security group to your EFS.

Install Appsmith

To deploy Appsmith on the Amazon ECS cluster that has a single node, you need to complete the below essential steps:

Create ECS cluster

  1. From the AWS Management Console, navigate to the Elastic Container Service (ECS) section.
  2. If you already have a single-node EC2 Linux + Networking ECS Cluster with 1 instance, you may skip to creating task and container definitions. If not, continue with the following:
  3. Click Clusters in the left sidebar, then click the Create Cluster button.
  4. Cluster name - Give a meaningful name to your cluster. For example, appsmith-ecs-ec2-cluster.
  5. Configure the Infrastructure settings as follows:
    • Choose Amazon EC2 instances
    • Provisioning Model: Choose On-demand
    • Auto Scaling Group: Keep default selection
    • Operating system/Architecture: Amazon Linux 2
    • EC2 instance type: Select at least a t3.medium or a t3a.medium instance type.
    • Desired Capacity: Give Minimum as 1 and Maximum as 2
    • SSH Key pair: Use the key pair created in the Prerequisites section Keep default settings for other attributes.
  6. Configure the Network Settings for Amazon EC2 instances section as shown below:
    • VPC: Choose your existing VPC or create a new one VPC
    • Subnets: Select subnets that provide public access
    • Security group: Use the security group created earlier in the [Prerequisites] section
    • Auto-assign public IP: Choose Turn on
  7. Configure the Monitoring section by toggling on the Use container insights setting
  8. Click the Create button to create your cluster. You'll see the ECS cluster under Clusters.

Create task and container definition

  1. Go to Task definitions from the ECS section in the sidebar of the AWS Management Console.
  2. Click the Create new task definition button and select Create new task definition from the dropdown.
  3. Under the Task definition configuration, give a meaningful name to the task definition by adding the name in the Task definition family field. For example, appsmith-ecs-ec2-cluster-task-def
  4. Configure the Infrastructure requirements as shown below:
    • Launch type - Amazon EC2 instances
    • Network mode - default
    • Task role and Task execution role as default. For all other fields keep the default settings.
  5. Configure the Container-1 as shown below:
    • Name - Give a meaningful name. For example, appsmith
    • Image URI -
    • Under the Environment variables section, click the Add environment variable button, and add the below environment variables in the Key and their values in the Value fields:
      • APPSMITH_ENCRYPTION_PASSWORD: Add a password to encrypt all credentials in the database. It's recommended to use a random password.
      • APPSMITH_ENCRYPTION_SALT: Use encryption salt to encrypt all credentials in the database. It's recommended to use a random password.
      • APPSMITH_SUPERVISOR_PASSWORD : Password to access the supervisor console to watch the processes in the Appsmith container. It's recommended to use a random password.
      • APPSMITH_MONGODB_URI : Enter the URI of the external MongoDB (v5.0 or later) instance.
      • APPSMITH_ENABLE_EMBEDDED_DB to 0. This disables embedded mock databases on EFS volume.
  6. Configure the HealthCheck section as shown below:
    • HealthCheck Command - CMD-SHELL, curl http://localhost/ || exit 1
    • Interval - 10
    • Timeout - 2
    • Start period - 160
    • Retries - 3
  7. Keep the default settings for other sections, and scroll down to Storage. Click Add volume button and configure Volume-1 as shown below:
    • Volume type- EFS
    • Configure the Storage configurations as show below:
      • Volume name- Give a meaningful name. For example, appsmith-ecs-ec2-cluster-efs-volume
      • EFS File System ID: Select the EFS file system created in the Create EFS volume section
      • Root directory: /
    • Configure the Container mount points as shown below:
      • Container- Choose appsmith
      • Source volume- Choose appsmith
      • Container path- add the path as /appsmith-stacks

Do not share the EFS across ECS services, as doing so will cause Appsmith services to crash.

  1. Keep the default settings for all other sections, and click the Create button to create the task definition.

Create and run ECS service

  1. Navigate to the Clusters dashboard in the ECS section and select your cluster.
  2. Under the Services tab, click the Create button.
  3. Configure the Environment section with the following settings:
    • Compute options- select option as Launch type
    • Launch type- select EC2 from the dropdown
  4. Configure the Deployment configuration section with the following settings:
    • Application type- Select Service
    • Set up the Task definition as follows:
      • Family- Choose the task definition you created in the Create task and container definition section
      • Revision- Keep the default selection
      • Service name- Give a meaningful name to the service. For example, appsmith-ecs-ec2-cluster-service
      • Service type- Choose DAEMON
  5. Keep the default setting for all other sections, and click the Create button to create a service. It will take about five minutes for Appsmith to be up and running. The Last status shown as Running means that the service is up and running.

Verify Appsmith installation

  1. Select your cluster from the Clusters section, and open the Tasks tab
  2. Locate the relevant task and click its EC2 instance id
  3. Click the Open address link available next to the Public IP field to access Appsmith
Use DNS or Public IP to access Appsmith.
Use Public IP to access Appsmith
  1. Fill in your details to create an administrator account
  2. Once you've created an account, you can either start with the free plan or activate your instance with a license key. If you want to generate a license key, sign up on to create one, and then proceed to activate your instance using the newly generated license key.

Install Appsmith Community

For the Appsmith open source edition (Appsmith Community), substitute appsmith/appsmith-ee with appsmith/appsmith-ce in the container definition for Container-1 in the Create task and container definition section on this page.


If you are facing issues during deployment, refer to the guide on troubleshooting deployment errors. If you continue to face issues, reach out to the support team via the chat widget on this page.

Further reading