1
00:00:06,379 --> 00:00:10,669
- Alright, now let's talk
about AWS Direct Connect.

2
00:00:10,669 --> 00:00:14,795
Direct Connect is a way
of getting direct access

3
00:00:14,795 --> 00:00:18,378
into an AWS region over
private networking.

4
00:00:19,367 --> 00:00:22,347
In many situations we have the need for

5
00:00:22,347 --> 00:00:25,034
on-premise applications or data

6
00:00:25,034 --> 00:00:28,716
to get to and from Amazon
Web Services region

7
00:00:28,716 --> 00:00:31,827
without going over the open internet.

8
00:00:31,827 --> 00:00:35,248
Maybe we need greater bandwidth
and better performance

9
00:00:35,248 --> 00:00:37,444
and we can get that
with the Direct Connect.

10
00:00:37,444 --> 00:00:39,342
Direct Connect comes in two options,

11
00:00:39,342 --> 00:00:43,887
being a one gig or a 10
gigabit per second connection.

12
00:00:43,887 --> 00:00:47,447
We can have one Direct Connect connection

13
00:00:47,447 --> 00:00:50,990
terminate into one or multiple VPCs.

14
00:00:50,990 --> 00:00:54,128
Now in order to establish this connection,

15
00:00:54,128 --> 00:00:56,476
we would provide our LOA-CFA

16
00:00:56,476 --> 00:00:59,181
to whatever vendor is local to us.

17
00:00:59,181 --> 00:01:03,547
In many cases, that might
be AT&T, Level 3, Equinix,

18
00:01:03,547 --> 00:01:05,004
the list goes on.

19
00:01:05,004 --> 00:01:05,837
There's a number of providers.

20
00:01:05,837 --> 00:01:08,332
It just depends on where
you are in the country

21
00:01:08,332 --> 00:01:10,036
or around the world.

22
00:01:10,036 --> 00:01:13,165
Another great benefit besides
the increased bandwidth,

23
00:01:13,165 --> 00:01:14,932
the consistent network performance,

24
00:01:14,932 --> 00:01:18,873
is that we should keep in
mind that data transfer

25
00:01:18,873 --> 00:01:22,982
out of AWS, whether it's
data leaving a load balancer,

26
00:01:22,982 --> 00:01:25,311
it's data leaving Simple Storage Service,

27
00:01:25,311 --> 00:01:29,478
or leaving DynamoDB, we pay
for all outgoing bandwidth,

28
00:01:30,397 --> 00:01:33,754
and so if we have
bandwidth coming out of S3

29
00:01:33,754 --> 00:01:35,901
and going back to our corporate network

30
00:01:35,901 --> 00:01:37,969
or out co-location facility,

31
00:01:37,969 --> 00:01:40,776
we could see a lower data transfer rate

32
00:01:40,776 --> 00:01:43,429
by using Direct Connect.

33
00:01:43,429 --> 00:01:46,379
So in this example we're seeing

34
00:01:46,379 --> 00:01:48,546
our corporate data center,

35
00:01:49,862 --> 00:01:53,435
this could be our on-premise
network at our headquarters,

36
00:01:53,435 --> 00:01:56,595
this could be our data
center or a co-location,

37
00:01:56,595 --> 00:01:59,088
and we have a Direct Connect,

38
00:01:59,088 --> 00:02:00,898
and this particular Direct Connect

39
00:02:00,898 --> 00:02:03,395
we would divide into multiple VLANs

40
00:02:03,395 --> 00:02:05,978
where each VLAN terminates into

41
00:02:06,864 --> 00:02:10,614
a separate virtual
gateway attached to a VPC.

42
00:02:11,714 --> 00:02:14,131
So we're leveraging one Direct Connect

43
00:02:14,131 --> 00:02:17,297
to gain access to multiple VPCs.

44
00:02:17,297 --> 00:02:20,293
So again, Direct Connect
is a really great way

45
00:02:20,293 --> 00:02:23,806
to achieve a private, dedicated connection

46
00:02:23,806 --> 00:02:26,139
directly into an AWS region.