<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kinesis on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/kinesis/</link><description>Recent content in Kinesis on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 12 Sep 2018 18:52:59 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/kinesis/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS EKK Log System Setup: Elasticsearch + Kinesis + Kibana Hands-On Guide</title><link>http://www.heyuan110.com/posts/elasticsearch/2018-09-12-log-ekk/</link><pubDate>Wed, 12 Sep 2018 18:52:59 +0800</pubDate><guid>http://www.heyuan110.com/posts/elasticsearch/2018-09-12-log-ekk/</guid><description>&lt;p&gt;EKK is a log collection stack built entirely on AWS managed services: &lt;strong&gt;Amazon Elasticsearch Service&lt;/strong&gt;, &lt;strong&gt;Amazon Kinesis&lt;/strong&gt;, and &lt;strong&gt;Kibana&lt;/strong&gt;. Compared to a self-managed ELK stack, EKK is significantly easier to set up and maintain since AWS handles the infrastructure. Here is the basic architecture:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://d2908q01vomqb2.cloudfront.net/472b07b9fcf2c2451e8781e944bf5f77cd8457c8/2017/09/07/1-2.png"
 alt="EKK Architecture"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 
 
/&gt;
&lt;/p&gt;
&lt;p&gt;This guide focuses on the practical aspects of collecting Nginx logs and getting them into Elasticsearch with the correct field mappings, rather than covering every AWS console click.&lt;/p&gt;</description></item></channel></rss>