1-Click deployment using CloudFormation


LOGIQ can be deployed on AWS in a single AMI instance in a 1-Click fashion using our CloudFormation template and the LOGIQ AMI from the Amazon Marketplace.

All the resources required to create and configure LOGIQ on AWS are taken care by the template. All you need to do is provide a few simple input parameters.

The CloudFormation template can be found below


Please note that using the Marketplace AMI is not free and you will be charged per the marketplace published rates for LOGIQ

Template parameters

The following parameters need to be provided for a successful deployment via the CloudFormation template

Stack name

AWS Resource configuration

The LOGIQ AMI is instantiated with an SSH key pair installed so a user can later connect to the AMI when required. In addition an S3 Bucket where the user data will be stored is required.

Optionally, the prefix for creating access control resources like a LOGIQ User and Role can be provided. For optional resources, we use defaults if none is provided. It is strongly advised that a unique prefix string be used if you plan on running multiple instances so as to keep the users and roles separate.

EC2 Instance configuration

The LOGIQ services are deployed in an EC2 instance in a specific region. The template asks you to select a region for deployment. You also need to select an appropriate instance size. By default an m5.xlarge instance is created if user does not change it.

A larger instance results in better performance. In addition, to secure your environment, it is strongly recommended that you provide a CIDR range for the clients that can connect to the LOGIQ server. This will be programmed in the security group created during the deployment.

Supported Regions

The CloudFormation template supports all AWS regions including Amazon GovCloud regions.

Default user and password

Once the LOGIQ instance is created, you can login to the instance using the below credentials

user: logiq@foo.com

password: <name of your CloudFormation stack>-<name of your S3 bucket>

e.g. if CloudFormation stack is called Foo and bucket is called Bar the password is Foo-Bar

TLS Client certificates

LOGIQ server exposes several protocols via secure ports. The client public/private certificate to connect to the server is available via SSH into the AMI. The below command illustrates ssh into LOGIQ server instance and print the certificate details

$ ssh -i ~/Downloads/logiqai.pem ubuntu@
$ sudo docker logs -f `sudo docker ps | grep quay.io/logiq/flash:rc.singlecontainer | awk '{ printf $1 }'