Install on AWS (Deprecated)
Install on AWS
The following AWS Marketplace Image is no longer available. We are working on updating the instructions.
Squidex is available in the AWS Marketplace as a listing. To begin, click the Deploy to AWS button below.
Squidex is free, but you still need to subscribe to the Amazon Marketplace listing.
In the listing page, click Continue to Subscribe (1).
Subscribe to AWS marketplace listing
Read the EULA and accept the terms by clicking Accept Terms (2).
Accept terms to subscribe to the listing
Wait until AWS processes your subscription (3).
Subscription being processed by AWS
Once that is ready, click Continue to Configuration (1).
Continue to Configuration
Pick a Delivery Method (1), a Software Version (2) and a Region (3), then click Continue to Launch (4).
Choose a software configuration
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.
Choose an instance type
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.
Choose network configuration and security group
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.
Select key pair and launch
Once the instance is launched, go to the EC2 Console (11).
EC2 instance successfully deployed
Once the instance is ready, take its Public IPv4 (1) and connect to it using SSH and the key pair you selected previously.
Retrieve Public IP
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.
For other issues, it is likely that you have a configuration problem not related to hosting under Docker. Checkout the following documentation: