Deployment on AWS CloudFormation
This guide will demonstrate how to use AWS CloudFormation to deploy Console in your AWS environment with all mandatory dependencies. It will deploy Conduktor as a Docker container on an ECS service with Fargate and configure it alongside a PostgreSQL database via RDS.
While this guide will help you get started, you may need to make additional configurations to ensure your deployment is production-ready.
The process should take no more than 15 - 30 minutes.
This template will create all the resources on a public subnet. However, the DB instance is available on private and public subnets. It is important to keep this in mind when using it.
Networking & Architecture
Click on "create stack" button and choose the "With new resources" option.
Choose the following options.
Upload one of our templates:
Decide if you want to deploy console using your own resources (cluster, DB, etc.) or if you want us to deploy all resource dependencies alongside console as well.
To deploy console only, you can use the following template:
To deploy console and all resources needed (e.g. DB), you can use the following template:
Give your stack a name and define/ review the parameters.
- If you have chosen the CDK-lite-template, then you will have to supply the following values before you can continue.
The ARN of the subnet you want to deploy your ECS service on.
The Security group that will have access to your ECS service.
The ARN of the cluster you want to deploy your ECS service on.
The endpoint of your DB instance.
The name of your DB instance.
The username for above DB instance.
The password for above DB instance.
- If you have chosen the CDK-Full-template, then you won't have to supply any parameter values, but you may override the default ones.
Note the default value for region is specified in the template as
eu-west-1a(public subnet) and
eu-west-1b(private subnet), if you are deploying in a different region you must update these values.
Acknowledge the tick box. This will ensure we have the right permissions to access our ECS instance!
Wait for all resources to be created. This may take some time!
From the "Resources" tab, click on
conduktor-ecsthen navigate to your newly created Service and then Task.
conduktor-consoleContainer and navigate to the Network bindings tab.
Click on the External link to open the Console application.
In our example, our application is running at 126.96.36.199:8080.
You can now log in as admin with the credentials previously defined in the environment variables: