AWS Global Infrastructure
Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Time
19 hours 19 minutes
Difficulty
Intermediate
CEU/CPE
20
Video Transcription
00:00
>> Hello everybody, welcome back.
00:00
In this lesson, we're going to be talking
00:00
about the AWS global infrastructure.
00:00
The learning objectives for this lesson
00:00
are going to be to describe
00:00
the various components of
00:00
the global infrastructure and what it is as a whole.
00:00
Then discuss some key concepts on
00:00
service availability and why that's important.
00:00
Right here, what you see before you is
00:00
the high-level map of the global infrastructure.
00:00
All these dots they represent the various regions across
00:00
the world where AWS has built their data centers.
00:00
Now regions are the largest location that one could
00:00
select in the AWS environment and
00:00
their account in order to build up services.
00:00
What the blue dots represent
00:00
are all the regions that exists
00:00
today and the orange dots
00:00
represent the regions that are coming soon.
00:00
Now, we're going to get to this in a second.
00:00
But within a region,
00:00
you can select your availability zone
00:00
and within your availability zone,
00:00
you can deploy your servers, your storage,
00:00
your databases, and what have you.
00:00
That gives you a little bit
00:00
of an idea of if there's so many blue dots,
00:00
they really have a large infrastructure across the globe.
00:00
You really have a lot of possibilities to work
00:00
with AWS resources across the world.
00:00
It shows that you're not really going to be tied down
00:00
to bandwidth constraints depending
00:00
on where you are in the world.
00:00
One thing I do want to point out here
00:00
is that a lot of their development has been
00:00
in the United States and
00:00
across Eastern and Western Europe.
00:00
We see some in Asia as well.
00:00
But they're starting to build out
00:00
a little bit more down in the lower hemisphere.
00:00
We see one in Brazil,
00:00
we see one in Africa and we see one
00:00
already built in Australia
00:00
and another that is being built in Australia soon.
00:00
Cool to see that, but they are actively developing this.
00:00
I do want to quickly comment on that last slide,
00:00
that does not reflect their CDN.
00:00
That is not their CDN,
00:00
that is their data centers
00:00
within the regions that CDN totally different.
00:00
There's a lot more dots across the map.
00:00
Let's go ahead and talk
00:00
a little bit about the differences here.
00:00
Regions, we just talked about that.
00:00
Every AWS region includes multiple isolated,
00:00
physically separate availability zones.
00:00
These availability zones are designed to allow you to
00:00
build your architecture and to build it for resilience.
00:00
Each availability zone is about
00:00
at least 60 miles and
00:00
100 kilometers away from each other.
00:00
That if there's any natural disasters that take
00:00
place like a hurricane or a tsunami or
00:00
anything like that and it knocks out
00:00
the services in one availability zone.
00:00
You have the option to still be running because you have
00:00
another availability zone that
00:00
your services are all deployed to.
00:00
The whole idea with this Cloud environment
00:00
is that you can
00:00
stay up and available even when life is still happening.
00:00
Because you can copy your services over,
00:00
you can copy your data over to
00:00
other environments and that's the goal here
00:00
is to be architected for resilience and all that stuff.
00:00
The next thing we
00:00
want to talk about is availability zones.
00:00
AZs they are data center.
00:00
There's just a large data center.
00:00
If you're here in the United States
00:00
and you've ever seen a data center,
00:00
you know that it's massive.
00:00
If you've never seen the data center,
00:00
regardless of where you're at,
00:00
it's like a very big warehouse.
00:00
The best thing I like to compare it to it's a building
00:00
that's like Sam's Club
00:00
or Walmart if you're here in the United States.
00:00
Very big steel building or concrete building,
00:00
but it has lots of AZs,
00:00
lots of redundant power going into the building.
00:00
Security is pretty tight around the building.
00:00
They have 24/7 security guards.
00:00
They're going to have guard dogs,
00:00
they're going to have cameras, all that stuff.
00:00
Large fences to prevent people from
00:00
going in and out that shouldn't be.
00:00
It's very tight and
00:00
controlled when you're trying to get into one of these.
00:00
But within the data center,
00:00
you're going to have thousands of computers,
00:00
large servers stacked on these large racks.
00:00
There's lots of cooling.
00:00
It's cold in there.
00:00
It keeps all the computers nice and cold.
00:00
That's what an availability zone
00:00
is and you're going to have
00:00
multiple of these data center buildings
00:00
in one of these availability zones.
00:00
Another thing to note here is that
00:00
not every region in
00:00
availability zone is as matured as the next.
00:00
US East 1 over in Virginia,
00:00
that one's pretty matured.
00:00
That's not going to necessarily have
00:00
all the same services in Ohio,
00:00
which I think is US East 2 or in Australia or in Asia.
00:00
The reason why is it's not
00:00
only because technically speaking,
00:00
they just don't have the servers
00:00
yet and they haven't built it yet.
00:00
But it could also be because of
00:00
geographic legal constraints like Asia or Europe.
00:00
They are very sensitive about how you
00:00
handle data and very particular about privacy.
00:00
Maybe not all of the AWS services
00:00
that you could use here in the United States,
00:00
you could easily deploy over there.
00:00
That's not to say that, that'll always be the case.
00:00
But for now or at the time,
00:00
if you're watching this, you may not see it.
00:00
Yesterday I was looking at Amazon Polly,
00:00
and I was looking for
00:00
a specific neural voice from Amazon Polly.
00:00
I was looking for a specific region
00:00
and availability zone and I
00:00
couldn't get it and
00:00
that's just because they just don't have that there.
00:00
You have to get it from certain
00:00
regions and that's just it.
00:00
It is what it is. Just keep that in mind.
00:00
There are actively building and actively improving and
00:00
every year new services and new options up here.
00:00
But that's just something to keep in mind.
00:00
The CloudFront edge location is their CDN network.
00:00
Like I said, there's a lot of
00:00
edge locations across the globe way
00:00
more than what we so for regions.
00:00
If you're trying to build
00:00
for speed on your websites and stuff like that,
00:00
you could deploy cached versions of
00:00
your website to an edge location
00:00
closest to your customers or to yourself.
00:00
Just pick the region that's most
00:00
relevant to you based on where you are in the world.
00:00
But for that speed and improved latency,
00:00
you could just deploy to
00:00
the CloudFront edge location
00:00
and that takes care of that as well.
00:00
Here we are. Let's go a little bit deeper here.
00:00
Regions are designed to be completely full tolerant.
00:00
They are strategically placed in areas around
00:00
the world that are isolated from one another.
00:00
This goes back to what I was saying there,
00:00
so many miles apart.
00:00
They're designed in this way to
00:00
prevent natural disasters and all that stuff.
00:00
Maybe black outages, blackouts,
00:00
and stuff like that from impacting one another.
00:00
If one gets impacted and it would
00:00
take a lot to knock it out.
00:00
But if it did, if they get knocked out,
00:00
the others would not be impacted.
00:00
You could rely on the fact that,
00:00
if Virginia got knocked out,
00:00
you could still have your services up and
00:00
running over in Oregon or something like that.
00:00
Availability zones add an additional layer to isolation
00:00
and persistence on how we
00:00
architect our solutions in the Cloud.
00:00
Each region contains multiple availability zones
00:00
and let's just take a step back here.
00:00
Usually, each region consists of two or more.
00:00
You're going to see a lot.
00:00
When you look online, a lot of the regions that I see,
00:00
they consist of three,
00:00
they're going to have a lot more availability zones.
00:00
That's a good thing.
00:00
You're going to see a lot of options as far as
00:00
how many availability zones you have,
00:00
but not every region will have the same so they do vary.
00:00
I think I saw one region that has six availability zones.
00:00
They all vary and all depends on how
00:00
mature they are and the demand.
00:00
The demand that's theirs.
00:00
AWS is going to prioritize
00:00
investing into the areas where there's higher demand.
00:00
US East 1 has a lot of
00:00
demand and there's going to be a lot
00:00
of availability zones in that
00:00
one. Just keep that in mind.
00:00
The availability zones are
00:00
characterized as discrete data centers.
00:00
They're strategically placed away from one another.
00:00
It doesn't necessarily mean there's
00:00
one building in each AZ.
00:00
I've seen AZs with multiple data center buildings.
00:00
But you're still going to have these AZs are placed
00:00
far enough away from each other to
00:00
be safe from getting impacted.
00:00
The CloudFront. Here's an example here.
00:00
We have three different devices
00:00
and they want to access the data on S3.
00:00
What they're doing is they're going through CloudFront.
00:00
If you don't know what a CDN is,
00:00
I recommend you look it up.
00:00
This is one of those things that you might
00:00
want to know about before jumping into the Cloud.
00:00
But it stands for content distribution network.
00:00
It is a network that is designed to share your content,
00:00
your images, your videos,
00:00
your websites, your files.
00:00
It's designed to do that in a situation that's rapid.
00:00
You can call the data down and review it.
00:00
Let's say you're trying to download a file,
00:00
you can download that file
00:00
over and over because it's cached,
00:00
it's stored there and you're not ever using
00:00
the actual file share server,
00:00
you're just using the CDN servers.
00:00
The two different locations, what happens is,
00:00
let's say you have your files stored in Amazon S3.
00:00
We have these three devices
00:00
and they're constantly hitting
00:00
the Amazon S3 bucket
00:00
for an image like Instagram or something like that.
00:00
They want to see the image constantly.
00:00
They want to engage with it.
00:00
Instead of overloading S3,
00:00
you could cache the images on CloudFront
00:00
and just have all the devices and
00:00
users access CloudFront instead.
00:00
What that does is that acts as a buffer to give
00:00
Amazon S3 or the servers whatever
00:00
you're using to have some room.
00:00
It gives a room to breathe and not deal with
00:00
the massive traffic overload
00:00
on the actual servers themselves.
00:00
To summarize, in this lesson we covered
00:00
the key concepts for AWS global infrastructure.
00:00
We talked about various characteristics for regions,
00:00
availability zones, and CloudFront edge locations.
00:00
If you need a little bit more information on CDNs,
00:00
go ahead and just do a brief search online.
00:00
You could go on Google, go
00:00
on Wikipedia, just look it up.
00:00
You maybe find a YouTube video that helps you with that.
00:00
We do have videos here on Cybrary that talk about
00:00
content distribution networks and
00:00
just general networking periods.
00:00
Be sure to check those out if you feel like you
00:00
need to be brushed up on your networking concepts.
00:00
I hope this was helpful.
00:00
If you have any questions, feel free
00:00
to reach out to me and if not,
00:00
I'll see you in the next lesson.
Up Next
Setting Up the CLI
10m
Module 2 Conclusion
5m
Similar Content
