--- title: Charmhub | Deploy Apache Kafka Connect using Charmhub - The Open Operator Collection description: Deploy the latest version of Apache Kafka Connect on any cloud. url: https://charmhub.io/kafka-connect/docs/h-deploy-aws --- # Apache Kafka Connect [Canonical](https://charmhub.io/publisher/data-platform "View all packages from Canonical") * [Canonical](https://charmhub.io/publisher/data-platform "View all packages from Canonical") Platform: 24.04 22.04 4/stable 37 ``` juju deploy kafka-connect --channel 4/stable ``` [Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications) --- #### Relevant links * [Homepage](https://github.com/canonical/kafka-connect-operator) --- #### Contacts ##### Maintainers + [Canonical Data Platform](mailto:data-platform@lists.launchpad.net) * [Submit a bug](https://github.com/canonical/kafka-connect-operator/issues) --- Share your thoughts on this charm with the community on discourse. [Join the discussion](https://discourse.charmhub.io/) # How to deploy on AWS [Amazon Web Services](https://aws.amazon.com/) is a popular subsidiary of Amazon that provides on-demand cloud computing platforms on a metered pay-as-you-go basis. Access the AWS web console at [console.aws.amazon.com](https://console.aws.amazon.com/). ## [Summary](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-summary) * [Install AWS and Juju tooling](https://charmhub.io/kafka-connect/docs/h-deploy-aws#install-aws-and-juju-tooling) + [Authenticate](https://charmhub.io/kafka-connect/docs/h-deploy-aws#authenticate) * [Bootstrap Juju controller on AWS EC2](https://charmhub.io/kafka-connect/docs/h-deploy-aws#bootstrap-juju-controller-on-aws-ec2) * [Deploy charms](https://charmhub.io/kafka-connect/docs/h-deploy-aws#deploy-charms) * [Clean up](https://charmhub.io/kafka-connect/docs/h-deploy-aws#clean-up) --- ## [Install AWS and Juju tooling](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-install-aws-and-juju-tooling) Install Juju via snap: ``` sudo snap install juju --channel 3.5/stable ``` Follow the [AWS documentation](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) for guidance on how to install the Amazon Web Services CLI. To check whether both Juju and AWS CLI are correctly installed, run commands to display their versions: ``` juju version aws --version ``` Output example ``` 3.5.4-genericlinux-amd64 aws-cli/2.13.25 Python/3.11.5 Linux/6.2.0-33-generic exe/x86_64.ubuntu.23 prompt/off ``` ### [Authenticate](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-authenticate) [Create an IAM account](https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html) or use legacy user access keys and secret key to operate AWS EC2: ``` mkdir -p ~/.aws && cat <<- EOF > ~/.aws/credentials.yaml credentials: aws: NAME_OF_YOUR_CREDENTIAL: auth-type: access-key access-key: SECRET_ACCESS_KEY_ID secret-key: SECRET_ACCESS_KEY_VALUE EOF ``` ## [Bootstrap Juju controller on AWS EC2](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-bootstrap-juju-controller-on-aws-ec2) Add AWS credentials to Juju: ``` juju add-credential aws -f ~/.aws/credentials.yaml ``` Bootstrap Juju controller ([check all supported configuration options](https://juju.is/docs/juju/amazon-ec2)): ``` juju bootstrap aws ``` Output example ``` Creating Juju controller "aws-us-east-1" on aws/us-east-1 Looking for packaged Juju agent version 3.5.4 for amd64 Located Juju agent version 3.5.4-ubuntu-amd64 at https://juju-dist-aws.s3.amazonaws.com/agents/agent/3.5.4/juju-3.5.4-linux-amd64.tgz Launching controller instance(s) on aws/us-east-1... - i-0f4615983d113166d (arch=amd64 mem=8G cores=2) Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 54.226.221.6:22 Attempting to connect to 172.31.20.34:22 Connected to 54.226.221.6 Running machine configuration script... Bootstrap agent now started Contacting Juju controller at 54.226.221.6 to verify accessibility... Bootstrap complete, controller "aws-us-east-1" is now available Controller machines are in the "controller" model Now you can run juju add-model to create a new model to deploy workloads. ``` ## [Deploy charms](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-deploy-charms) Create a new Juju model, if needed: ``` juju add-model ``` (Optional) Increase the debug level if you are troubleshooting charms: ``` juju model-config logging-config='=INFO;unit=DEBUG' ``` Deploy and integrate Kafka and ZooKeeper: ``` juju deploy zookeeper -n3 --channel 3/stable [--constraints "instance-type="] juju deploy kafka -n3 --channel 3/stable [--constraints "instance-type="] juju integrate kafka zookeeper ``` The smallest AWS instance types may not provide sufficient resources to host an Apache Kafka broker. We recommend choosing an instance type with a minimum of `8` GB of RAM and `4` CPU cores, such as `m7i.xlarge`. For more guidance on sizing production environments, see the [Requirements page](https://charmhub.io/kafka-connect/docs/r-requirements). Additional information about AWS instance types is available in the [AWS documentation](https://us-east-1.console.aws.amazon.com/ec2/home?region=us-east-1#Instances:instanceState=running). We also recommend to deploy a [Data Integrator](https://charmhub.io/data-integrator) for creating an admin user to manage the content of the Kafka cluster: ``` juju deploy data-integrator admin \ --config extra-user-roles=admin \ --config topic-name=admin-topic ``` And integrate it with the Kafka application: ``` juju integrate kafka admin ``` For more information on Data Integrator and how to use it, please refer to the [how-to manage applications](https://charmhub.io/kafka-connect/docs/h-manage-app) guide. ## [Clean up](https://charmhub.io/kafka-connect/docs/h-deploy-aws#p-34315-clean-up) Always clean AWS resources that are no longer necessary! Abandoned resources are tricky to detect and they can become expensive over time. To list all controllers that have been registered to your local client, use the `juju controllers` command. To destroy the Juju controller and remove AWS instance (**Warning**: all your data will be permanently deleted): ``` juju destroy-controller --destroy-all-models --destroy-storage --force ``` Should the destroying process take a long time or be seemingly stuck, proceed to delete EC2 resources also manually via the AWS portal. See [Amazon AWS documentation](https://repost.aws/knowledge-center/terminate-resources-account-closure) for more information on how to remove active resources no longer needed. After destroying the controller, check and manually delete all unnecessary AWS EC2 instances, to show the list of all your EC2 instances run the following command (make sure to use the correct region): ``` aws ec2 describe-instances --region us-east-1 --query "Reservations[].Instances[*].{InstanceType: InstanceType, InstanceId: InstanceId, State: State.Name}" --output table ``` Output example ``` ------------------------------------------------------- | DescribeInstances | +---------------------+----------------+--------------+ | InstanceId | InstanceType | State | +---------------------+----------------+--------------+ | i-0f374435695ffc54c| m7i.xlarge | terminated | | i-0e1e8279f6b2a08e0| m7i.xlarge | terminated | | i-061e0d10d36c8cffe| m7i.xlarge | terminated | | i-0f4615983d113166d| m7i.xlarge | terminated | +---------------------+----------------+--------------+ ``` List your Juju credentials with the `juju credentials` command: ``` ... Client Credentials: Cloud Credentials aws NAME_OF_YOUR_CREDENTIAL ... ``` Remove AWS EC2 CLI credentials from Juju: ``` juju remove-credential aws NAME_OF_YOUR_CREDENTIAL ``` Finally, remove AWS CLI user credentials (to avoid forgetting and leaking): ``` rm -f ~/.aws/credentials.yaml ``` ---