Install on AWS (Deprecated)

Install on AWS

The following AWS Marketplace Image is no longer available. We are working on updating the instructions.

1. Use the AWS Marketplace Image

Squidex is available in the AWS Marketplace as a listing. To begin, click the Deploy to AWS button below.

2. Subscribe

Squidex is free, but you still need to subscribe to the Amazon Marketplace listing.

In the listing page, click Continue to Subscribe (1).

Read the EULA and accept the terms by clicking Accept Terms (2).

Wait until AWS processes your subscription (3).

Once that is ready, click Continue to Configuration (1).

3. Instance Configuration

Pick a Delivery Method (1), a Software Version (2) and a Region (3), then click Continue to Launch (4).

This will take you to the configuration of the EC2 instance to be launched.

Pick the EC2 Instance Type (5). We recommend at least a m5.large.

Scroll down and select a VPC (6) and Subnet (7) from the pre-populated list. Next, select a Security Group (8) or click Create New Based On Seller Settings to automatically create one based on Squidex requirements.

Finally, select a Key Pair (9) and click Launch (10).

You must have an AWS Key Pair and selected here, otherwise you will not be able to login to the EC2 instance later.

Once the instance is launched, go to the EC2 Console (11).

4. Connect

Once the instance is ready, take its Public IPv4 (1) and connect to it using SSH and the key pair you selected previously.

ssh -i path/to/keypair.pem ubuntu@[PUBLIC IP]

Once you are logged in, run the setup command and follow the on-screen instructions.


You will be asked to enter the domain here. All other values are optional. The installation script will start docker-compose, download all images and start them in the right order.

After you make sure the domain you configured is pointing to the public IP of your instance and that the DNS changes propagated, go to and you should be ready to go.

For further help, go to Configuration.


For other issues, it is likely that you have a configuration problem not related to hosting under Docker. Checkout the following documentation:


Last updated