1 00:00:00,480 --> 00:00:03,800 So here is a short lecture just on the features you should know. 2 00:00:03,800 --> 00:00:06,680 An Elastic Beanstalk and let's go have a look at them. 3 00:00:06,690 --> 00:00:11,220 They're just small features but it's good that I mentioned them and my conscience will be appeased. 4 00:00:11,250 --> 00:00:14,940 So if you go to hell the world and we create a new environment. 5 00:00:14,940 --> 00:00:18,060 We have the option to choose a web server or a or environment. 6 00:00:18,090 --> 00:00:22,470 I'll be going into worker environment later in this course so we'll just focus on web server environments. 7 00:00:22,470 --> 00:00:27,720 Click on select and you can select a domain name and a pre configured platform so we'll just choose 8 00:00:28,350 --> 00:00:29,920 BHP as we did from before. 9 00:00:30,030 --> 00:00:33,750 Which is a simple application and then I'll configure more options. 10 00:00:33,840 --> 00:00:35,800 So this is just to show you the settings. 11 00:00:35,820 --> 00:00:41,080 So here we have a configuration presets which is low cost and free tier eligible. 12 00:00:41,190 --> 00:00:47,430 In this case the capacity the environment type a single instance and they will have an elastic IP attached 13 00:00:47,430 --> 00:00:48,060 to it. 14 00:00:48,060 --> 00:00:54,060 So this is one way and then as soon as we go into high availability then we have a load balancer and 15 00:00:54,060 --> 00:00:57,680 an older sibling group attached to our Elastic Beanstalk environment. 16 00:00:57,720 --> 00:01:03,540 And this is better for product ready environments so low cost is great for Dev and high availability 17 00:01:03,540 --> 00:01:07,510 is great for product and that's the only thing I want to show you out here. 18 00:01:07,680 --> 00:01:14,310 So I'll go ahead and cancel this next I'll just go into the environments and hear that. 19 00:01:14,410 --> 00:01:16,710 Next hour we'll show you the application versions. 20 00:01:16,840 --> 00:01:23,050 So any time we upload a new version and we deploy it it gets created into application versions. 21 00:01:23,150 --> 00:01:25,930 And as you can see here we've done five of these deploys. 22 00:01:26,050 --> 00:01:29,650 So we have five application versions being created. 23 00:01:29,650 --> 00:01:34,450 And we can see that the latest application version is currently deployed to end. 24 00:01:34,660 --> 00:01:35,820 So this is great. 25 00:01:35,830 --> 00:01:40,990 So as we start uploading more and more versions into these application versions you can imagine over 26 00:01:40,990 --> 00:01:43,150 time there will be hundreds of them. 27 00:01:43,150 --> 00:01:47,880 And it turns out that there is a limits in beanstalk that you can only have a thousand of them. 28 00:01:48,280 --> 00:01:53,410 So at some point you need to get rid of these application versions and for this you have something called 29 00:01:53,470 --> 00:01:55,270 an application version lifecycle. 30 00:01:55,810 --> 00:02:00,880 So by clicking on settings here I have the application version lifecycle settings and you can create 31 00:02:00,940 --> 00:02:06,910 a lifecycle policy which says that we can limit the number of application versions to say for example 32 00:02:06,940 --> 00:02:13,960 200 versions or we could limit by age and say OK after 180 days you can get rid of them. 33 00:02:14,260 --> 00:02:17,380 And this is just you would do you register them. 34 00:02:17,440 --> 00:02:22,180 You can retain the source bundle in history or you can delete the source bundle in history as well. 35 00:02:22,180 --> 00:02:26,590 So it's a good idea to retain the service bundle if you still want to delete it from the application 36 00:02:26,590 --> 00:02:32,980 versions and beanstalk but be able to somehow re upload it at some points and roll back to it if she 37 00:02:32,980 --> 00:02:34,060 needed to. 38 00:02:34,060 --> 00:02:39,640 And finally you need to create a service role or use a service role at least to perform this application 39 00:02:39,640 --> 00:02:43,260 version lifecycle settings and deletes these application versions. 40 00:02:43,270 --> 00:02:49,780 So here I'll just enable a lifecycle policy and say I only want 200 version of applications and don't 41 00:02:49,780 --> 00:02:53,740 worry it will not delete this one ever if it's deployed to an environment. 42 00:02:53,740 --> 00:02:58,920 So it will not delete an application version that is deployed in environments. 43 00:02:59,020 --> 00:03:02,470 The reason we do this again is to keep the number of application versions under control. 44 00:03:02,590 --> 00:03:08,260 But the reason we like to have many application versions in here is to be able to apply them to our 45 00:03:08,470 --> 00:03:12,430 stock environments and this is effectively doing a rollback for us. 46 00:03:12,520 --> 00:03:13,230 OK. 47 00:03:14,040 --> 00:03:14,260 OK. 48 00:03:14,260 --> 00:03:15,820 Next for these environments. 49 00:03:16,000 --> 00:03:21,130 If I go and click on it and click on actions I have the option to clone the environments. 50 00:03:21,130 --> 00:03:26,140 So cleaning the environment is taking all the settings and applying them to a new environments. 51 00:03:26,140 --> 00:03:30,560 So this is a really easy and quick way to create a new environment. 52 00:03:30,580 --> 00:03:36,030 We could also create clean environments using the ABC light and we'll be seeing this later on. 53 00:03:36,040 --> 00:03:39,650 So I wanted to show the clone option but I'm not going to use it. 54 00:03:39,680 --> 00:03:46,660 Next week we can do is completely redo the environments so you can terminate the environment and everything 55 00:03:46,660 --> 00:03:47,460 will go away. 56 00:03:47,530 --> 00:03:53,230 And this is the same in the ABC ally as doing Eby terminates or you can rebuild the environments and 57 00:03:53,230 --> 00:03:58,350 rebuilding the environment we'll delete everything and recreate it for you. 58 00:03:58,390 --> 00:04:04,060 So as it says here for example if you have any attach Amazon ideas database instance it will be deleted 59 00:04:04,330 --> 00:04:05,230 and then recreate it. 60 00:04:05,590 --> 00:04:11,530 So this is again going into our discussion of do we want the instances such as Audi as that emoji be 61 00:04:11,530 --> 00:04:18,040 or as soon as topics to be within our application environments or do we want them to be external. 62 00:04:18,040 --> 00:04:21,460 So I'm not going to click on rebuild but you get an idea of what it would do. 63 00:04:22,270 --> 00:04:27,510 And finally the last thing I want to show you is manage updates so it is possible for Elastic Beanstalk 64 00:04:27,520 --> 00:04:33,430 to apply patches to your environments and for this unit you present to create and manage updates. 65 00:04:33,580 --> 00:04:39,460 And so you can enable managed platform that's in the configuration tabs in here under manage updates. 66 00:04:39,460 --> 00:04:40,270 Here we go. 67 00:04:40,480 --> 00:04:46,270 And we could enable them and saying okay we create an update window weekly that starts Wednesday at 68 00:04:46,270 --> 00:04:52,720 2:00 a.m. and we want to do minor and patch only and if anybody we can do instant replacements. 69 00:04:52,720 --> 00:04:56,150 So this is a way to keep our Elastic Beanstalk up to date. 70 00:04:56,170 --> 00:05:01,660 And this is why beanstalk is such a great managed service is because it will do the updates for us on 71 00:05:01,660 --> 00:05:04,530 a weekly basis if we need to in a rolling manner. 72 00:05:04,570 --> 00:05:06,080 And it will be manage updates. 73 00:05:06,190 --> 00:05:07,710 So not going to enable it as well. 74 00:05:07,720 --> 00:05:13,060 But just showing you that it exists and there is a way to keep your instance patched using manage updates 75 00:05:13,200 --> 00:05:14,850 in Elastic Beanstalk. 76 00:05:14,890 --> 00:05:18,030 So this is what it's like to just a little bit of like random bits here and there. 77 00:05:18,130 --> 00:05:19,300 But now you've seen them. 78 00:05:19,300 --> 00:05:22,180 So you're supposed to know them and then we'll see you in the next lecture.