1 00:00:00,770 --> 00:00:07,570 Unless sectionals set up a new elastic beanstalk instance as soon as the initial setup is complete you're 2 00:00:07,570 --> 00:00:09,390 going to see something like this on the screen. 3 00:00:09,550 --> 00:00:13,600 Now before we move on I want to very quickly tell you a little bit more about the lastic beanstalk and 4 00:00:13,600 --> 00:00:15,710 give you a better idea of why we're using it. 5 00:00:16,780 --> 00:00:17,110 All right. 6 00:00:17,110 --> 00:00:19,820 So here's what's happening right now with the lastic beanstalk. 7 00:00:20,020 --> 00:00:21,040 One of our users. 8 00:00:21,130 --> 00:00:26,130 In reality you and me as we're testing the application is going to open up their web browser and intend 9 00:00:26,140 --> 00:00:31,920 to navigate to our application running on AWOS when they attempt to navigate to our Web site. 10 00:00:31,930 --> 00:00:37,630 Their request will be handled by a load balancer that has already been created as a part of the elastic 11 00:00:37,630 --> 00:00:40,910 beanstalk application that we just created in the last section. 12 00:00:41,140 --> 00:00:45,770 So this load balancer has already been created for us when a request comes into it. 13 00:00:45,790 --> 00:00:51,700 The load balancer will around that request to a virtual machine that is running docker and on that virtual 14 00:00:51,700 --> 00:00:56,790 machine our dock or container will be running with our application inside of it. 15 00:00:57,660 --> 00:01:02,550 The benefit to elastic beanstalk is that it monitors the amount of traffic that's come in to our virtual 16 00:01:02,550 --> 00:01:03,620 machine right here. 17 00:01:03,780 --> 00:01:08,880 And as soon as that traffic reaches a certain threshold elastic beanstalk is going to automatically 18 00:01:08,880 --> 00:01:13,080 add in additional virtual machines to handle that traffic. 19 00:01:13,080 --> 00:01:17,970 So as soon as they request comes in it's going to go to the load balancer load balancers going to find 20 00:01:18,180 --> 00:01:24,060 the note here with the least amount of traffic and that will route that request to that particular virtual 21 00:01:24,060 --> 00:01:25,070 machine. 22 00:01:25,380 --> 00:01:30,360 Our application running inside of the dock or container will then respond to that request and the user 23 00:01:30,360 --> 00:01:33,660 will eventually get the file that they are looking for. 24 00:01:33,660 --> 00:01:34,670 So that's pretty much it. 25 00:01:34,680 --> 00:01:40,920 The benefit to plastic beanstalk is that it's going to automatically scale everything up for us. 26 00:01:40,920 --> 00:01:45,640 All right so now we've got a better idea of how elastic things stock is doing things for us. 27 00:01:45,660 --> 00:01:47,960 I want to flip back over to the CBS dashboard. 28 00:01:47,960 --> 00:01:49,080 Here it is right here. 29 00:01:49,230 --> 00:01:52,160 So I can see on the very top line we have a URL. 30 00:01:52,230 --> 00:01:55,390 This is the address of our application as it stands right now. 31 00:01:55,470 --> 00:02:00,470 You can open up this link at a new tab and you'll see a welcome message like this right here. 32 00:02:00,480 --> 00:02:05,940 So this is the default application that is launch anytime that you make a new elastic beanstalk instance 33 00:02:06,000 --> 00:02:07,230 running doctor. 34 00:02:07,260 --> 00:02:13,590 So of course we're going to eventually want to replace all this stuff with our application. 35 00:02:13,600 --> 00:02:13,870 All right. 36 00:02:13,870 --> 00:02:16,140 So let's take another quick break in the next section. 37 00:02:16,240 --> 00:02:23,380 We're going to make use of this new IBS instance and wire it up to our Travis see-I deployment process. 38 00:02:23,380 --> 00:02:25,470 So quick break and I'll see you in just a minute.