<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Itamar Yerushalmi on Medium]]></title>
        <description><![CDATA[Stories by Itamar Yerushalmi on Medium]]></description>
        <link>https://medium.com/@itamar_68092?source=rss-7b9b412e7544------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dy1dNn-dFyZuIJANKch8KQ.jpeg</url>
            <title>Stories by Itamar Yerushalmi on Medium</title>
            <link>https://medium.com/@itamar_68092?source=rss-7b9b412e7544------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:14:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itamar_68092/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ELK6.x on Centos7.x — Quick install]]></title>
            <link>https://medium.com/talking-tech-all-around/elk6-x-on-centos7-x-quick-install-219dd0a97065?source=rss-7b9b412e7544------2</link>
            <guid isPermaLink="false">https://medium.com/p/219dd0a97065</guid>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[elk]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Itamar Yerushalmi]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 09:44:31 GMT</pubDate>
            <atom:updated>2018-01-29T10:57:32.669Z</atom:updated>
            <content:encoded><![CDATA[<p>How many times did you want to to install something for testing something specific. “Let’s do it quick manually , i won’t need it more then this time” is something i always negotiate with myself . As part of working a-lot with ELK i come across with this question a-lot. This time i was looking for a fast way to install one node -ELK6 for Centos/RHEL 7.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*vEb40HRegQgqJvz7Qz8zZg.png" /></figure><p>Instead of doing the work myself i started to look for something on the web but there are a lot of out dated playbooks online and github has become a graveyard for not-operational stuff .I have based my playbook on<a href="https://github.com/bingoarun/ansible-elk"> Arun’s Prasath</a> one but did some minor changes to fit the ELK 6.x . The playbook is written as a role — so you can use it in your <strong>Ansible CM.</strong></p><p><strong>You can find it here:</strong></p><p><a href="https://github.com/skywiz-io/Ansible-ELK">skywiz-io/Ansible-ELK</a></p><p>I’ll be posting a second part on “Cluster mode” as well in the next weeks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=219dd0a97065" width="1" height="1" alt=""><hr><p><a href="https://medium.com/talking-tech-all-around/elk6-x-on-centos7-x-quick-install-219dd0a97065">ELK6.x on Centos7.x — Quick install</a> was originally published in <a href="https://medium.com/talking-tech-all-around">Talking Tech Around</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kafka Multi-Tenancy Architecture: SSL client authentication]]></title>
            <link>https://medium.com/talking-tech-all-around/how-to-enable-and-verify-client-authentication-in-kafka-21e936e670e8?source=rss-7b9b412e7544------2</link>
            <guid isPermaLink="false">https://medium.com/p/21e936e670e8</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[pki]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[ssl-certificate]]></category>
            <dc:creator><![CDATA[Itamar Yerushalmi]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 16:25:49 GMT</pubDate>
            <atom:updated>2018-03-01T14:32:51.712Z</atom:updated>
            <content:encoded><![CDATA[<p>Kafka is a distributed streaming platform. As such, we would want many consumers and producers to write to the same Kafka cluster.</p><p>In one of our latest projects in a large scale cyber-security company, we created a large scale deployment of a Kafka cluster that needed to serve approximately 10TB of digested data each day, split across over 100 million events. This was done in order to limit each customer’s ability to access only their topic in a multi-tenancy architecture.</p><blockquote>There are a few guides over the internet to enable SSL client authentication on Kafka. Some of them are outdated or incomplete, while the others include overkill Kerberos implementation. So I created this one, which is based on Kafka’s official documentation at this <a href="http://kafka.apache.org/documentation.html#security_ssl">link</a>, hopefully you’ll find it useful.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkUDyya838QHOrxY7cGglg.jpeg" /><figcaption>Producer can write to all topics. Consumer can access secured topic only with right certificate.</figcaption></figure><p><strong>For this example, I have one Kafka server and 2 clients (consumers).</strong></p><p>Server Side:</p><p>Make sure that you have truststore and keystore JKSs for each server.</p><ol><li>In case you want a self signed certificate, you can use the following commands:</li></ol><pre>export PASSWORD=password</pre><pre>keytool -keystore kafka.server.keystore.jks -alias localhost -validity 365 -genkey</pre><pre>openssl req -new -x509 -keyout ca-key -out ca-cert -days 365</pre><pre>keytool -keystore kafka.server.truststore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.client1.truststore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.client2.truststore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.server.keystore.jks -alias localhost -certreq -file cert-file</pre><pre>openssl x509 -req -CA ca-cert -CAkey ca-key -in cert-file -out cert-signed -days 365 -CAcreateserial -passin pass:$PASSWORD</pre><pre>keytool -keystore kafka.server.keystore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.server.keystore.jks -alias localhost -import -file cert-signed</pre><pre>keytool -keystore kafka.client1.keystore.jks -alias localhost -validity 365 -genkey</pre><blockquote>Make sure that you configure the certificate properly — this will be used later in the ACL configuration.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ccmX5gp_Hs2Q9oQnDduDzQ.png" /></figure><pre>keytool -keystore kafka.client1.keystore.jks -alias localhost -certreq -file cert-file</pre><pre>openssl x509 -req -CA ca-cert -CAkey ca-key -in cert-file -out cert-signed -days 365 -CAcreateserial -passin pass:$PASSWORD</pre><pre>keytool -keystore kafka.client1.keystore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.client1.keystore.jks -alias localhost -import -file cert-signed</pre><pre>keytool -keystore kafka.client2.keystore.jks -alias localhost -validity 365 -genkey</pre><pre>keytool -keystore kafka.client2.keystore.jks -alias localhost -certreq -file cert-file</pre><pre>openssl x509 -req -CA ca-cert -CAkey ca-key -in cert-file -out cert-signed -days 365 -CAcreateserial -passin pass:$PASSWORD</pre><pre>keytool -keystore kafka.client2.keystore.jks -alias CARoot -import -file ca-cert</pre><pre>keytool -keystore kafka.client2.keystore.jks -alias localhost -import -file cert-signed</pre><p>2. On Kafka servers — <strong>server.properties</strong> — add the following lines:</p><pre>ssl.enabled.protocols=TLSv1.2,TLSv1.1,TLSv1</pre><pre>ssl.endpoint.identification.algorithm=HTTPS</pre><pre>ssl.keymanager.algorithm=SunX509</pre><pre>ssl.keystore.location=/PATH-TO/kafka.server.keystore.jks</pre><pre>ssl.keystore.password=password</pre><pre>ssl.keystore.type=JKS</pre><pre>ssl.protocol=TLS</pre><pre>ssl.trustmanager.algorithm=PKIX</pre><pre>ssl.truststore.location=/PATH-TO/kafka.server.truststore.jks</pre><pre>ssl.truststore.password=password</pre><pre>ssl.truststore.type=JKS</pre><pre>authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer</pre><pre>allow.everyone.if.no.acl.found=true</pre><p>3. Add the following to the <strong>advertised.listeners</strong> and the listeners keys SSL values on port 9092:</p><pre>advertised.listeners=PLAINTEXT://KAFKA_IP:9092,SSL://KAFKA_IP:9093</pre><pre>listeners=PLAINTEXT://KAFKA_IP:9092,SSL://KAFKA_IP:9093</pre><p>4. Change</p><pre>ssl.client.auth=none</pre><p>To</p><pre>ssl.client.auth=required</pre><p>5. For logging — enable DEBUG on Kafka authentication by changing the line in <strong>log4j.properties —</strong></p><p>From:</p><pre>log4j.logger.kafka.authorizer.logger=WARN, authorizerAppender</pre><p>To:</p><pre>log4j.logger.kafka.authorizer.logger=DEBUG, authorizerAppender</pre><p>6. On the client servers add the following lines to<strong> consumer.properties</strong> and <strong>producer.properties</strong>:</p><pre>security.protocol=SSL</pre><pre>ssl.truststore.location=/PATH-TO/ssl/kafka.client1.truststore.jks</pre><pre>ssl.truststore.password=password</pre><pre>ssl.keystore.location=/PATH-TO/kafka.client1.keystore.jks</pre><pre>ssl.keystore.password=password</pre><pre>ssl.key.password=password</pre><p>Notice that you are using different files for the different servers.</p><p>7. Produce messages to a new topic:</p><pre>./bin/kafka-console-producer.sh — broker-list KAFKA_IP:9093 — topic secured-topic — producer.config /opt/kafka/config/producer.properties</pre><pre>&gt;1</pre><pre>CTRL+D</pre><p>You should now be able to write to the topic from both servers — if you look at the <strong>kafka-authorizer.log</strong> on the server you will see the following messages:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3Vi8Q2dJZMp0Bn41Ty9kA.png" /></figure><p>8. Using the kafka-acl command — set permissions for one of the users — by default, it will remove permissions from the other user:</p><pre>bin/kafka-acls.sh — authorizer kafka.security.auth.SimpleAclAuthorizer — authorizer-properties zookeeper.connect=ZOOKEEPER_IP:2181 — add — allow-principal User:”CN=client1,OU=1,O=1,L=1,ST=1,C=1&quot; — operation Write — operation Read — operation Describe — topic secured-topic</pre><p>9. Now, if you try to write or read from the granted user, you will succeed —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-z0z75zhge5dfRHcefPaog.png" /></figure><p>and from the other user — permission denied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7hd8E50pU5myRF1toK4tow.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21e936e670e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/talking-tech-all-around/how-to-enable-and-verify-client-authentication-in-kafka-21e936e670e8">Kafka Multi-Tenancy Architecture: SSL client authentication</a> was originally published in <a href="https://medium.com/talking-tech-all-around">Talking Tech Around</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>