# Deploy Conduktor Console on AWS with CloudFormation in 10 Minutes

## Why Use a Kafka Console

Managing Kafka clusters through CLIs and scattered APIs wastes time. A console gives you topic configs, consumer lag, and data inspection in one place.

Conduktor works with Confluent, AWS MSK, Redpanda, and any Kafka-compatible provider. It supports Confluent Schema Registry, AWS Glue, Kafka Connect, and ksqlDB.

This guide walks you through deploying Conduktor on ECS using CloudFormation. The whole process takes a few clicks. For Kubernetes, use the [Helm chart](https://docs.conduktor.io/platform/get-started/installation/get-started/kubernetes/).

[GIF not supported - Claudiu to reupload Video]

## Architecture Overview

The CloudFormation template deploys:

- An RDS instance for metadata (user preferences, tags, permissions)
- Conduktor Console on ECS Fargate
- A public IP by default (configurable for private access)

![AWS architecture diagram: Conduktor Console deployed via CloudFormation on ECS Fargate with RDS metadata storage and a public IP](https://www.conduktor.io/assets/images/blog/aws-cloudformation-architecture-overview.png)

## Deployment Steps

*This guide gets you started. Review the [production requirements](https://docs.conduktor.io/platform/get-started/installation/hardware/#production-requirements) before deploying to production.*

1. Go to [AWS CloudFormation](https://aws.amazon.com/cloudformation/getting-started/)

2. Choose a template:
   - [Full template](https://github.com/conduktor/quickstart-conduktor-cloudformation/blob/main/templates/CDK-full-template.yaml): Deploys Conduktor and all required infrastructure
   - [Lite template](https://github.com/conduktor/quickstart-conduktor-cloudformation/blob/main/templates/CDK-lite-template.yaml): Deploys Conduktor on existing ECS cluster and RDS

![AWS CloudFormation template selection screen for the full and lite Conduktor stacks](https://www.conduktor.io/assets/images/blog/aws-cloudformation-template-selection.png)

3. Wait 5-10 minutes for the stack to complete

4. Navigate to Cluster > Service > Task > Conduktor Console > Network Bindings and click the address

![AWS ECS task screen showing the Conduktor Console network bindings to reach the running console](https://www.conduktor.io/assets/images/blog/aws-ecs-task-network-bindings-conduktor.png)

## Configure Your Kafka Cluster

Add your first cluster:

![Conduktor Console UI: Add Cluster screen with name and bootstrap server fields](https://www.conduktor.io/assets/images/blog/conduktor-aws-add-cluster-screen.png)

Enter your bootstrap server and authentication details. If you use Schema Registry, Kafka Connect, or ksqlDB, add those in the corresponding tabs:

![Conduktor Console cluster configuration: bootstrap server, authentication and tabs for Schema Registry, Kafka Connect and ksqlDB](https://www.conduktor.io/assets/images/blog/conduktor-aws-cluster-bootstrap-config.png)

## Add Your Team

Invite users from the Users & Groups screen. Conduktor supports SSO (LDAP, OIDC) or basic authentication:

![Conduktor Console Users and Groups screen with SSO (LDAP, OIDC) and basic auth options](https://www.conduktor.io/assets/images/blog/conduktor-aws-users-groups-sso.png)

## Next Steps

You now have Conduktor Console running on AWS. Browse topics, manage consumer groups, inspect schemas, and monitor connectors.

See the [documentation](https://docs.conduktor.io/platform/get-started/installation/get-started/CloudFormation/) for detailed configuration. Other deployment options: [Docker](https://docs.conduktor.io/platform/get-started/installation/get-started/docker/), [Helm](https://docs.conduktor.io/platform/get-started/installation/get-started/kubernetes/).