<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Lambda - Tag - Filipe Felisbino</title><link>https://felisbino.dev/tags/lambda/</link><description>Lambda - Tag - Filipe Felisbino</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 06 Aug 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://felisbino.dev/tags/lambda/" rel="self" type="application/rss+xml"/><item><title>AWS custom-crafted load balancer with haproxy</title><link>https://felisbino.dev/posts/aws-load-balancer/</link><pubDate>Sat, 06 Aug 2016 00:00:00 +0000</pubDate><author>Filipe Felisbino</author><guid>https://felisbino.dev/posts/aws-load-balancer/</guid><description><![CDATA[<p>Today&rsquo;s tip is on how to launch a custom-crafted load balancer on AWS as a replacement for ELBs.</p>
<h2 id="motivation">Motivation</h2>
<p>First of all I need to say that I love AWS&rsquo; ELB. It is cost-effective and works just fine for most of the cases.</p>
<p>So why would I create a custom-crafted ELB? Well, there are some features that AWS&rsquo; ELB just don&rsquo;t support. Things like:</p>
<ul>
<li>A static IP or elastic IP entry point</li>
<li>UDP load balancing</li>
<li>Customized balancing strategy</li>
<li>Custom backend routing</li>
<li>One load balancer for multiple backends</li>
<li>SNI resolution(SSL routing)</li>
</ul>
<p>So if the ELB is not suited for your use case, do it yourself :-)</p>]]></description></item></channel></rss>