Hello and welcome back.
Still with MLB and now we're going to talk about the supported target types.
One very important thing to note as as of now that lambda functions as a target is not supported by
the MLB unlike the MLB.
This is not supported for the network nightclub balance.
So let's talk about the supported one target types.
So what are the support the target type junior configuring a network load balancer two types.
An easy to instance I.D. So basically the back end or the target groups are going to include or the
target group in that you're configuring is going to have instances easy to instances references referenced
or registered by their I.D. to the group or an IP address.
And if it is an IP address then it can be an IP address of instances honorable yes or they could be
even on premise removed virtual machines or even remote load balancers firewalls whatever that is if
the target is pacified by the IP address it can be from one of the following sites arrange like they'll
be exactly.
So it could be from the RNC 1918 range the 10 dot 8 1 2016 slash twelve and 1 six 16.
Or it could be from the artists out of CE 65 98 that 160 for the 0 0 slash 10.
Or it could be subnets from the VPC for the target group.
The same thing if it is the same thing like the be the IP address targets can not be public ip addresses
so they cannot be publicly refutable IP addresses.
And currently for instance I.D. There are some types instance types that are not supported by the instance
I.D. and they have to be configured by the IP address like what the C1 S.S. wants easy to see G1 C.G.
to see R1 one and the rest of the list.
Of course this will change with time guys.
So please if you want to know the fine and most accurate one go to the obvious and try to find under
the MLB what is a supported or the excluded list from being defined by the instance I.D. however you
have a solution if you had instances from those lists or from those types then you can configure them
as targeted by the IP address not by the instance i.e. the supported side their blocks enabled the registration
of the following with a target group the site there blocks that were just configured not the instance
idea if the resources are addressable by IP address for example a database you can do that on premises
resources link to yes through direct connect or VPN.
Also the classic link instances if you have the classic easy two instances for IP target types for the
ones configured with IP then the NLRB can support 55000 simultaneous connections or this is about 55000
connections per minute for each unique target IP address and port that you are using to define are this
number is going to be the same for months and years to come.
They could be changed based on how it obviously enhances the nodes and the hardware and the easy to
instance is used for their network load balancer but that gives you an indication that pair target will
be can support up to 55000 connections per minute port allocation error so what if you go beyond the
55000 what happens if the conviction rate is much higher than that you would find that there's allocation
errors port allocation errors that might be surfacing or starting because of that and the solution is
increase the target.
So if you increase the targets the number of connections distributed across a larger number of targets
are going to be less pair target and that's how you fix this problem if you face it and there'll be
do not support longer target types.
And as I mentioned this is as of now instances in appeared VPC.
So if I have instances from a VPC that is paired with a VPC where the NLRB is then they must be registered
with the IP address target types and not with the instance I.D..
All right.
So instance I.D. for the supported instances undressed is all targets by IP address because routing
for Target that are referenced or off type instance idea for Target using the instance I.D. traffic
is routed to instances using the primary private IP address.
Which one was that exactly.
That's the one on Ethernet net zero.
How about if I want to routing to a different IP address on a secondary interface if I need one if I
need to then a reference to instances by the IP address and that's how you can have more than one IP
on the instance where the the NLRB is going to send traffic to.
All right.
So if you are hosting multiple Web sites and you would like them to be to have certificates and all
that on an easy to instance with the MLB then specify that the target type as IP address and add the
different IP addresses on the AC to instance if you specify targets using the IP address what happens
you can route traffic to an instance using any private IP address from one or more network interfaces.
So even the secondary interface and interface you can do that thing the IP address is different.
This enables multiple applications on an instance using the same port websites.
It's the DP port 80.
Obviously each network interface can have its own security group.
So we can even have security rules different for each network interface All right so let's take a quick
break come back and talk about a very important feature of MLB that is not existing for MLB NCLB which
is the source IP address preservation basically when the client request passes through the MLB in certain
conditions.
The same IP address as a source will be passed on to the easy to instance or the back and compute that
is defined.
And let's talk about this in the next lecture after the break.
I'll see you then.
Thank you.