<?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 Ishwar Chandra on Medium]]></title>
        <description><![CDATA[Stories by Ishwar Chandra on Medium]]></description>
        <link>https://medium.com/@IshwarChandra?source=rss-16d4f1187247------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8k0T48BqxNkggKyb7Juy6A.jpeg</url>
            <title>Stories by Ishwar Chandra on Medium</title>
            <link>https://medium.com/@IshwarChandra?source=rss-16d4f1187247------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:06:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@IshwarChandra/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[How to Create a Simple Cassandra Cluster]]></title>
            <link>https://medium.com/@IshwarChandra/how-to-create-a-simple-cassandra-cluster-f09c9fde1087?source=rss-16d4f1187247------2</link>
            <guid isPermaLink="false">https://medium.com/p/f09c9fde1087</guid>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[cassandra]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ishwar Chandra]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 02:41:09 GMT</pubDate>
            <atom:updated>2019-07-30T02:41:09.758Z</atom:updated>
            <content:encoded><![CDATA[<p>Apache Cassandra is a free and open-source distributed wide column store NoSQL database management system designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. <a href="https://en.wikipedia.org/wiki/Apache_Cassandra">Wikipedia</a></p><p>Apache Cassandra is a high performance, extremely scalable, fault-tolerant (i.e. no single point of failure), distributed post-relational database solution. <em>Cassandra combines all the benefits of Google Bigtable and Amazon Dynamo to handle the types of database management needs that traditional RDBMS vendors cannot support</em>. (Source: DataStax).</p><h3>Why do we even need to self manage and run Apache Cassandra if we have Amazon Managed DynamoDB?</h3><p><em>Cassandra and DynamoDB both origin from the same paper:</em> <a href="http://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf">Dynamo: Amazon’s Highly Available Key-value store</a>. (By the way — it has been a very influential paper and set the foundations for several NoSQL databases).</p><p>Of course, it means that DynamoDB and Cassandra have a lot in common! (They have the same DNA). However, both AWS DynamoDB and Apache Cassandra have evolved quite a lot since this paper was written back in 2007 and there are now some key differences to be aware of when choosing between the two.</p><p>Both databases have their own advantages and disadvantages, you can choose the one that best matches your requirements. Read <a href="https://www.beyondthelines.net/databases/dynamodb-vs-cassandra/">here</a> in detail.</p><p>We were initially using DynamoDB. Our primary reason to switch from DynamoDB to Cassandra was the Total Cost of Ownership (TCO).</p><p>We have been able to reduce the cost to almost half what we were paying for DynamoDB.</p><p>Other benefits are: Cassandra is Open Source, it provides full active-active multi-region support, significantly lower latency than DynamoDB, etc.</p><p>Read detailed comparison over TCO of DynamoDB and Cassandra <a href="https://www.instaclustr.com/managed-cassandra-versus-dynamodb/">here</a>.</p><h3>Bootstrap the cluster:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6nff49tNbeAg-YGMLf4BKA.png" /></figure><p>Continue reading <a href="https://blog.avmconsulting.net/posts/2019-05-28-how-to-create-a-simple-cassandra-cluster-on-aws/">here</a>. Thank You.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f09c9fde1087" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to encrypt EBS volumes of a running EC2 instance?]]></title>
            <link>https://medium.com/@IshwarChandra/how-to-encrypt-ebs-volumes-of-a-running-ec2-instance-a2236b0b45?source=rss-16d4f1187247------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2236b0b45</guid>
            <category><![CDATA[encryption]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[ec2]]></category>
            <dc:creator><![CDATA[Ishwar Chandra]]></dc:creator>
            <pubDate>Tue, 26 Jun 2018 22:52:18 GMT</pubDate>
            <atom:updated>2019-07-31T15:34:43.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*e3lbJY6Osq88kHkJEyfLQg.jpeg" /></figure><p>Nowadays encryption of data at rest is a must, especially if it’s stored somewhere in public cloud. It’s necessary to meet various compliance requirements like PCI DSS.</p><p>We will use AWS KMS for encryption of EBS Volumes. AWS has default key for EBS volume encryption- aws/ebs, you can use this or create your own.</p><p><strong>Create KMS Key:</strong></p><p>Login to <a href="https://hackernoon.com/tagged/aws">AWS</a> Account and go to IAM, <a href="https://console.aws.amazon.com/iam/home?region=eu-central-1#/encryptionKeys/us-east-1"><strong>Encryption keys</strong></a><strong>, </strong>select <strong>region</strong> you want to use the key in and create a key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1tLy63BP723JSVzA6BLVA.png" /><figcaption>AWS IAM KMS Console</figcaption></figure><p>You will need to provide:<br>-<em>Alias Name (required), <br>-Tag (optional), <br>-IAM user who has Administrative Privilege over this particular key, <br>-IAM users and roles that can use this key to encrypt and decrypt data from within applications and when using AWS services integrated with KMS.</em></p><p>Now we have key ready to use for encryption, use below steps to complete the task:<br> 1. Stop your <a href="https://hackernoon.com/tagged/ec2">EC2</a> instance.<br> 2. Create an EBS snapshot of the volume you want to encrypt.<br> 3. Copy the EBS snapshot, encrypting the copy in the process using key created above.<br> 4. Create a new EBS volume from your new encrypted EBS snapshot. The new EBS volume will be encrypted.<br> 5. Detach the original EBS volume and attach your new encrypted EBS volume, making sure to match the device name (/dev/xvda1, etc.)<br>6. Start the EC2 instance.</p><p>Now you have an EC2 instance with Encrypted EBS Volumes. Please note that do not delete the KMS key in use. Deleting a key makes all data encrypted under that key unrecoverable.</p><p>That’s all. Thanks for reading :) Happy Cloud Computing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2236b0b45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Centralized Logging and Monitoring of a Distributed System and Application using ELK]]></title>
            <link>https://medium.com/@IshwarChandra/centralised-logging-and-monitoring-of-a-distributed-system-and-application-using-elk-57dc073cd22e?source=rss-16d4f1187247------2</link>
            <guid isPermaLink="false">https://medium.com/p/57dc073cd22e</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[kibana]]></category>
            <dc:creator><![CDATA[Ishwar Chandra]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 00:00:00 GMT</pubDate>
            <atom:updated>2019-07-01T06:12:50.205Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*JX0wHwci1khQwcSd" /></figure><p><strong>Introduction</strong></p><p>Nowadays, centralized logging and monitoring have become an integral part of our technology stack. It empowers organizations to gain important insights into operation, security, and infrastructure. We have different types of service-specific metrics and logs. Metrics and Log files from different distributed web servers, applications, and operating systems can be collected and used together with a centralized overview of useful insights.</p><p>We have some very popular SaaS-based logging and monitoring tools e.g. Datadog, Splunk, Loggly and many others.</p><p><strong>Implementation</strong></p><p>The ELK Stack is the most commonly used open source tool for this kind of purpose. Users can use their own ELK deployment or can use managed <a href="https://hackernoon.com/tagged/elasticsearch">ElasticSearch</a> service e.g. <a href="https://aws.amazon.com/elasticsearch-service/">Amazon ElasticSearch</a>, <a href="https://www.elastic.co/cloud">Elastic Cloud</a>.</p><p>ELK is used because it helps in aggregating log and audit data from the different sources, processing and enhancing this data (Logstash, Beats), storing them in one central data store (Elasticsearch), and providing analysis and visualization tools (<a href="https://hackernoon.com/tagged/kibana">Kibana</a>).</p><p>Let us consider we have a simple LAMP based application running on servers behind ELB on AWS and we want to collect OS metrics and Apache logs.</p><p>For ELK stack, we will consider AWS managed Amazon ElasticSearch which comes with pre-installed Kibana. While Logstash and Beats (Filebeat, Metricbeat, Packetbeat, Winlogbeat, Auditbeat, Heartbeat) would work as data shippers.</p><blockquote>“Beats is the platform for single-purpose data shippers. They install as lightweight agents and send data from hundreds or thousands of machines to Logstash or Elasticsearch.” Detailed information can be found</blockquote><p>Above architecture contains two Web servers running behind ELB which have Beats agents installed. All the required configuration is baked into an AMI (Amazon Machine Image). One can dynamically configure it using Amazon CloudFormation tools as well.</p><p>Beats collect logs and metrics, parse it, and send to Elasticsearch. Amazon Elasticsearch is configured in high-availability mode and also there isNGINX proxy server in front of Kibana.</p><p>The Complete Elasticsearch solution is inside Private Subnet since it’s intended to be used inside an organization. So Kibana is accessible through VPN. It further increases the security of logs and metrics.</p><h3>Conclusion</h3><p>Log Management and Analytics enable enterprises to collect, manage, and analyze log data in order to improve their application and infrastructure management and monitoring. ELK collects any log data in real-time and enables our customers to perform analytics such as application troubleshooting and root cause analysis, application monitoring, IT infrastructure monitoring and troubleshooting, and application analytics.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/logging-monitoring-distributed-system-application-using-chandra/"><em>https://www.linkedin.com</em></a><em> on January 8, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57dc073cd22e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>