I don't want come back.
So let's start digging into what each of us is the US or the U.S. to continue our service is all about.
So there was an elastic container service or the easy to container service easier is a highly scalable
fast Content Management Service that makes it easy to run stop and manage what darker containers on
a cluster.
So it is all about running Dhokha containers and running stopping and managing applications that run
on containers on a cluster on a WS.
You can host your cluster on a server list infrastructure that is managed by an easy task.
Now let's take a step back why are we talking about a cluster.
Because you need a pool of computer resources right.
Whether they are bare metal servers or they are virtual machines like easy to instances where the management
and orchestration for the containers can start spinning containers right.
So that's what you need.
So when are talking about the cluster that's the computer resource on which your containers will be
ran stopped and managed.
So that cluster can be on a server list infrastructure that is managed by Amazon s.c.s.
So it could be services infrastructure.
In this case you are not responsible for spinning.
You see two instances and managing them yourself.
Either we will do that easy as will be and provide that as a manager.
So you compute cluster where the containers will run will be fully managed service.
But in order to do that you have to launch your services and or task using and fire gate launch.
And we'll talk about that later on.
If for any reason you would like to manage your own cluster you would like to manage a spinning easy
to instances and using auto scaling and elastic load balancers and all that.
And you manage the plasticity and the scalability of your cluster.
It's up to you but then you have to use a different launch type which is called the easy to launch type.
So for more control you can host your tasks on a cluster of Amazon Elastic Compute Cloud easy to instances
that you'll manage.
So there is a fully managed service server unless there is a managed one where you have to create your
own easy two instances cluster in an existing or a new PC and you manage it yourself.
But it's a different lunchtime It wasn't easy lets you launch and stop container based applications
with simple API calls.
So these are the benefits of an easy task.
It will allow you to get the state of your cluster from a centralized service which is going to be that
Dhokha orchestration and management tool and will gives it will give you access to many familiar and
easy to features
you can use as an easy task to schedule the placement of containers across your cluster based on your
resource needs.
So that's the management and orchestration part which is Dakar based on based on isolation policies
and availability requirements
wasn't easy as eliminates the need for you to operate your own custom management.
This is if you use exactly the far gate launch type and configuration management systems or worry about
scaling your management infrastructure this is the Savalas option using the forget launch start wasn't
easy as can also be used to create a consistent deployment and build experience and manage and scale
batch workloads as well as extract transform e-tail workloads.
The workload is basically like what the AWOS glue service.
It's not here in the exam in this exam but you can take data from sources transform it in a way and
then load it to other services in the new form.
So that's what they extract transform and load workloads and build sophisticated application architectures
on the micro services model.
So again that's to the benefit of easy yes it can be used to create consistent deployment and build
experience can allow you to manage and scale workloads of any types of batch workload type or extractors
from load workloads and build sophisticated application architectures on our micro services model.
So that's the couple applications that's what we're talking about here is the US is a regional service.
So when you launch an Amazon easiest cluster that's in a region that simplifies an application containers
in a highly available manner across multiple of celebrity zones within a region.
So can an easy task cluster extend between regions.
And the answer is as of now no it's regional confined to a region but your cluster can run in multiple
Even if it is only within a region for every liberty you can create as an atheist cluster within a new
VTC or an existing VBC and after a cluster is up and running what do I do.
How can I start spinning containers.
You start defining what we call task definitions and services that specify which took a container images
to run across your clusters.
So within that definition you start defining where is the image of the container.
Remember with easy to insense we have something called A-MEI.
Right.
And that's what we used to launch and easy to instance.
Basically that's the operating system and any other packaged tools that within the a.m.-I like that
and for instance that instance or the VPN if you want to run VPN so am I the.
And another analogy for they might is what we call content or image or container image.
So we're witched image where is it saved are all defined within the definitions.
Okay the next question.
Where are the containers stored container images are stored and pulled from what we call container registries
and that could be the Amazon registry they.
Or it could be that look our hub.
There are different registries for that which may exist within or outside of your obvious infrastructure
containers and image.
So let's talk about containers with just a little bit more to deploy an application as an easier.
So containers in your application components must be architected to run in in containers.
So of course in order to run anything on containers the application should know or should we develop
to run and contain a tool should we develop as a containerized.
Remember when we said the are not going anytime soon.
Because the older applications are not designed to be containerized.
So here what we are affirming are what we are confirming again is an application to be to run on containers
has to be developed as such.
I took her container as a standardized unit of software development containing everything that your
software application needs.
So the code runtime system to system is OK I'm not going to elaborate on that but the containers are
created from a read only template called an image.
So for a container to start it needs to run from the end of the container which is called an image.
And in our case it's darker image because it is all about running containers.
Images are typically built from a dock or five.
What is a fight is a plain text file that specifies all the components that are included in the container.
So basically as a script of commands that needs to say this is what you need.
So if I'm starting Apache Web site or web server on a container.
So in that case my components will be defined through the book or files I would say Do this do that.
These are the commands you need to run this is that these other services you need to start in order
to have that.
So I create the image from a book or file.
Now once it is created it should be published.
Where to a registry which they can be downloaded from which they can be downloaded and run on your cluster.
So the process as we see it here is look at a file that is used to create the image and then the image
is published to a registry.
And now when I do test definitions it will know because I will define it here.
Where to go and get that image from look at file reference or a little bit about look and file if can
build images automatically by reading instructions from other confi.
So look a file is about instructions script or look at file as a text document that contains all the
commands.
A user could call on the command line to assemble an image.
So instead of doing that manually you just put all the instructions into a look at file and Uecker will
read the file build the image for you and then it will be published on registry's
using Bokor built.
So this is a set of Dooke are commands.
Users can create an automated bill to make to build that executes several command line instructions
in succession.
OK so that was the Hubble image.
So like much like him in his or her image is an inert immutable file that's essentially a snapshot of
a container.
Remember when we talked about the MRI being a snapshot of your easy to instance when you are creating
an MRI.
That's exactly the same images are created with the build command.
So the doctor build command.
And they will produce a container when it started.
Where do I store them after they are created.
Images are stored in a brokerage history such as book or hub.
So this is the darker one version and easy are content registry is to be a version of that repository
for our images.
And this is how it looks like.
So what we talked about the docker file has the instructions and commands.
So it's the script when it is run.
Then you get a container image and when you have the container image done tested then you can publish
it to remember that it will be a smart place.
This is the corresponding entity.
So a container registry that could be the hub could be self-hosted registry or it could be easier.
Right.
So let's take a break and we'll come back and talk about it easy as long stipes briefly and then we'll
talk about more of s.c.s features that are important for us to understand first because you will use
it that's the future.
And for that exam as well or the ABS component in the exam.
So take a break and I'll see you shortly.
Thank you.