<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>aws on Devops Diary</title><link>/categories/aws/</link><description>Recent content in aws on Devops Diary</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 09 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="/categories/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Elasticsearch snapshots at S3</title><link>/tech/s3-elasticsearch-snapshots/</link><pubDate>Tue, 09 Feb 2021 00:00:00 +0000</pubDate><guid>/tech/s3-elasticsearch-snapshots/</guid><description>We use elasticsearch for a lot of purposes within our organisation, and thanks to kibana, we sometimes also use elasticsearch to store some data that isn&amp;rsquo;t necessarily timeseries data, but just nosql data that we want to visualize. We had a business requirement of having multiple backups for one of these types of data. So, we decided to have a dump of these indices once everyday and store it in an Amazon S3 bucket, in case the worst should happen.</description></item><item><title>Logging at Scale - Part 2</title><link>/tech/logging-at-scale-2/</link><pubDate>Fri, 12 Jun 2020 00:00:00 +0000</pubDate><guid>/tech/logging-at-scale-2/</guid><description>Continuing from the last post where we created a logging pipeline for storing and visualizing access logs in realtime, we faced some further issues with the said pipeline. In this post, I&amp;rsquo;ll try to build on that and get rid of some of these issues.
An expected unexpected problem With the increase in number of requests during spikes in traffic, we were running quite a few instances. And that&amp;rsquo;s when we first encountered the AWS API request throttling.</description></item><item><title>Logging at Scale - Part 1</title><link>/tech/logging-at-scale/</link><pubDate>Fri, 08 May 2020 00:00:00 +0000</pubDate><guid>/tech/logging-at-scale/</guid><description>So I work for an Ad-Tech company, and in this industry we receive a huge volume and rate of requests. At our peak, we serve around 35,000 requests per second, which is actually a bigger number than you initially realize.
Over the past 2 years, our business has seen an exponential growth in the amount of requests we serve and the infrastructure we handle. When I joined 2 years back, we were serving like 400-500 qps and handled like 20 servers for different purposes.</description></item><item><title>All about DHCP Servers</title><link>/tech/setup-own-dhcp/</link><pubDate>Sun, 03 May 2020 00:00:00 +0000</pubDate><guid>/tech/setup-own-dhcp/</guid><description>On a network with a large number of clients, DHCP is a must for dynamically assigning IP addresses to all the connected clients in order to avoid address conflicts and automating other required configurations like subnet mask, default gateway, DNS servers etc. Nowadays, almost all of the routers, even the smaller home routers already have an inbuilt DHCP server within the router that assigns IP addresses to connected clients. Still, why not learn how to set up one for yourself?</description></item><item><title>Self Hosting my blog - Part 2</title><link>/tech/blog-setup-part-2/</link><pubDate>Thu, 16 Apr 2020 00:00:00 +0000</pubDate><guid>/tech/blog-setup-part-2/</guid><description>So, in the last post, we finished setting up the infrastructure for our blog. In this post, we&amp;rsquo;ll deploy our blog to our server and make our blog live!
The idea here would be to do all this within the User Data Script, which is executed when the EC2 instance is initializing. We&amp;rsquo;ll write a shell script with all the required commands and run it with the User data script. Here are the things that need to be done to make our blog live:</description></item><item><title>Self Hosting my blog - Part 1</title><link>/tech/blog-setup-part-1/</link><pubDate>Wed, 08 Apr 2020 00:00:00 +0000</pubDate><guid>/tech/blog-setup-part-1/</guid><description>So, after a long time and a very little deliberation, I finally decided to stop using Google Blogger and move to a &amp;ldquo;self-hosted&amp;rdquo; soultion. The idea was to setup most of the things from scratch and have much more control over my own blog. So, I decided to give &amp;ldquo;static site generators&amp;rdquo; a try. I looked at a few different static site generators and in the end decided to go with Hugo, because it was version controlled, fast, secure, easy to understand and had good flexibilty in terms its functionality (not to mention a lot of themes to go with it).</description></item><item><title>Setting up a VPN Server</title><link>/tech/setup-own-vpn/</link><pubDate>Thu, 06 Feb 2020 00:00:00 +0000</pubDate><guid>/tech/setup-own-vpn/</guid><description>VPN services are pretty popular these days. As days pass, more and more people are starting to use VPN services. There are a lot of benefits for using VPNs, some of them being:
Protection from snooping on public networks (like public WiFi hostspots etc.) Bypass geographic restrictions on websites. Access blocked websites and services. Hide your internet activity from your ISP. Avoid network throttling (in some cases) and so much more&amp;hellip;.</description></item></channel></rss>