1 00:00:02,040 --> 00:00:05,020 Now before we dive deeper into this section 2 00:00:05,020 --> 00:00:06,657 and into working with AWS, 3 00:00:07,660 --> 00:00:11,470 there actually are a couple of things I wanna clarify. 4 00:00:11,470 --> 00:00:16,260 First, if you wanna learn a bit more about the AWS basics, 5 00:00:16,260 --> 00:00:19,020 you can visit our webpage academind.com, 6 00:00:19,020 --> 00:00:23,270 click on browse by topic and go to the AWS sectioned here. 7 00:00:23,270 --> 00:00:26,250 Here you find some AWS resources we get 8 00:00:26,250 --> 00:00:29,310 and especially this Basics playlist, 9 00:00:29,310 --> 00:00:31,090 might be interesting to you. 10 00:00:31,090 --> 00:00:34,060 You also find a link to that playlist attached. 11 00:00:34,060 --> 00:00:37,640 There I get you started with AWS in general, 12 00:00:37,640 --> 00:00:39,960 we talk about a couple of core concepts, 13 00:00:39,960 --> 00:00:42,630 which have nothing to do with containers 14 00:00:42,630 --> 00:00:46,030 but which will help you understand AWS a bit better. 15 00:00:46,030 --> 00:00:49,640 Especially this AWS, VPC and subnets, 16 00:00:49,640 --> 00:00:52,140 part might be interesting to you 17 00:00:52,140 --> 00:00:56,370 since you will see these VPCs and subnets in action 18 00:00:56,370 --> 00:00:58,880 throughout this section here. 19 00:00:58,880 --> 00:01:00,430 So, this is optional 20 00:01:00,430 --> 00:01:02,390 but you might wanna go through this 21 00:01:02,390 --> 00:01:05,530 in case you're wondering what we're working with 22 00:01:05,530 --> 00:01:09,270 and why we're using all these things we are using. 23 00:01:09,270 --> 00:01:11,400 Of course you can also adjust follow along 24 00:01:11,400 --> 00:01:13,160 without that greater knowledge. 25 00:01:13,160 --> 00:01:16,610 But if you consider using AWS for yourself 26 00:01:16,610 --> 00:01:19,923 then I definitely recommend you pick up these basics. 27 00:01:20,940 --> 00:01:23,150 Now, that's AWS in general. 28 00:01:23,150 --> 00:01:25,450 Now, I also briefly wanna explain 29 00:01:25,450 --> 00:01:29,310 this Fargate thing in greater detail. 30 00:01:29,310 --> 00:01:33,760 We did create our first cluster and run our first container 31 00:01:33,760 --> 00:01:37,440 in this task which uses this Fargate thing, 32 00:01:37,440 --> 00:01:40,650 this Fargate runtime, you could say. 33 00:01:40,650 --> 00:01:42,940 Now, this is AWS specific, 34 00:01:42,940 --> 00:01:46,570 and it simply means that AWS will run this container 35 00:01:46,570 --> 00:01:50,310 in an environment where it only creates this server 36 00:01:50,310 --> 00:01:53,780 on which the container runs when it's needed kind of, 37 00:01:53,780 --> 00:01:57,300 of course it does this in a very efficient and fast way, 38 00:01:57,300 --> 00:01:59,340 but it will ensure that we don't always 39 00:01:59,340 --> 00:02:01,260 have a EC2 Instance, 40 00:02:01,260 --> 00:02:03,000 as server up and running, 41 00:02:03,000 --> 00:02:05,020 but only when we need it. 42 00:02:05,020 --> 00:02:08,500 And that server is also fully managed for us, 43 00:02:08,500 --> 00:02:10,889 so that we don't need to worry about updates 44 00:02:10,889 --> 00:02:12,850 or anything like this. 45 00:02:12,850 --> 00:02:15,690 The task size which we can choose down there, 46 00:02:15,690 --> 00:02:19,780 then simply specifies how much memory and CPU 47 00:02:19,780 --> 00:02:23,840 is available for our container when it executes. 48 00:02:23,840 --> 00:02:28,190 And here we by default use the smallest possible choices, 49 00:02:28,190 --> 00:02:31,270 of course, if you are using this in production, 50 00:02:31,270 --> 00:02:35,150 you might wanna consider using more powerful settings here, 51 00:02:35,150 --> 00:02:38,250 but of course the more powerful settings you choose here 52 00:02:38,250 --> 00:02:40,550 the higher your costs will be. 53 00:02:40,550 --> 00:02:42,750 So, for the demo purposes here 54 00:02:42,750 --> 00:02:45,393 the smallest settings will do. 55 00:02:46,800 --> 00:02:47,633 Now of course, 56 00:02:47,633 --> 00:02:50,490 if you use the smallest possible settings here, 57 00:02:50,490 --> 00:02:54,700 this means that if you got a lot of incoming requests, 58 00:02:54,700 --> 00:02:57,660 your container will be up and running handling them. 59 00:02:57,660 --> 00:03:01,670 But at some point, these resources might not suffice. 60 00:03:01,670 --> 00:03:04,460 AWS, ECS then also offers 61 00:03:04,460 --> 00:03:07,260 something which is called Auto Scaling, 62 00:03:07,260 --> 00:03:09,570 where it would actually create 63 00:03:09,570 --> 00:03:12,370 more than one running container at the same time, 64 00:03:12,370 --> 00:03:16,610 with these tasks sizes to help you scale up 65 00:03:16,610 --> 00:03:20,020 and have more containers handling incoming requests. 66 00:03:20,020 --> 00:03:23,530 So, in addition to choosing higher memory 67 00:03:23,530 --> 00:03:25,340 and CPU values here, 68 00:03:25,340 --> 00:03:29,030 you could also configure this scaling later 69 00:03:29,030 --> 00:03:32,540 to be able to handle more workload with your container. 70 00:03:32,540 --> 00:03:36,250 That's all not something we need here in this course 71 00:03:36,250 --> 00:03:38,260 and for this demo application, 72 00:03:38,260 --> 00:03:41,800 I just want to clarify what this ECS 73 00:03:41,800 --> 00:03:44,180 and this Fargate thing is about, 74 00:03:44,180 --> 00:03:45,890 and what you should watch out for 75 00:03:45,890 --> 00:03:48,600 if you wanna dive into AWS deeper 76 00:03:48,600 --> 00:03:52,680 and if you plan on using this for your own real application. 77 00:03:52,680 --> 00:03:55,350 Of course also check out the AWS, ECS 78 00:03:56,238 --> 00:03:59,410 and Fargate documentations in that case. 79 00:03:59,410 --> 00:04:02,690 With that, we don't need to change anything at the moment, 80 00:04:02,690 --> 00:04:04,900 I just wanted to briefly mention this 81 00:04:04,900 --> 00:04:07,520 to ensure that we're all on the same page 82 00:04:07,520 --> 00:04:10,513 and these values are no mystery to you.