Search This Blog

Confluent Single Node - AWS Linux Daemon script

I've been working with Confluent lately & noticed that Confluent Version 4
doesn't have systemV or systemD scripts which allow the service to autostart as a daemon on the host OS. I asked about these scripts in the Confluent Community slack channel & a member politely responded that these daemon scripts will be available in Confluent Version 4.1 & at the moment I would have to roll my own.

I have created a very simple Confluent systemV script that has been tested & works on AWS Linux.

Important: This script is designed for a a Single Node/Sandbox installation of Confluent and should not be used in Production deployments. I'll follow-up with another blog that'll address all of the Confluent services in individual systemV scripts which can be used in distributed deployments.

So here is my simple AWS Linux systemV script for those who need it but obviously you need to install the Confluent platform (Use the RHEL/CentOS 6.8 repository for AWS Linux) on your AWS Linux instance.

# Create the daemon file on the host server

$ sudo touch /etc/init.d/confluent.d

# Make it executable

$ sudo chmod +x /etc/init.d/confluent.d

# Open the confluentd file in vi, vim, nano or your text editor of choice

$ sudo nano /etc/init.d/confluentd

# Paste the following script into the confluentd file and save it on the server

Now you have a systemV script to start, stop & auto start the very cool Confluent services.

Remember that this is only recommended for a development or single node/sandbox deployment & should not be used in Production environments. I'll be following up with another blog that will address Production systemV scripts on AWS Linux instances.

If you need a systemD script you're gonna have to roll your own but ping me if you'd like some help.

Post a Comment

Popular Posts

I recently worked on a project where I had to develop a solution that can
interact with instances of IBM's FileNet P8 and installing FileNet was an utter nightmare. Throughout the years I have encountered & used IBM solutions and systems in many capacities but I can honestly say this was the worst experience I ever had with an IBM solution.

The project has a really tight deadline and my time to hack a solution was very short. Upon procuring the FileNet software I first had to spend about 2 hours on the IBM Passport site which is where I had to hunt down all 11 install packages that clock in at over 10 GB compressed. The IBM Passport site is not user friendly at all you'll probably spend a few minutes figuring out how to find the packages that you need. I just ran searches in the "Find By" name for each install package. Be sure to download the proper packages for your particular OS.

After I had all of the files I began the Windows Server 2008 installation using…

So it's been kinda fun watching people freak out about the Heartbleed vulnerability this week. What I don't find so funny & kinda scary is that this vulnerability has been in the wild since December 2011 and people are learning about this over two years later.

In any case my social media feeds are being flooded by people asking how to mitigate this vulnerability. This post will outline how to patch some of the most popular affected distributions by running commands in Terminals:

Mac OSX: $ brew upgrade openssl

Red Hat: $ sudo yum update openssl

Centos: $ sudo yum update openssl

Fedora: $ sudo yum update openssl

Amazon Linux AMI: $ sudo yum update openssl

Debian: $ sudo apt-get update && sudo apt-get upgrade

Ubuntu: $ sudo apt-get update && sudo apt-get upgrade

#! Linux: $ sudo apt-get update && sudo apt-get upgrade

So people please patch your servers and take other measures as recommended per your distro's security bulltetins.