1
00:00:06,580 --> 00:00:08,303
- Now let's talk about regions.

2
00:00:09,190 --> 00:00:13,710
Within AWS we have a
number of different regions

3
00:00:13,710 --> 00:00:15,200
all over the world,

4
00:00:15,200 --> 00:00:19,470
and regions are sort of the
primary building block of AWS.

5
00:00:19,470 --> 00:00:21,970
It's the first thing that we start with.

6
00:00:21,970 --> 00:00:24,110
It's the first decision that we make.

7
00:00:24,110 --> 00:00:28,930
Before we start launching EC2
instances or storage volumes

8
00:00:28,930 --> 00:00:32,010
or whatever else, we first have to decide

9
00:00:32,010 --> 00:00:34,320
which region will these go into.

10
00:00:34,320 --> 00:00:37,520
From which region will
we run our applications

11
00:00:37,520 --> 00:00:39,320
and serve our audience?

12
00:00:39,320 --> 00:00:41,300
And so let's take a look at the regions

13
00:00:41,300 --> 00:00:43,000
that are currently available.

14
00:00:43,000 --> 00:00:44,130
If we look here on the map

15
00:00:44,130 --> 00:00:47,450
starting from the West Coast of the U.S.,

16
00:00:47,450 --> 00:00:49,503
we have the Oregon region,

17
00:00:50,640 --> 00:00:51,790
the California region.

18
00:00:51,790 --> 00:00:54,010
Those are U.S. West one and two.

19
00:00:54,010 --> 00:00:57,160
We also have GovCloud West.

20
00:00:57,160 --> 00:00:58,640
Moving towards the East Coast,

21
00:00:58,640 --> 00:01:01,830
we have U.S. East two in Ohio,

22
00:01:01,830 --> 00:01:04,970
U.S. East one in northern Virginia.

23
00:01:04,970 --> 00:01:08,700
We have Canada Central up in Montreal.

24
00:01:08,700 --> 00:01:12,370
Down into South America,
we have Sao Paulo.

25
00:01:12,370 --> 00:01:15,770
Moving into Europe, we have Ireland,

26
00:01:15,770 --> 00:01:18,470
London, Paris,

27
00:01:18,470 --> 00:01:19,683
Frankfurt, Germany,

28
00:01:20,640 --> 00:01:24,410
and then moving farther
east into Asia Pacific,

29
00:01:24,410 --> 00:01:28,090
we have Mumbai, Singapore,

30
00:01:28,090 --> 00:01:29,463
Sydney, Australia,

31
00:01:30,540 --> 00:01:32,120
Ningxia, China,

32
00:01:32,120 --> 00:01:34,010
Beijing, China,

33
00:01:34,010 --> 00:01:35,383
Seoul, South Korea,

34
00:01:37,190 --> 00:01:38,870
and Tokyo, Japan.

35
00:01:38,870 --> 00:01:43,810
Now these 18 regions are
currently available for use,

36
00:01:43,810 --> 00:01:47,070
but there are a few more
regions that are on the way.

37
00:01:47,070 --> 00:01:49,150
As of the time of this
video, these regions

38
00:01:49,150 --> 00:01:52,420
are not yet online but they will be soon.

39
00:01:52,420 --> 00:01:57,170
We have GovCloud East on
the East Coast of the U.S.

40
00:01:57,170 --> 00:02:01,770
We have Sweden, Bahrain,
they're in the Middle East,

41
00:02:01,770 --> 00:02:03,510
and then Hong Kong.

42
00:02:03,510 --> 00:02:07,200
Right, so at some point
here in the near future

43
00:02:07,200 --> 00:02:09,790
if not already by the time of this video,

44
00:02:09,790 --> 00:02:13,330
we will have 22 regions available

45
00:02:13,330 --> 00:02:16,970
to run our applications and workloads.

46
00:02:16,970 --> 00:02:20,650
So a common question
is, well why do I choose

47
00:02:20,650 --> 00:02:22,160
one region over another?

48
00:02:22,160 --> 00:02:25,110
And it mainly comes down
to several key things.

49
00:02:25,110 --> 00:02:29,080
One many be due to cost, right?

50
00:02:29,080 --> 00:02:31,360
Different services

51
00:02:31,360 --> 00:02:34,480
cost different amounts
in different regions.

52
00:02:34,480 --> 00:02:37,200
So, the other reason might be

53
00:02:38,060 --> 00:02:40,410
that you want to serve that application

54
00:02:40,410 --> 00:02:42,740
to a particular audience,

55
00:02:42,740 --> 00:02:46,360
and you want that application
to run close to that audience

56
00:02:46,360 --> 00:02:50,140
so that you can deliver
the lowest latency.

57
00:02:50,140 --> 00:02:53,420
If you don't have an audience
that you're worried about,

58
00:02:53,420 --> 00:02:54,930
if you're not really
worried about latency,

59
00:02:54,930 --> 00:02:56,250
then you may look at it

60
00:02:56,250 --> 00:02:59,300
from a purely cost savings perspective.

61
00:02:59,300 --> 00:03:01,760
Another reason we might choose one region

62
00:03:01,760 --> 00:03:05,430
is because we need to
consider data sovereignty

63
00:03:05,430 --> 00:03:08,280
and laws and compliance
around data sovereignty.

64
00:03:08,280 --> 00:03:13,280
Certain countries in certain
regions like the EU for example

65
00:03:13,360 --> 00:03:15,550
have certain laws regarding

66
00:03:16,630 --> 00:03:17,840
certain types of data

67
00:03:17,840 --> 00:03:21,020
whether it can leave that
particular geographic region

68
00:03:21,020 --> 00:03:23,240
or not, so you may choose a region

69
00:03:23,240 --> 00:03:26,660
that satisfies security
and compliance, right?

70
00:03:26,660 --> 00:03:29,090
So those are the regions
that are available,

71
00:03:29,090 --> 00:03:32,500
and those are some of the
reasons why we might choose

72
00:03:32,500 --> 00:03:33,923
one region over another.