In this demo, we are going to create an e-commerce cluster, which is Amazon's managed coroneted service
known as elastic at service.
And before we begin, there are a set of prerequisites to be configured.
And so just having an established account.
So if you're new to areas, then check out this link to get free access.
You must already have installed the cubicle utility, which we have already done.
So that's not required.
Also, you must have some basic enterprise knowledge to perform some basic operations, such as configuring
a cluster roll for each case.
And then I am role for node group VPC.
And an easy to key pair which will be used to Essence's to the worker notes.
If you have two.
So the by step instructions are available in this link.
So you must have the advocacy ALLAI installed and have the Italy ACLC credentials configured.
And we already have the two Cuttle utility installed.
So we're going to skip that.
And you must have created the I am role for the eCards cluster and a VPC if if required.
Or you can use the default one.
So we will start from this step here, which is of creating an Amazon case cluster.
So these are the basic A.W. as configurations.
So we've not spent time on that.
Instead, we will dive into creating the communities cluster.
So we've already configured all of the prerequisites required on our system.
So to provision and a case cluster.
Once you're logged into your W.S. account, go to services.
Now, the easiest way to look up things here is to search for case within the search window and click
on a case.
So first thing to do is to name our cluster.
So I'm going to use the name exampled voting app and we will leave the companies version had one dot,
one six has default and we must have created a cluster service role.
So select the role created for the eCards cluster here and then click on next in the networking section.
We're going for the default VPC.
And this is the only VPC that we have in this region.
So one thing to notice here is that we're going with the US West to region, which is Oregon too, and
we're making use of all the default subnets.
Click on next.
And again, click on Next.
And this is just a review page so you can review and click on create.
So this can take quite some time after 10 minutes.
So let's just wait for this cluster to be created.
OK, so now our cluster is active and it has got the active checkmark here.
So the next thing to do is to add a node group, which is basically a group of worker nodes.
Right.
So we have created the Echobrain, this cluster, but there are no worker nodes.
As of now.
So that's the next step to do.
So if you go to the compute section just below, you'll see an option to add a node node group.
And let's assign a name for this, such as demo workers.
And we select the case node roll.
So this is another role that we created as a prerequisite for subnets.
We select all the default subnets for now, of course, in your environment.
You must choose those that are more relevant for you.
And next, I've got a key that is also created so that we can essence's to work worker nodes as part
of the prerequisite.
So this key was created earlier.
Now, you don't really need this unless you're really unless you really want to SSX to the worker nodes.
Right.
So everything else looks good.
So we will click on next.
And next, we said the compute configuration.
And this is basically what images will be used for the worker nodes and their size.
That this size, et cetera.
So we'll leave these at the defaults for now.
Then I'm going to click on Next.
And here's the auto scaling groups where we specify the minimum number of nodes in the cluster.
The maximum number of nodes and the desired size.
So we will leave the default values here.
Next, we will review the selected configurations and then click on CREATE.
So, again, this can take a few minutes.
So let's wait for that to finish.
Now, let's check the status of the new group.
We see that there are two nodes which are easy, two instances and are no groups are active.
So the next step for us is to go to the terminal and set up the cube coddle utility to access this cluster.
So run the cube cardioversion command and verify that it's working.
But currently the Cube Carol utility is configured to work with our local I mean, you cube cluster.
So the edible UCLA has a command to configure Cube Cuttle to work with the remote cluster reprovision.
So for this, we must first have the ABC allai installed and configured to work with our A.W. as account.
So the instructions to install a WC allai are available in the documentation.
So we have that already installed on our system.
So we're just going to skip that.
Now, if you don't have the IWC allai installed, then you follow the relevant steps in the documentation
for your operating system.
So once installed the documentation page, we have an obvious command to configure keep conflict.
It's called Update Dash Cube Config Command.
So we copy this whole command and we paste it in our terminal and we specify the name of the cluster
we created, which is example voting app.
So once run, we see that the cube config is configured in our home directory under the folder Dot Cube.
To verify if it's working as expected.
Run the got to get notes command.
And we should see the two worker nodes that are provisioned on A.W. US with their status and version
of 1.0 16.
So that's a proof that we are connecting to the right components cluster.
And that cube config setup actually worked.
So as with any managed service, you cannot see the massive nodes here, the massive nodes do not host
any applications or workloads.
You cannot associate to the master nodes or even access them, because in managed to coordinate the
services, the mass notes are maintained by the service provider.
Now, any cubicle commands we run would be targeting the remote cluster on NWS.
So now we should be good to move ahead with our application deployment.
So just as before, we will go to our GitHub repo and I'm going to clone it again.
And so I'm going to run get get clone voting app command.
And once downloaded.
I'm going to go into the example Wooding app and under DCA, its specifications directory.
If I run the Ellis command, I see all the deployment definition files as well as the service definition
files.
So now let's get started and create these resources.
So first, I'll create the voting app deployment to keep Cupido create command and specify the voting
app deployment file and followed by the service.
And then we will create the Red House deployment and then the ready service.
Followed by the Postgres deployment.
And the postgrads service.
And next, we create our work, our deployment.
And finally recreate the result app deployment.
And the result app service.
So that's all of the objects.
And they've all been created.
So let's check the status using the cube to get DEPLOYMENT'S command.
And we can see that we have most of our services that are up, except for the worker, which is still
in process of being deployed.
And we have to load balancer type services.
And we also see the public IP and the public who are ill with which we can access them.
So let's wait for our worker app to be deployed.
And once that is done, we will go ahead and access the applications using the load balancer IP address.
So the service has already interacted or made an I made a call to the native load balancer and created
a load balancer on on the eatables environment.
And this is the IP or the.
You are for that.
Now, all of our ports are up and running and all of our deployments have one out of one ready ports,
which is what we expect.
So let's view the voting service using the load balancer and I'm going to open it up in a Web browser.
So here's the euro and hit enter.
And here we go.
So we have our voting application, which is accessible from our public extra load balancer and the
external IP.
So I'm going to make a selection here and to validate that.
Let me copy and paste the external IP or the euro for my result app.
And here we see the results as expected.
So let's change the vote and we verify that the result reflects that change.
So this was a quick and easy deployment for our voting application on a case.
Once you're done, I'll make sure that you go back and clean up anything that you have done to save
costs.
So make sure to delete the case cluster and any applications that you have deployed on that.
All right.
Thanks for your time.
And I will see you in the next demo.