DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • End-to-End Event Streaming With Kafka, Spring Boot and AWS SQS/SNS (Production-Ready Code Guide)
  • Securing and Monitoring Your Data Pipeline: Best Practices for Kafka, AWS RDS, Lambda, and API Gateway Integration
  • A Comparative Analysis: AWS Kinesis vs Amazon Managed Streaming for Kafka - MSK
  • Designing High Performant Responsive Web Application With AWS Services and Finetuning for Performance

Trending

  • Introduction to Tactical DDD With Java: Steps to Build Semantic Code
  • Building a DevOps-Ready Internal Developer Platform: A Hands-On Guide to Golden Paths, Self-Service, and Automated Delivery Pipelines
  • Rethinking Java CRUDs With Event Sourcing and CQRS Patterns
  • Why DDoS Protection Is an Architectural Decision for Developers
  1. DZone
  2. Coding
  3. Tools
  4. Install and Configure Confluent Platform (Kafka) in AWS EC2 Instance RHEL 8

Install and Configure Confluent Platform (Kafka) in AWS EC2 Instance RHEL 8

In this article, I'm gonna show you how to install and configure a self-manage Confluent Platform in the AWS EC2 instance.

By 
Enrico Rafols Dela Cruz user avatar
Enrico Rafols Dela Cruz
·
May. 22, 20 · Tutorial
Likes (2)
Comment
Save
Tweet
Share
12.3K Views

Join the DZone community and get the full member experience.

Join For Free

The Confluent Platform is a stream data platform that enables you to organize and manage massive amounts of data that arrive every second at the doorstep of a wide array of modern organizations in various industries, from retail, logistics, manufacturing, and financial services, to online social networking. 

It contains all the components you need to create a scalable data platform built around Apache Kafka and they offer both Managed Cloud and a Self-Managed Confluent Platform.

In this article, I'm gonna show you how to install and configure a self-manage Confluent Platform in the AWS EC2 instance.

Prerequisites

  • Redhat 8 Linux - EC2 Instance in AWS
    • Open JDK 8 installed
    • wget installed
  • SSH Client (I'm using Git Bash https://gitforwindows.org/)

Instructions

1. Make sure that the EC2 instance is up and running.

aws

2. To access the EC2 instance using Git bash as the SSH client, Execute the command ssh -i <PEM file> ec2-user@<Public DNS>

redhat

3. Make sure the OpenJDK 8 is installed, you can verify it using the command java -version.

If you don't have it, you can download and install by executing sudo yum install java-1.8.0-OpenJDK-devel

redhat-instance

4. Next, download and install the wget library in the RHEL box, we need this command to allow us to download the tar file of the Confluent Platform from the EC2 instance.

redhat instance

redhat instance

5. Go to https://www.confluent.io/download, download the Self-Managed Software

self-managed software

single kafka broker

6. Copy the download link from the Browser's Download Manager.

We will download the tar file using wget from the EC2 instance

EC2 instance

7.  Execute the command wget https://packages.confluent.io/archive/5.5/confluent-5.5.0-2.12.tar.gz in the Root directory to download the source.

Run the ls command once the download the completed, you should see the confluent-5.5.0-2.12.tar.gz file

redhat instance

8. Extract the confluent-5.5.0-2.12.tar.gz  by executing the command tar-xvzf confluent-5.5.0-2.12.tar.gz

redhat instance

9. Once we have the confluent platform source extracted in the root directory, we need to create a new environment variable CONFLUENT_HOME and add it to the environment PATH variable. 

Execute the below command:

export CONFLUENT_HOME=<path-to-confluent>

export PATH=$PATH:$CONFLUENT_HOME/bin

root@ip

10. Start the services by executing the confluent local start

To check the status, run the confluent local status

root@ip

root@ip

11. Before we can access the Confluent Control Center, we need to make sure that a Custom TCP for port 9021 is added in the Security Group as inbound rules of the AWS EC2 instance.

launch-wizard

12. Take note of the Public IP or the Public DNS, this will be the hostname when accessing the Confluent Control Center HTTP://<host name>:9021

confluent control

12. Open the Browser for HTTP://<Public IP>:9021

You should be able to access and view the Confluent Control Center

confluent overview

That's it. An easy to follow step if you are planning to install a self-managed Confluent Platform to your RHEL or CentOS box.

I hope this helps!

AWS kafka

Opinions expressed by DZone contributors are their own.

Related

  • End-to-End Event Streaming With Kafka, Spring Boot and AWS SQS/SNS (Production-Ready Code Guide)
  • Securing and Monitoring Your Data Pipeline: Best Practices for Kafka, AWS RDS, Lambda, and API Gateway Integration
  • A Comparative Analysis: AWS Kinesis vs Amazon Managed Streaming for Kafka - MSK
  • Designing High Performant Responsive Web Application With AWS Services and Finetuning for Performance

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook