1 00:00:00,090 --> 00:00:00,840 Hello and welcome back. 2 00:00:00,840 --> 00:00:04,110 Still with MLB and now we're going to talk about the supported target types. 3 00:00:04,110 --> 00:00:12,630 One very important thing to note as as of now that lambda functions as a target is not supported by 4 00:00:12,630 --> 00:00:15,120 the MLB unlike the MLB. 5 00:00:15,150 --> 00:00:18,090 This is not supported for the network nightclub balance. 6 00:00:18,900 --> 00:00:23,920 So let's talk about the supported one target types. 7 00:00:24,330 --> 00:00:28,360 So what are the support the target type junior configuring a network load balancer two types. 8 00:00:28,440 --> 00:00:34,710 An easy to instance I.D. So basically the back end or the target groups are going to include or the 9 00:00:34,710 --> 00:00:41,490 target group in that you're configuring is going to have instances easy to instances references referenced 10 00:00:41,520 --> 00:00:44,970 or registered by their I.D. to the group or an IP address. 11 00:00:45,000 --> 00:00:51,870 And if it is an IP address then it can be an IP address of instances honorable yes or they could be 12 00:00:51,960 --> 00:00:57,930 even on premise removed virtual machines or even remote load balancers firewalls whatever that is if 13 00:00:57,930 --> 00:01:03,680 the target is pacified by the IP address it can be from one of the following sites arrange like they'll 14 00:01:03,690 --> 00:01:04,730 be exactly. 15 00:01:04,770 --> 00:01:11,980 So it could be from the RNC 1918 range the 10 dot 8 1 2016 slash twelve and 1 six 16. 16 00:01:12,210 --> 00:01:18,300 Or it could be from the artists out of CE 65 98 that 160 for the 0 0 slash 10. 17 00:01:19,140 --> 00:01:23,000 Or it could be subnets from the VPC for the target group. 18 00:01:23,040 --> 00:01:30,650 The same thing if it is the same thing like the be the IP address targets can not be public ip addresses 19 00:01:30,690 --> 00:01:33,770 so they cannot be publicly refutable IP addresses. 20 00:01:33,960 --> 00:01:40,890 And currently for instance I.D. There are some types instance types that are not supported by the instance 21 00:01:41,010 --> 00:01:47,420 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. 22 00:01:47,430 --> 00:01:49,350 to see R1 one and the rest of the list. 23 00:01:49,350 --> 00:01:52,220 Of course this will change with time guys. 24 00:01:52,230 --> 00:01:58,420 So please if you want to know the fine and most accurate one go to the obvious and try to find under 25 00:01:58,420 --> 00:02:04,050 the MLB what is a supported or the excluded list from being defined by the instance I.D. however you 26 00:02:04,050 --> 00:02:09,480 have a solution if you had instances from those lists or from those types then you can configure them 27 00:02:09,540 --> 00:02:15,780 as targeted by the IP address not by the instance i.e. the supported side their blocks enabled the registration 28 00:02:15,780 --> 00:02:19,560 of the following with a target group the site there blocks that were just configured not the instance 29 00:02:19,570 --> 00:02:27,120 idea if the resources are addressable by IP address for example a database you can do that on premises 30 00:02:27,120 --> 00:02:31,370 resources link to yes through direct connect or VPN. 31 00:02:31,410 --> 00:02:37,650 Also the classic link instances if you have the classic easy two instances for IP target types for the 32 00:02:37,650 --> 00:02:46,070 ones configured with IP then the NLRB can support 55000 simultaneous connections or this is about 55000 33 00:02:46,080 --> 00:02:52,170 connections per minute for each unique target IP address and port that you are using to define are this 34 00:02:52,160 --> 00:02:56,230 number is going to be the same for months and years to come. 35 00:02:56,280 --> 00:03:02,060 They could be changed based on how it obviously enhances the nodes and the hardware and the easy to 36 00:03:02,060 --> 00:03:07,980 instance is used for their network load balancer but that gives you an indication that pair target will 37 00:03:07,990 --> 00:03:14,820 be can support up to 55000 connections per minute port allocation error so what if you go beyond the 38 00:03:14,840 --> 00:03:20,370 55000 what happens if the conviction rate is much higher than that you would find that there's allocation 39 00:03:20,440 --> 00:03:26,310 errors port allocation errors that might be surfacing or starting because of that and the solution is 40 00:03:26,610 --> 00:03:27,870 increase the target. 41 00:03:27,900 --> 00:03:32,400 So if you increase the targets the number of connections distributed across a larger number of targets 42 00:03:32,400 --> 00:03:37,530 are going to be less pair target and that's how you fix this problem if you face it and there'll be 43 00:03:37,890 --> 00:03:40,360 do not support longer target types. 44 00:03:40,360 --> 00:03:44,690 And as I mentioned this is as of now instances in appeared VPC. 45 00:03:44,820 --> 00:03:52,020 So if I have instances from a VPC that is paired with a VPC where the NLRB is then they must be registered 46 00:03:52,020 --> 00:03:55,040 with the IP address target types and not with the instance I.D.. 47 00:03:55,050 --> 00:03:55,690 All right. 48 00:03:55,740 --> 00:04:02,370 So instance I.D. for the supported instances undressed is all targets by IP address because routing 49 00:04:02,370 --> 00:04:08,430 for Target that are referenced or off type instance idea for Target using the instance I.D. traffic 50 00:04:08,430 --> 00:04:11,510 is routed to instances using the primary private IP address. 51 00:04:11,520 --> 00:04:12,690 Which one was that exactly. 52 00:04:12,750 --> 00:04:15,660 That's the one on Ethernet net zero. 53 00:04:15,660 --> 00:04:20,820 How about if I want to routing to a different IP address on a secondary interface if I need one if I 54 00:04:20,820 --> 00:04:27,480 need to then a reference to instances by the IP address and that's how you can have more than one IP 55 00:04:27,480 --> 00:04:31,910 on the instance where the the NLRB is going to send traffic to. 56 00:04:31,920 --> 00:04:32,240 All right. 57 00:04:32,250 --> 00:04:37,110 So if you are hosting multiple Web sites and you would like them to be to have certificates and all 58 00:04:37,110 --> 00:04:45,030 that on an easy to instance with the MLB then specify that the target type as IP address and add the 59 00:04:45,030 --> 00:04:51,470 different IP addresses on the AC to instance if you specify targets using the IP address what happens 60 00:04:51,480 --> 00:04:57,210 you can route traffic to an instance using any private IP address from one or more network interfaces. 61 00:04:57,210 --> 00:05:02,030 So even the secondary interface and interface you can do that thing the IP address is different. 62 00:05:02,040 --> 00:05:07,820 This enables multiple applications on an instance using the same port websites. 63 00:05:07,820 --> 00:05:09,420 It's the DP port 80. 64 00:05:09,510 --> 00:05:12,850 Obviously each network interface can have its own security group. 65 00:05:12,850 --> 00:05:20,380 So we can even have security rules different for each network interface All right so let's take a quick 66 00:05:20,380 --> 00:05:27,790 break come back and talk about a very important feature of MLB that is not existing for MLB NCLB which 67 00:05:27,790 --> 00:05:33,880 is the source IP address preservation basically when the client request passes through the MLB in certain 68 00:05:33,880 --> 00:05:34,540 conditions. 69 00:05:34,540 --> 00:05:42,250 The same IP address as a source will be passed on to the easy to instance or the back and compute that 70 00:05:42,250 --> 00:05:43,180 is defined. 71 00:05:43,230 --> 00:05:46,300 And let's talk about this in the next lecture after the break. 72 00:05:46,300 --> 00:05:46,930 I'll see you then. 73 00:05:46,930 --> 00:05:47,320 Thank you.