1 00:00:00,670 --> 00:00:01,550 I don't want come back. 2 00:00:01,560 --> 00:00:08,360 So let's start digging into what each of us is the US or the U.S. to continue our service is all about. 3 00:00:08,360 --> 00:00:13,740 So there was an elastic container service or the easy to container service easier is a highly scalable 4 00:00:13,860 --> 00:00:21,480 fast Content Management Service that makes it easy to run stop and manage what darker containers on 5 00:00:21,480 --> 00:00:22,720 a cluster. 6 00:00:22,800 --> 00:00:31,560 So it is all about running Dhokha containers and running stopping and managing applications that run 7 00:00:31,620 --> 00:00:35,350 on containers on a cluster on a WS. 8 00:00:35,460 --> 00:00:41,290 You can host your cluster on a server list infrastructure that is managed by an easy task. 9 00:00:41,340 --> 00:00:45,270 Now let's take a step back why are we talking about a cluster. 10 00:00:45,270 --> 00:00:48,650 Because you need a pool of computer resources right. 11 00:00:48,660 --> 00:00:56,860 Whether they are bare metal servers or they are virtual machines like easy to instances where the management 12 00:00:56,920 --> 00:01:03,220 and orchestration for the containers can start spinning containers right. 13 00:01:03,370 --> 00:01:04,530 So that's what you need. 14 00:01:04,720 --> 00:01:10,930 So when are talking about the cluster that's the computer resource on which your containers will be 15 00:01:11,880 --> 00:01:14,950 ran stopped and managed. 16 00:01:15,190 --> 00:01:22,780 So that cluster can be on a server list infrastructure that is managed by Amazon s.c.s. 17 00:01:23,030 --> 00:01:25,280 So it could be services infrastructure. 18 00:01:25,280 --> 00:01:29,260 In this case you are not responsible for spinning. 19 00:01:29,500 --> 00:01:32,180 You see two instances and managing them yourself. 20 00:01:32,230 --> 00:01:37,490 Either we will do that easy as will be and provide that as a manager. 21 00:01:37,490 --> 00:01:42,230 So you compute cluster where the containers will run will be fully managed service. 22 00:01:42,230 --> 00:01:50,010 But in order to do that you have to launch your services and or task using and fire gate launch. 23 00:01:50,330 --> 00:01:51,940 And we'll talk about that later on. 24 00:01:54,920 --> 00:02:01,520 If for any reason you would like to manage your own cluster you would like to manage a spinning easy 25 00:02:01,550 --> 00:02:05,450 to instances and using auto scaling and elastic load balancers and all that. 26 00:02:05,480 --> 00:02:09,790 And you manage the plasticity and the scalability of your cluster. 27 00:02:09,920 --> 00:02:15,400 It's up to you but then you have to use a different launch type which is called the easy to launch type. 28 00:02:15,530 --> 00:02:22,220 So for more control you can host your tasks on a cluster of Amazon Elastic Compute Cloud easy to instances 29 00:02:22,580 --> 00:02:24,180 that you'll manage. 30 00:02:24,200 --> 00:02:30,500 So there is a fully managed service server unless there is a managed one where you have to create your 31 00:02:30,500 --> 00:02:37,800 own easy two instances cluster in an existing or a new PC and you manage it yourself. 32 00:02:38,360 --> 00:02:45,860 But it's a different lunchtime It wasn't easy lets you launch and stop container based applications 33 00:02:45,860 --> 00:02:47,210 with simple API calls. 34 00:02:47,210 --> 00:02:50,340 So these are the benefits of an easy task. 35 00:02:50,690 --> 00:02:55,940 It will allow you to get the state of your cluster from a centralized service which is going to be that 36 00:02:55,940 --> 00:03:02,320 Dhokha orchestration and management tool and will gives it will give you access to many familiar and 37 00:03:02,330 --> 00:03:03,260 easy to features 38 00:03:06,770 --> 00:03:12,770 you can use as an easy task to schedule the placement of containers across your cluster based on your 39 00:03:12,770 --> 00:03:13,690 resource needs. 40 00:03:13,700 --> 00:03:19,550 So that's the management and orchestration part which is Dakar based on based on isolation policies 41 00:03:19,580 --> 00:03:20,960 and availability requirements 42 00:03:23,970 --> 00:03:27,840 wasn't easy as eliminates the need for you to operate your own custom management. 43 00:03:27,840 --> 00:03:35,400 This is if you use exactly the far gate launch type and configuration management systems or worry about 44 00:03:35,400 --> 00:03:42,270 scaling your management infrastructure this is the Savalas option using the forget launch start wasn't 45 00:03:42,290 --> 00:03:49,860 easy as can also be used to create a consistent deployment and build experience and manage and scale 46 00:03:50,160 --> 00:03:55,830 batch workloads as well as extract transform e-tail workloads. 47 00:03:55,830 --> 00:04:00,000 The workload is basically like what the AWOS glue service. 48 00:04:00,000 --> 00:04:09,420 It's not here in the exam in this exam but you can take data from sources transform it in a way and 49 00:04:09,420 --> 00:04:13,020 then load it to other services in the new form. 50 00:04:13,020 --> 00:04:19,440 So that's what they extract transform and load workloads and build sophisticated application architectures 51 00:04:19,440 --> 00:04:21,380 on the micro services model. 52 00:04:21,390 --> 00:04:26,330 So again that's to the benefit of easy yes it can be used to create consistent deployment and build 53 00:04:26,350 --> 00:04:34,700 experience can allow you to manage and scale workloads of any types of batch workload type or extractors 54 00:04:34,750 --> 00:04:40,960 from load workloads and build sophisticated application architectures on our micro services model. 55 00:04:41,190 --> 00:04:48,730 So that's the couple applications that's what we're talking about here is the US is a regional service. 56 00:04:48,750 --> 00:04:55,230 So when you launch an Amazon easiest cluster that's in a region that simplifies an application containers 57 00:04:55,230 --> 00:04:59,820 in a highly available manner across multiple of celebrity zones within a region. 58 00:05:00,120 --> 00:05:03,140 So can an easy task cluster extend between regions. 59 00:05:03,150 --> 00:05:10,110 And the answer is as of now no it's regional confined to a region but your cluster can run in multiple 60 00:05:10,110 --> 00:05:16,260 Even if it is only within a region for every liberty you can create as an atheist cluster within a new 61 00:05:16,260 --> 00:05:23,700 VTC or an existing VBC and after a cluster is up and running what do I do. 62 00:05:23,700 --> 00:05:25,550 How can I start spinning containers. 63 00:05:25,560 --> 00:05:32,850 You start defining what we call task definitions and services that specify which took a container images 64 00:05:33,210 --> 00:05:35,220 to run across your clusters. 65 00:05:35,220 --> 00:05:39,660 So within that definition you start defining where is the image of the container. 66 00:05:39,680 --> 00:05:42,680 Remember with easy to insense we have something called A-MEI. 67 00:05:42,690 --> 00:05:43,270 Right. 68 00:05:43,560 --> 00:05:46,020 And that's what we used to launch and easy to instance. 69 00:05:46,020 --> 00:05:51,980 Basically that's the operating system and any other packaged tools that within the a.m.-I like that 70 00:05:52,020 --> 00:06:00,890 and for instance that instance or the VPN if you want to run VPN so am I the. 71 00:06:00,940 --> 00:06:08,100 And another analogy for they might is what we call content or image or container image. 72 00:06:08,100 --> 00:06:14,040 So we're witched image where is it saved are all defined within the definitions. 73 00:06:14,250 --> 00:06:15,720 Okay the next question. 74 00:06:15,720 --> 00:06:21,720 Where are the containers stored container images are stored and pulled from what we call container registries 75 00:06:21,960 --> 00:06:25,380 and that could be the Amazon registry they. 76 00:06:25,590 --> 00:06:27,620 Or it could be that look our hub. 77 00:06:27,810 --> 00:06:34,710 There are different registries for that which may exist within or outside of your obvious infrastructure 78 00:06:35,040 --> 00:06:36,430 containers and image. 79 00:06:36,430 --> 00:06:42,240 So let's talk about containers with just a little bit more to deploy an application as an easier. 80 00:06:42,480 --> 00:06:48,150 So containers in your application components must be architected to run in in containers. 81 00:06:48,180 --> 00:06:54,680 So of course in order to run anything on containers the application should know or should we develop 82 00:06:54,870 --> 00:06:58,240 to run and contain a tool should we develop as a containerized. 83 00:06:58,260 --> 00:07:00,760 Remember when we said the are not going anytime soon. 84 00:07:00,780 --> 00:07:04,820 Because the older applications are not designed to be containerized. 85 00:07:04,830 --> 00:07:11,940 So here what we are affirming are what we are confirming again is an application to be to run on containers 86 00:07:12,240 --> 00:07:15,330 has to be developed as such. 87 00:07:15,330 --> 00:07:20,280 I took her container as a standardized unit of software development containing everything that your 88 00:07:20,280 --> 00:07:21,810 software application needs. 89 00:07:21,810 --> 00:07:27,870 So the code runtime system to system is OK I'm not going to elaborate on that but the containers are 90 00:07:27,870 --> 00:07:30,860 created from a read only template called an image. 91 00:07:30,860 --> 00:07:38,940 So for a container to start it needs to run from the end of the container which is called an image. 92 00:07:39,060 --> 00:07:43,370 And in our case it's darker image because it is all about running containers. 93 00:07:43,380 --> 00:07:46,910 Images are typically built from a dock or five. 94 00:07:47,220 --> 00:07:54,560 What is a fight is a plain text file that specifies all the components that are included in the container. 95 00:07:54,570 --> 00:07:59,920 So basically as a script of commands that needs to say this is what you need. 96 00:07:59,910 --> 00:08:04,950 So if I'm starting Apache Web site or web server on a container. 97 00:08:04,950 --> 00:08:11,850 So in that case my components will be defined through the book or files I would say Do this do that. 98 00:08:11,850 --> 00:08:15,270 These are the commands you need to run this is that these other services you need to start in order 99 00:08:15,270 --> 00:08:15,890 to have that. 100 00:08:16,050 --> 00:08:18,480 So I create the image from a book or file. 101 00:08:18,600 --> 00:08:21,430 Now once it is created it should be published. 102 00:08:21,420 --> 00:08:29,510 Where to a registry which they can be downloaded from which they can be downloaded and run on your cluster. 103 00:08:29,520 --> 00:08:35,310 So the process as we see it here is look at a file that is used to create the image and then the image 104 00:08:35,300 --> 00:08:37,140 is published to a registry. 105 00:08:37,140 --> 00:08:41,740 And now when I do test definitions it will know because I will define it here. 106 00:08:41,760 --> 00:08:48,180 Where to go and get that image from look at file reference or a little bit about look and file if can 107 00:08:48,180 --> 00:08:52,240 build images automatically by reading instructions from other confi. 108 00:08:52,320 --> 00:08:57,780 So look a file is about instructions script or look at file as a text document that contains all the 109 00:08:57,780 --> 00:08:58,410 commands. 110 00:08:58,410 --> 00:09:01,900 A user could call on the command line to assemble an image. 111 00:09:02,130 --> 00:09:08,310 So instead of doing that manually you just put all the instructions into a look at file and Uecker will 112 00:09:08,400 --> 00:09:13,170 read the file build the image for you and then it will be published on registry's 113 00:09:16,120 --> 00:09:18,400 using Bokor built. 114 00:09:18,460 --> 00:09:20,630 So this is a set of Dooke are commands. 115 00:09:20,650 --> 00:09:26,320 Users can create an automated bill to make to build that executes several command line instructions 116 00:09:26,320 --> 00:09:27,220 in succession. 117 00:09:27,310 --> 00:09:29,700 OK so that was the Hubble image. 118 00:09:29,710 --> 00:09:39,190 So like much like him in his or her image is an inert immutable file that's essentially a snapshot of 119 00:09:39,190 --> 00:09:40,060 a container. 120 00:09:40,060 --> 00:09:44,950 Remember when we talked about the MRI being a snapshot of your easy to instance when you are creating 121 00:09:44,950 --> 00:09:45,560 an MRI. 122 00:09:45,610 --> 00:09:51,910 That's exactly the same images are created with the build command. 123 00:09:51,910 --> 00:09:53,550 So the doctor build command. 124 00:09:53,740 --> 00:09:56,480 And they will produce a container when it started. 125 00:09:56,500 --> 00:09:59,430 Where do I store them after they are created. 126 00:09:59,530 --> 00:10:03,660 Images are stored in a brokerage history such as book or hub. 127 00:10:03,760 --> 00:10:13,360 So this is the darker one version and easy are content registry is to be a version of that repository 128 00:10:13,360 --> 00:10:15,540 for our images. 129 00:10:15,770 --> 00:10:17,580 And this is how it looks like. 130 00:10:17,590 --> 00:10:21,730 So what we talked about the docker file has the instructions and commands. 131 00:10:21,730 --> 00:10:24,510 So it's the script when it is run. 132 00:10:24,610 --> 00:10:31,870 Then you get a container image and when you have the container image done tested then you can publish 133 00:10:31,870 --> 00:10:35,070 it to remember that it will be a smart place. 134 00:10:35,080 --> 00:10:36,980 This is the corresponding entity. 135 00:10:37,060 --> 00:10:43,030 So a container registry that could be the hub could be self-hosted registry or it could be easier. 136 00:10:43,330 --> 00:10:43,830 Right. 137 00:10:44,020 --> 00:10:50,260 So let's take a break and we'll come back and talk about it easy as long stipes briefly and then we'll 138 00:10:50,260 --> 00:10:57,730 talk about more of s.c.s features that are important for us to understand first because you will use 139 00:10:57,730 --> 00:10:58,710 it that's the future. 140 00:10:58,750 --> 00:11:04,330 And for that exam as well or the ABS component in the exam. 141 00:11:04,390 --> 00:11:06,420 So take a break and I'll see you shortly. 142 00:11:06,460 --> 00:11:06,930 Thank you.