Herron.
And welcome back.
Now, in today's video, we will be discussing about the eight outposts.
Now, at this stage, we already know that cloud basically behind the scenes, it consists of group
of servers.
And on top of servers, there are multiple services that are hosted.
Now, these servers are basically into the data center of the cloud provider in case of a blaze.
All of the servers are in the data center.
And that basically means that everything related to the servers, the power, the cooling, Internet
connectivity, the physical security of the servers, everything is managed by e, w s.
Now, let's look into some of the challenges that you will face specifically related to how the base
regions are designed.
So let's say that you have an India map here and you have one region somewhere in the southern side
of India.
Now, let's say that you have a company that is into online gaming.
So they have users across multiple sites in India.
So you have users somewhere here in Gujarat, then you have a user somewhere here and you have a user
somewhere here.
Now, since the online gaming servers are hosted into the data center in the southern side, that basically
means that the user will be connecting across India to this specific data center.
And since the physical location across all of these users are different, the overall roundtrip time
that might take can also be different over here.
So the oral latency that each of these user might face would be different.
And when it comes to various use cases like online gaming, latency is something that is not really
looked upon through the happy face.
So one of the possible solution is you can go ahead and create your server somewhere in the middle of
the country so that the distribution and the oral roundtrip time can be reduced.
So now if you'll see, physical location is something very similar across all of these three users.
So now what we are discussing, we are discussing about some kind of a hybrid architecture.
Now, one of the challenges that you will face in hybrid architecture, let's assume that till now you
have everything hosted in the data center of a place you are extensively making use of the services
you are making, use of automation, tool to automate infrastructure and so on.
So if you jump to a hybrid architecture, it can come with own set of challenges.
One of the primary challenge that you will face is that you have a different set of APIs to manage servers
and services.
Then the automation is difficult.
Let's say that you are using TerraForm to go ahead and create set of servers and the entire infrastructure.
Now since you are using a hybrid architecture automation, you will have to spend more time on designing
automation here.
And third is additional learning is required because the hybrid architecture will require to not only
learn eatables but also the data center side of things.
So in order to overcome these challenges, you can make use of a base outpost.
So a outpost is basically a fully managed service that offers the same infrastructure services, APIs
and tools to virtually any data center, co-location space or on premise facility.
So basically we were discussing that there are servers hosted in the A side of the data center.
So what you can do with a base outpost is you can order these servers and you can put it at the customer
side location.
And once the servers are at the customer site location, what you can do, you can go ahead and run
wide variety of services like EC2, EBS, S3, RDC, X, EMR and so many others.
So it is something like you have an on premise location, you order servers through a outpost and you
can go ahead and all of the things like the set of APIs, automation, everything will work perfectly
here as well.
So let's look into the overall installation step.
First one is you have to order the set of servers.
Then the second part is installation.
Now do note that these servers are completely designed based on the service based requirements, and
hence the installation will not be done by you.
The installation will be done by the steam itself.
Once the installation is done, you can go ahead and launch and start to build your infrastructure here.
So these are the oral steps.
Let's quickly look into it at a high level overview.
Now from the aid of management console, let's open up the outpost service and within it let's quickly
do a browse catalog.
Now, depending upon the size requirements of the servers on the customer side, there are various kind
of offerings that are available.
So you see you have multiple sizes of offerings and based upon the size of the offering, you can go
ahead and choose the capacity here as well.
Now, along with that, one more thing I wanted to show you.
Let's quickly create a site.
So you're basically one of the first thing that you'll have to specify is the site address, which includes
the country street address as well as pin code.
Now do note that when the servers are hosted into the away side, there are a lot of things that place
takes care, like the power, the cooling, the physical security connectivity and so on.
Now, when these servers are moved to the customer site, all of these things like power will have to
be taken care by the customer.
So when you go ahead and create a site apart from just giving the site address, there are a lot of
other requirements related to facility.
So you are basically you have the temperature control related requirements.
You have power information that you'll have to specify the network for installation configuration,
you'll have to specify and all of those details.
So this is one thing that needs to be remembered.
Now, before we conclude, let's look into some of the use cases where a outpost can be beneficial.
The first use case, as we're discussing, is related to the low latency requirements.
The second important use case is related to the data residency requirement.
Many times in a lot of use cases, specifically in the organizations that are dealing with financial
and health care and so many others, they have a very tight data residency requirements where they're
mandated to store the data in a specific area.
Now, in fact, I'll tell you, I have a friend.
He works into a private organization that deals with military related equipment.
So they design and they manufacture them.
And he sees that there are so many requirements and one of the primary requirement is related to the
data residency.
So for example, let's say that you are designing a military equipment for a country and you are storing
all of the data like designs into a separate region that is outside of your country.
That is something like a no no.
So they have a very tight data residency requirement where the data must be stored in a specific facility.
It cannot even be stored in a different state altogether.
So for such use, cases at an outpost can be beneficial.
Then you also have requirements related to the local data processing where a outpost can also be used.
So that's the high level overview about the outpost.
And with this will conclude today's video.