<p>1) you are using <strong>2</strong> classic ELBs instead of <strong>1</strong> ALB
so costs savings can be a factor</p>

<p>2) using a layer7 loadbalancer vs a layer4 gives many features and capabilities not possible otherwise</p>

<p>you can see a comparrison here: 
<a href="https://aws.amazon.com/elasticloadbalancing/details/#compare" rel="nofollow noreferrer">https://aws.amazon.com/elasticloadbalancing/details/#compare</a></p>

<p>3) yes that wildcard would fit all your needs (sub1/sub2.domain.com)</p>

CC BY-SA 4.0
2018-07-19T20:22:38.260Z
2018-07-19T20:22:38.260Z
tolib
<p>My senario is this:</p>

<p>I am using 2 EC2 instances which I want reachable via urls as follows:</p>

<pre><code>sub1.domain.com
sub2.domain.com
</code></pre>

<p>I am aware of the fact that AWS Application Load Balancers currently support <a href="https://aws.amazon.com/blogs/aws/new-host-based-routing-support-for-aws-application-load-balancers/" rel="nofollow noreferrer">host based routing</a> so I guess this is now feasible.</p>

<p>Currently I am using 2 <strong>Classic</strong> Load Balancers on AWS to support access to those instances;</p>

<p>Is there a reason for me to switch to the host-based routing scenario of ALBs?</p>

<p>Perhaps the motive for this question is silly, but lately Amazon in its console, has grayed out the Classic ELB and marked it as </p>

<blockquote>
  <p>Previous Generation</p>
</blockquote>

<p>(I guess this wouldn't be a strong motive but it kind of discourages you a bit from using Classic ELBs henceforth...)</p>

<p>P.S. Haven't got the chance to test it, but I assume if I have issued an AWS wildcard certificate for <code>*.domain.com</code>, this would cover all target groups (i.e. hosts) under the ALB, right?</p>

<amazon-web-services><amazon-ec2><load-balance>
AWS: Application vs Classic Load Balancer
pkaramol
# AWS: Application vs Classic Load Balancer

(Asked by: username_0 on 2018-07-19)

My senario is this:
I am using 2 EC2 instances which I want reachable via urls as follows:
sub1.domain.com
sub2.domain.com

I am aware of the fact that AWS Application Load Balancers currently support host based routing so I guess this is now feasible.
Currently I am using 2 Classic Load Balancers on AWS to support access to those instances;
Is there a reason for me to switch to the host-based routing scenario of ALBs?
Perhaps the motive for this question is silly, but lately Amazon in its console, has grayed out the Classic ELB and marked it as 

Previous Generation

(I guess this wouldn't be a strong motive but it kind of discourages you a bit from using Classic ELBs henceforth...)
P.S. Haven't got the chance to test it, but I assume if I have issued an AWS wildcard certificate for *.domain.com, this would cover all target groups (i.e. hosts) under the ALB, right?

**Tags:** amazon-web-services, amazon-ec2, load-balance


---

## 1 answers

### Answer by username_1 on 2018-07-19. Score: 3 | Accepted answer

1) you are using **2** classic ELBs instead of **1** ALB
so costs savings can be a factor

2) using a layer7 loadbalancer vs a layer4 gives many features and capabilities not possible otherwise

you can see a comparrison here:
<https://aws.amazon.com/elasticloadbalancing/details/#compare>

3) yes that wildcard would fit all your needs (sub1/sub2.domain.com)


---

