网络课程笔记

00:00 Hello and welcome to this lecture.

00:01 Now that we understood

00:02 different types of Direct Connect connections,

00:05 that is dedicated connection and hosted connection,

00:10 and there is a slight variant

00:12 when it comes to the hosted VIF,

00:14 now let's try to understand which are the steps involved

00:18 in setting up this connection.

00:19 So if you want to set up this connection,

00:22 what are the steps you would have to follow?

00:24 Now this is important for your exam

00:26 because I have seen the cases

00:28 where some of the steps are given

00:30 and it is asked that what would be the next step

00:32 in the Direct Connect connection setup,

00:34 so let's try to understand this here.

00:38 As we know, there are two types of the connection,

00:40 dedicated and hosted,

00:42 so I'm not going to go through this again.

00:44 Now let's pick up the dedicated connection

00:47 and let's see what are the sequence of the events.

00:49 So this is overall the architecture.

00:51 Looks like you have AWS VPCs

00:54 and your accounts on one side,

00:56 corporate data center on the other side,

00:57 and then Direct Connect location in between,

01:00 and then you have customer router here

01:02 and AWS Direct Connect router here

01:04 and then you establish this connectivity end-to-end.

01:07 That is what the dedicated connection is.

01:10 So with respect to the steps it takes,

01:13 let's try to understand.

01:15 First, you select AWS region

01:17 where you want your Direct Connect connection,

01:19 then you select Direct Connect location,

01:21 and then submit the connection request

01:23 via AWS console or a CLI or an API.

01:26 You can do that and in the later lecture,

01:28 I will show you that as well.

01:30 So that is something you have to initiate via AWS console.

01:35 Once you make that request in AWS console,

01:38 AWS takes up to 72 hours to provision that port for you

01:43 at given Direct Connect location.

01:45 And additionally, AWS provides you

01:47 something called LOA-CFA.

01:49 That is a Letter of Authorization

01:51 Connection Facility Assignment.

01:54 Now what is LOA-CFA?

01:55 This is something you need to provide

01:58 to your Direct Connect location provider

02:00 so that they can allocate that port

02:03 and make the cross-connect

02:04 between AWS router and your router.

02:07 So this is an important digital document

02:11 which you need to provide to prove that you own that port

02:14 and then required details it has

02:17 like where is AWS side of the router.

02:21 Now, LOA contains the demarcation details

02:24 of the assigned port within the facility.

02:26 So Direct Connect location provider also knows

02:28 this is a port which is allocated to you.

02:32 If your organization has physical presence in DX location,

02:35 that means you already have your router,

02:37 then you can request the cross-connect within the facility

02:40 to connect to AWS device.

02:42 That means there is no additional router

02:43 needs to be set up there

02:45 because you already have your routers there.

02:47 Then the Direct Connect location provider

02:49 will make that cross-connect request and that's it,

02:53 your connection is established.

02:55 But if you do not have your router there

02:59 in the Direct Connect facility,

03:01 then what you can do is you can provide your LOA copy

03:04 to Direct Connect APN partner

03:07 and then APN partner can place the router

03:10 as well as cross-connect request on behalf of you.

03:15 Once that is done, you have to make sure

03:17 that you are receiving the good Tx/Rx optical signals

03:22 at your equipment.

03:23 Now what is Tx/Rx?

03:24 These are like transmit and receive signals.

03:26 They are the digital signal processor signals

03:29 which are sent by the router

03:33 and these are typically measured in decibels per milliwatt

03:36 and traditionally minus 18 to minus 25

03:40 decibels per milliwatt is good signal.

03:42 And if it goes beyond this range,

03:45 then it is called signal-to-noise ratio

03:46 and cannot be considered as good signal

03:48 which can carry your data through the Direct Connect pipe.

03:51 So you have to make sure

03:53 that you are receiving that Tx/Rx signal

03:55 and you can also see that in the CloudWatch as well

03:58 that we will cover when we see monitoring DX connection.

04:01 Now you can create private or public virtual interfaces

04:05 on top of this Direct Connect connection

04:07 and then you can start accessing the AWS services

04:10 from your on-premises network.

04:13 Now, if the same thing has to be shown here,

04:15 this is what the setup look like.

04:17 There is an AWS account which you own or a customer owns.

04:21 Customers first go to the AWS console

04:24 and make a connection request.

04:25 Now, this connection request looks something like this.

04:28 You would put some name there

04:30 and the location based on your region and the port speed

04:34 which would be one or 10 or 100 Gbps port speed.

04:38 Once you select that,

04:39 you get something called a port allocated

04:43 in the AWS Direct Connect router

04:45 in a given Direct Connect location that you selected

04:48 and also AWS give you the copy of LOA-CFA.

04:53 Now what you need to do

04:54 is based on whether you have your own router here or not,

04:57 you will take this LOA copy

04:59 and this LOA would have all the details which it needs

05:02 to make the cross connection at the Direct Connect location.

05:06 So all these details are there.

05:08 Once you have this,

05:10 you just have to contact your Direct Connect provider.

05:13 Now based on which Direct Connect location you selected,

05:15 there are the email IDs of those providers.

05:17 So you can send or share this LOA-CFA

05:20 with the Direct Connect provider at a given email ID.

05:24 So this LOA will be shared with the Direct Connect provider.

05:27 And based on whether you have your router

05:30 or if you can talk to Direct Connect APN partner

05:34 and get their router here,

05:36 and once that router is established,

05:38 the Direct Connect location provider

05:39 will make a cross-connect between AWS router

05:43 and the port that has been allocated to you

05:45 and between this router.

05:47 Once that is turned, you are responsible for setting up

05:50 this connectivity from router to on-premise data center.

05:53 Again, either you can do it yourself

05:55 or you can also have your other ISP partner

05:59 who can establish this connectivity.

06:02 Once that is done, you can create virtual interfaces

06:05 and you can access AWS services from there.

06:08 So this is end-to-end physical connectivity

06:10 and you have to establish, of course, the BGP routing

06:14 and we'll talk about how to set that up later,

06:17 but BGP routing is established.

06:19 That means now traffic can actually flow

06:21 from on-premise data center to AWS.

06:25 So that's it.

06:26 Your connection gets successful

06:27 and that's how the dedicated connection is set up.

06:30 I hope that is clear.

06:32 Now let's try to see the steps involved

06:35 in hosted connection.

06:36 Now as you know, in hosted connection,

06:38 connection is already there.

06:40 It is being managed by your Direct Connect partner.

06:43 That means you don't have to create the connection

06:46 in AWS console.

06:47 You don't have to get that LOA-CFA copies.

06:50 It has been already taken care.

06:51 What you request to your partner

06:53 is to just give you hosted connection

06:56 on top of your partner's existing connection.

07:00 So in case of hosted connection,

07:01 the sequence of events would follow like this.

07:05 To order the hosted connection,

07:07 of course, you don't need LOA,

07:09 so you can directly contact the Direct Connect partner

07:11 to order the connection.

07:13 What you give to your partner

07:14 is your 12-digit account number

07:16 and also tell them what is the bandwidth

07:20 that you're looking for.

07:22 Then what partner will do

07:23 is it will set up the hosted connection

07:25 and this connection will be available in your account

07:28 in a given region to accept it.

07:30 So what you will see in your AWS account is a connection

07:33 which you need to accept first.

07:35 And then once you accept it, it starts billing.

07:37 So that's one important point.

07:39 As soon as you accept that connection,

07:41 it will start billing for the Direct Connect charges.

07:44 So once you accept connection, it enables the billing

07:46 and port hour charges and data transfer charges

07:49 would be applicable for that point of time.

07:52 Now with respect to the dedicated connection

07:54 we just talked earlier, AWS will wait for maximum 90 days

07:59 from the start of the billing.

08:00 If you don't complete this connection end-to-end,

08:03 you still get a 90 days window.

08:06 After 90 days, if you still have the connection there,

08:09 it will start billing for the port hours.

08:11 Of course, there won't be data transfer charges

08:13 because there is no connectivity end-to-end,

08:15 so no data can flow, but you still pay for those port hours.

08:20 So better if you are not using your dedicated connection,

08:23 you accidentally created it,

08:24 then just go and delete your connection there.

08:28 Similarly steps would be something like this

08:31 for hosted connection.

08:32 You have Direct Connect partner here

08:35 which you can select from the APN and what you will do

08:38 is you will request the hosted connection

08:43 by providing your 12-digit account number

08:46 and this AWS partner will create a hosted connection for you

08:50 and that connection will be available in your AWS account

08:54 as a pending acceptance.

08:56 So this connection would look something like this,

08:58 it would have detail

08:59 like what is my Direct Connect location, what is the speed,

09:02 it's a 50 Mbps connection here,

09:05 there will be VLAN assignment

09:07 and we'll talk more about that shortly,

09:09 but then all the details are here.

09:11 Once you accept this connection, then that's it.

09:14 That's it you have to do.

09:16 The router will be a partner router there

09:18 and there will be a port allocated automatically

09:21 by the partner.

09:22 And finally, you accept the request

09:25 and there is a cross-connect done

09:27 between this router and AWS router.

09:29 Then it is assumed that you already have connectivity

09:32 from your data center to partner router.

09:34 If not, you would again have to set that connection up,

09:38 either the same partner can do it

09:40 or your ISP can also do that.

09:44 Now, once that is done, you can create a private VIF

09:47 on top of your hosted connection.

09:49 As I said, only one VIF can be created

09:51 per hosted connection.

09:52 So if you want to create a public VIF on top of here,

09:55 you would have to take another hosted connection here.

10:00 Okay, so that's it

10:01 about the hosted connection sequence of events.

10:04 Now let's look at the hosted VIF.

10:06 Okay, so first thing first,

10:08 don't get confused with hosted connection and hosted VIF.

10:12 The hosted connection, as you know,

10:15 it is created by Direct Connect partner

10:18 and then it appears into your AWS account

10:21 because Direct Connect partners

10:23 share that connection with you.

10:26 And this is typically done because you don't want

10:28 probably one Gbps of Direct Connect connection.

10:32 You need some sub-one Gbps connection

10:35 and what Direct Connect partner does,

10:37 it might have say one gigabit connection already

10:40 as a dedicated connection

10:42 and then it can split that bandwidth

10:44 and provide maybe 1,000 Mbps connection to 10 customers.

10:49 Likewise, you can have one sub-Gbps connection

10:52 into your account, so that's a hosted connection.

10:55 But in case of hosted VIF, it doesn't really matter

10:59 whether it's a hosted connection or a dedicated connection.

11:02 We are talking about the VIF

11:03 that we create on top of this connection.

11:06 Now in this case, the connection owner is one AWS account,

11:11 but the VIF owner is someone else.

11:13 So you can create a VIF and then you say

11:16 this VIF is owned by another AWS account.

11:20 Now why you would do this?

11:22 Imagine a situation where you have

11:23 centralized networking team

11:25 who owns all Direct Connect connections

11:28 and then different projects inside the organization

11:31 need a connectivity to on-premise network and AWS.

11:35 In that case, you could have your own dedicated connection

11:38 or a hosted connection

11:39 and this account is owned by the networking team,

11:42 but then every project would have their own AWS account

11:46 and the networking team can then create a VIF

11:48 and say the owner of this VIF is project one team

11:52 or project two team.

11:53 In that case, that team still owns the VIF,

11:56 but the connection is owned

11:58 by the centralized networking IT team.

12:01 So as I said, when you create a VIF,

12:03 you choose another AWS account who owns that VIF.

12:08 Now with respect to the functionality and the connectivity,

12:12 it does exactly same as with the public virtual interface

12:15 or a private virtual interface.

12:17 That means you can connect to AWS public resources like S3

12:21 or you can create a private VIF

12:23 and can connect to AWS VPC.

12:26 And we already talked

12:28 that the connection is owned by one account

12:30 and the VIF is owned by another account.

12:32 However, the VIF owner has to accept that VIF

12:35 into his or her AWS account.

12:38 You can't just create a VIF

12:39 and then it will appear into someone else account.

12:42 It's not really the right thing to do.

12:45 So the VIF owner has to accept it.

12:49 And finally, it is used in the scenarios where, as I said,

12:52 networking team manages the DX connection

12:54 and provides the VIF as a service to the project teams.

12:58 So that essentially is the hosted VIF.

13:01 Okay, almost similar architecture just that AWS account here

13:06 which is your central IT team account

13:08 probably is the connection owner.

13:11 Now, this connection could be dedicated connection

13:13 or a hosted connection,

13:15 does not really matter for other business units,

13:18 but what they can do is they can request the VIFs

13:21 into their account,

13:22 so the account owner here with a central IT team here

13:26 will create a VIF into your account

13:29 by providing your account ID,

13:30 and then you would have to accept that VIF connection

13:33 into your AWS account.

13:35 Once that is done,

13:36 the VIF is created on the same Direct Connect connection

13:40 and then you can then access the on-premise network

13:43 from this AWS region and the VPC.

13:47 So in a nutshell, that is the step to create a hosted VIF.

13:52 And I think that's it for this lecture.

13:54 So we saw three scenarios, the steps involved in creating

13:58 dedicated Direct Connect connection,

14:01 the hosted Direct Connect connection, and then hosted VIF.

14:05 So understand the differences between these three

14:07 because in some cases,

14:09 you will find the questions which involves like LOA-CFA

14:14 in which case it would be applicable.

14:16 So as you can see,

14:17 it is applicable only in case of the dedicated connection.

14:20 So that's it about this lecture.

14:21 Now, in the next lecture, we'll actually see in the console

14:24 how this flow looks like,

14:25 though we won't be able to create an actual connection,

14:28 but at least we'll walk you through the steps there.

14:30 So stay tuned and thanks for watching.