WEBVTT 00:00.670 --> 00:07.020 In this demo, we are going to create an e-commerce cluster, which is Amazon's managed coroneted service 00:07.080 --> 00:09.340 known as elastic at service. 00:10.290 --> 00:13.620 And before we begin, there are a set of prerequisites to be configured. 00:13.780 --> 00:15.750 And so just having an established account. 00:15.780 --> 00:19.860 So if you're new to areas, then check out this link to get free access. 00:20.280 --> 00:24.780 You must already have installed the cubicle utility, which we have already done. 00:24.780 --> 00:25.740 So that's not required. 00:26.250 --> 00:32.130 Also, you must have some basic enterprise knowledge to perform some basic operations, such as configuring 00:32.160 --> 00:33.870 a cluster roll for each case. 00:34.210 --> 00:37.950 And then I am role for node group VPC. 00:38.580 --> 00:42.370 And an easy to key pair which will be used to Essence's to the worker notes. 00:42.600 --> 00:43.290 If you have two. 00:44.740 --> 00:48.670 So the by step instructions are available in this link. 00:48.970 --> 00:55.780 So you must have the advocacy ALLAI installed and have the Italy ACLC credentials configured. 00:56.410 --> 01:00.580 And we already have the two Cuttle utility installed. 01:00.760 --> 01:01.900 So we're going to skip that. 01:02.530 --> 01:09.520 And you must have created the I am role for the eCards cluster and a VPC if if required. 01:09.670 --> 01:11.440 Or you can use the default one. 01:12.040 --> 01:17.890 So we will start from this step here, which is of creating an Amazon case cluster. 01:18.880 --> 01:21.220 So these are the basic A.W. as configurations. 01:21.850 --> 01:23.200 So we've not spent time on that. 01:23.230 --> 01:25.690 Instead, we will dive into creating the communities cluster. 01:26.260 --> 01:29.650 So we've already configured all of the prerequisites required on our system. 01:30.290 --> 01:32.410 So to provision and a case cluster. 01:32.710 --> 01:36.340 Once you're logged into your W.S. account, go to services. 01:36.880 --> 01:43.240 Now, the easiest way to look up things here is to search for case within the search window and click 01:43.240 --> 01:44.460 on a case. 01:45.620 --> 01:48.260 So first thing to do is to name our cluster. 01:48.360 --> 01:54.860 So I'm going to use the name exampled voting app and we will leave the companies version had one dot, 01:55.160 --> 01:59.810 one six has default and we must have created a cluster service role. 01:59.840 --> 02:07.390 So select the role created for the eCards cluster here and then click on next in the networking section. 02:07.400 --> 02:09.700 We're going for the default VPC. 02:09.830 --> 02:12.560 And this is the only VPC that we have in this region. 02:13.100 --> 02:20.570 So one thing to notice here is that we're going with the US West to region, which is Oregon too, and 02:20.570 --> 02:24.230 we're making use of all the default subnets. 02:24.770 --> 02:25.490 Click on next. 02:25.520 --> 02:27.530 And again, click on Next. 02:28.130 --> 02:31.880 And this is just a review page so you can review and click on create. 02:32.660 --> 02:35.870 So this can take quite some time after 10 minutes. 02:35.900 --> 02:38.720 So let's just wait for this cluster to be created. 02:41.810 --> 02:45.710 OK, so now our cluster is active and it has got the active checkmark here. 02:45.920 --> 02:51.970 So the next thing to do is to add a node group, which is basically a group of worker nodes. 02:52.220 --> 02:52.400 Right. 02:52.430 --> 02:55.610 So we have created the Echobrain, this cluster, but there are no worker nodes. 02:55.670 --> 02:56.110 As of now. 02:56.120 --> 02:57.890 So that's the next step to do. 02:58.280 --> 03:03.680 So if you go to the compute section just below, you'll see an option to add a node node group. 03:04.640 --> 03:08.090 And let's assign a name for this, such as demo workers. 03:08.480 --> 03:11.420 And we select the case node roll. 03:11.840 --> 03:16.280 So this is another role that we created as a prerequisite for subnets. 03:16.490 --> 03:19.970 We select all the default subnets for now, of course, in your environment. 03:20.270 --> 03:23.900 You must choose those that are more relevant for you. 03:24.630 --> 03:30.590 And next, I've got a key that is also created so that we can essence's to work worker nodes as part 03:30.590 --> 03:31.940 of the prerequisite. 03:31.980 --> 03:33.410 So this key was created earlier. 03:34.060 --> 03:40.590 Now, you don't really need this unless you're really unless you really want to SSX to the worker nodes. 03:40.970 --> 03:41.180 Right. 03:41.990 --> 03:43.280 So everything else looks good. 03:43.790 --> 03:45.590 So we will click on next. 03:46.490 --> 03:48.500 And next, we said the compute configuration. 03:48.740 --> 03:52.910 And this is basically what images will be used for the worker nodes and their size. 03:53.390 --> 03:54.590 That this size, et cetera. 03:54.920 --> 03:57.560 So we'll leave these at the defaults for now. 03:57.690 --> 03:59.090 Then I'm going to click on Next. 04:00.410 --> 04:05.330 And here's the auto scaling groups where we specify the minimum number of nodes in the cluster. 04:05.600 --> 04:07.920 The maximum number of nodes and the desired size. 04:08.030 --> 04:10.610 So we will leave the default values here. 04:11.570 --> 04:15.530 Next, we will review the selected configurations and then click on CREATE. 04:16.190 --> 04:18.470 So, again, this can take a few minutes. 04:18.490 --> 04:20.360 So let's wait for that to finish. 04:21.370 --> 04:23.800 Now, let's check the status of the new group. 04:24.490 --> 04:31.120 We see that there are two nodes which are easy, two instances and are no groups are active. 04:31.510 --> 04:37.060 So the next step for us is to go to the terminal and set up the cube coddle utility to access this cluster. 04:37.660 --> 04:41.640 So run the cube cardioversion command and verify that it's working. 04:42.210 --> 04:47.290 But currently the Cube Carol utility is configured to work with our local I mean, you cube cluster. 04:47.890 --> 04:54.270 So the edible UCLA has a command to configure Cube Cuttle to work with the remote cluster reprovision. 04:54.850 --> 05:02.710 So for this, we must first have the ABC allai installed and configured to work with our A.W. as account. 05:03.520 --> 05:07.480 So the instructions to install a WC allai are available in the documentation. 05:07.510 --> 05:11.350 So we have that already installed on our system. 05:11.440 --> 05:13.030 So we're just going to skip that. 05:13.660 --> 05:19.420 Now, if you don't have the IWC allai installed, then you follow the relevant steps in the documentation 05:20.080 --> 05:21.680 for your operating system. 05:25.840 --> 05:33.280 So once installed the documentation page, we have an obvious command to configure keep conflict. 05:33.370 --> 05:36.860 It's called Update Dash Cube Config Command. 05:36.930 --> 05:45.610 So we copy this whole command and we paste it in our terminal and we specify the name of the cluster 05:45.610 --> 05:47.530 we created, which is example voting app. 05:48.280 --> 05:54.580 So once run, we see that the cube config is configured in our home directory under the folder Dot Cube. 05:55.600 --> 05:57.560 To verify if it's working as expected. 05:57.690 --> 05:59.460 Run the got to get notes command. 06:00.020 --> 06:06.260 And we should see the two worker nodes that are provisioned on A.W. US with their status and version 06:06.320 --> 06:07.430 of 1.0 16. 06:08.120 --> 06:13.370 So that's a proof that we are connecting to the right components cluster. 06:13.400 --> 06:16.370 And that cube config setup actually worked. 06:17.390 --> 06:24.000 So as with any managed service, you cannot see the massive nodes here, the massive nodes do not host 06:24.000 --> 06:25.590 any applications or workloads. 06:26.250 --> 06:31.430 You cannot associate to the master nodes or even access them, because in managed to coordinate the 06:31.430 --> 06:35.490 services, the mass notes are maintained by the service provider. 06:36.090 --> 06:41.700 Now, any cubicle commands we run would be targeting the remote cluster on NWS. 06:42.600 --> 06:46.320 So now we should be good to move ahead with our application deployment. 06:47.160 --> 06:52.260 So just as before, we will go to our GitHub repo and I'm going to clone it again. 06:52.350 --> 06:55.830 And so I'm going to run get get clone voting app command. 06:59.740 --> 07:00.680 And once downloaded. 07:00.740 --> 07:05.640 I'm going to go into the example Wooding app and under DCA, its specifications directory. 07:06.410 --> 07:11.630 If I run the Ellis command, I see all the deployment definition files as well as the service definition 07:11.630 --> 07:12.050 files. 07:13.150 --> 07:16.180 So now let's get started and create these resources. 07:16.330 --> 07:21.580 So first, I'll create the voting app deployment to keep Cupido create command and specify the voting 07:21.580 --> 07:25.360 app deployment file and followed by the service. 07:26.750 --> 07:31.850 And then we will create the Red House deployment and then the ready service. 07:34.550 --> 07:36.980 Followed by the Postgres deployment. 07:39.540 --> 07:40.680 And the postgrads service. 07:43.090 --> 07:45.300 And next, we create our work, our deployment. 07:47.600 --> 07:49.960 And finally recreate the result app deployment. 07:50.060 --> 07:51.250 And the result app service. 07:56.640 --> 07:58.350 So that's all of the objects. 07:58.680 --> 07:59.830 And they've all been created. 08:00.000 --> 08:03.480 So let's check the status using the cube to get DEPLOYMENT'S command. 08:05.970 --> 08:10.830 And we can see that we have most of our services that are up, except for the worker, which is still 08:10.830 --> 08:12.120 in process of being deployed. 08:12.630 --> 08:14.520 And we have to load balancer type services. 08:14.910 --> 08:20.070 And we also see the public IP and the public who are ill with which we can access them. 08:20.580 --> 08:22.830 So let's wait for our worker app to be deployed. 08:22.950 --> 08:28.320 And once that is done, we will go ahead and access the applications using the load balancer IP address. 08:29.850 --> 08:38.880 So the service has already interacted or made an I made a call to the native load balancer and created 08:39.630 --> 08:42.270 a load balancer on on the eatables environment. 08:42.420 --> 08:44.230 And this is the IP or the. 08:45.060 --> 08:46.020 You are for that. 08:47.220 --> 08:52.260 Now, all of our ports are up and running and all of our deployments have one out of one ready ports, 08:52.620 --> 08:53.640 which is what we expect. 08:53.850 --> 08:59.400 So let's view the voting service using the load balancer and I'm going to open it up in a Web browser. 09:00.090 --> 09:02.250 So here's the euro and hit enter. 09:02.340 --> 09:03.660 And here we go. 09:04.140 --> 09:09.870 So we have our voting application, which is accessible from our public extra load balancer and the 09:09.870 --> 09:10.590 external IP. 09:10.620 --> 09:13.860 So I'm going to make a selection here and to validate that. 09:13.880 --> 09:17.790 Let me copy and paste the external IP or the euro for my result app. 09:21.550 --> 09:24.070 And here we see the results as expected. 09:24.970 --> 09:31.620 So let's change the vote and we verify that the result reflects that change. 09:32.810 --> 09:38.600 So this was a quick and easy deployment for our voting application on a case. 09:39.470 --> 09:44.900 Once you're done, I'll make sure that you go back and clean up anything that you have done to save 09:45.160 --> 09:45.570 costs. 09:45.680 --> 09:51.410 So make sure to delete the case cluster and any applications that you have deployed on that. 09:52.010 --> 09:52.280 All right. 09:52.520 --> 09:53.810 Thanks for your time. 09:53.810 --> 09:55.690 And I will see you in the next demo.