Lecture 143: DX Pricing
- 课程：[NEW] AWS Certified Advanced Networking Specialty 2026
- 视频时长：17:40
- 来源：Udemy Lecture 27898902
- Slide 数量：41
- 画面切换：00:35、01:24、02:07、02:51、03:06、03:31、04:07、05:14、05:36、05:41、05:44、05:46、05:49、05:52、06:01、06:13、06:18、06:39、06:42、07:15、07:25、08:53、08:56、09:19、09:56、11:06、11:11、12:07、14:39、14:45、14:49、15:08、15:18、15:51、16:16、16:17、16:25、16:45、17:01、17:14
扫描说明
逐条检查了 Udemy 页面中的 411 条 Transcript cue，并扫描了全长约 17:40 的视频。该讲包含 Direct Connect 计费拓扑、端口小时与数据传出计费表、三组区域/位置示例、多账户责任、Transit Gateway 特例、总结和知识检查；按每张新幻灯片及每次有意义的文本或图示渐显，共划分为 41 个小节。最终截图均在精确 Transcript cue 暂停后关闭侧栏、恢复完整横向播放器并将指针移出媒体区域；41 张图片均无黑边、无顶部课程栏、无底部或中心播放器控件，也无右侧或下方裁切，并统一输出为 1364×770。
Transcript 来自 Udemy 页面自带的英文自动字幕，没有使用 ASR。下面保留页面原文，包括其中的语法或识别错误。
1. Direct Connect Billing 概览
时间范围：00:00–00:35
总结 / Summary
中文
Direct Connect（DX）计费涉及多个费用组件；在多账户架构（Multi-Account Architecture）中，还必须判断每项费用由哪个 AWS 账户承担。
English
Direct Connect billing has multiple charge components, and a multi-account architecture adds the question of which AWS account pays each charge.
Transcript
00:00 Hello, and welcome to this lecture,
00:02 Direct Connect Billing.
00:03 Now, this is one of the most confusing topic, I would say,
00:05 when it comes to the Direct Connect Billing.
00:08 And that is essentially because, there are multiple
00:11 components involved in Direct Connect Billing.
00:13 And further, if you add the complexity
00:16 of multi account setup,
00:18 then it becomes more challenging to know,
00:21 who pays for what.
00:22 And, let's try to understand this.
00:25 And also for your exam,
00:27 you might have one odd question
00:29 on Direct Connect Billing.
00:31 So, please be attentive for this lecture.
2. DX 计费拓扑与参与组件
时间范围：00:35–01:24
总结 / Summary
中文
Direct Connect（DX）把 AWS 区域（AWS Region）中的 VPC 或公共服务，经 DX 位置（DX Location）的端口连接到客户路由器（Customer Router）；端口和跨链路流量构成主要计费基础。
English
Direct Connect links VPCs or public AWS services to a customer router through ports at a DX location; the port and traffic crossing the link form the basis of billing.
Transcript
00:35 Okay, so when it comes to the Direct Connect,
00:37 you know what parties are involved,
00:39 there is AWS region,
00:41 which is connected to on-premise data center
00:44 via the Direct Connect location, right?
00:47 And in Direct Connect location,
00:49 you have, routers allocated to you.
00:52 And on those routers, you need to get port,
00:55 and those ports are used by your Direct Connect connection.
00:58 Now, on AWS side, you would have
01:00 either the private IP addresses like VPC,
01:05 or AWS public services like S3,
01:08 or public EC2 instances,
01:08 which can send and receive traffic
01:13 from on-premise network.
01:14 Now in all this, what are the charges
01:16 that you have to pay when you go for a Direct Connect.
01:19 So in case of Direct Connect, there are multiple charges,
01:22 very first charge is, port-hour charges.
3. 端口小时费用
时间范围：01:24–02:07
总结 / Summary
中文
端口小时费用（Port-Hour Charges）取决于连接容量以及连接是专用连接（Dedicated Connection）还是托管连接（Hosted Connection）；连接可用后即使没有流量也会持续计费。
English
Port-hour charges depend on connection capacity and whether the connection is Dedicated or Hosted. Once available, the connection incurs charges even when it carries no traffic.
Transcript
01:24 And the port-hour charges would
01:26 obviously depend on the capacity
01:28 of your Direct Connect connection.
01:30 That means, whether you go for 1Gbps link
01:32 or 10 Gbps link,
01:34 accordingly, there will be per our port-hour charges.
01:38 Now, once you get your connection and it is available,
01:41 irrespective of whether you send it or not,
01:45 the port-hour charges will be applicable
01:46 till the time your connection is there, right?
01:50 So of course, port-hour charges are there.
01:52 And the charges will also depend on the capacity
01:56 as well as whether the connection is a
01:58 dedicated connection or a hosted connection.
02:01 So, that's first type of the charge for DX.
02:04 And the second type of the charge is,
4. 数据传出费用
时间范围：02:07–02:51
总结 / Summary
中文
数据传出费用（Data Transfer Out，DTO）按 GB 计算，适用于从 AWS 流向本地网络的流量，并取决于 DX 位置（DX Location）和源 AWS 区域（Source AWS Region）；数据传入（Data Transfer In）免费。
English
Data Transfer Out is charged per GB for traffic moving from AWS to the on-premises network, with the rate determined by the DX location and source AWS Region. Data Transfer In is free.
Transcript
02:07 of course, the data transfer out charges.
02:10 Now, when we say data charges out means,
02:12 any data that is going from AWS to on-premise network,
02:17 or to Direct Connect location, right?
02:20 That's a data transfer out.
02:22 And which also means, there is no charge
02:24 for data transfer IN.
02:25 So, the data transfer charges are calculated per GB.
02:31 That means how much data you sent.
02:33 And, it would also depend on the DX location,
02:37 as well as source AWS region.
02:40 So, I hope that it's clear,
02:41 like there are two type of the charges for DX,
02:44 one is port-hour charges
02:46 and second is, data transfer out charges.
02:49 So with that, now let's get into the
5. 两类 DX 费用汇总图
时间范围：02:51–03:06
总结 / Summary
中文
Direct Connect（DX）的核心费用分为端口小时费用（Port-Hour Charges）和数据传出费用（Data Transfer Out Charges）两类。
English
The two core Direct Connect charge categories are port-hour charges and Data Transfer Out charges.
Transcript
02:51 next part, which is, port hour charges,
02:54 how they're calculated and how much you have to pay.
02:57 Now, as you know,
02:58 the port hour charges depends on the capacity
03:01 as well as, whether the connection is a dedicated
03:04 and a hosted connection.
6. Dedicated Connection 端口价格
时间范围：03:06–03:31
总结 / Summary
中文
专用连接（Dedicated Connection）的端口小时费率通常在各 DX 位置一致，日本除外；费率随 1、10、100 Gbps 等容量增加。
English
Dedicated Connection port-hour rates are generally consistent across DX locations except Japan, and increase with capacities such as 1, 10, and 100 Gbps.
Transcript
03:06 So for dedicated connection,
03:07 the port-hour charges are pretty much consistent
03:16 across all location.
03:13 So for 1GB, it is, $0.30 per hour.
03:16 And similarly, for other capacity connections.
03:20 Now, this is different for Japan,
03:22 but, otherwise for every other DX location,
03:26 this is a same price.
03:28 And now, if you look at the hosted connection,
7. Hosted Connection 端口价格
时间范围：03:31–04:07
总结 / Summary
中文
托管连接（Hosted Connection）还提供低于 1 Gbps 的容量；其端口小时费率同样按容量变化，并通常在各位置一致，日本除外。
English
Hosted Connections add sub-1-Gbps capacities. Their port-hour rates also vary by capacity and are generally consistent across locations except Japan.
Transcript
03:31 which comes into the sub 1Gbps capacity as well,
03:35 it is also consistent across all AWS regions
03:38 and Direct Connect location, except Japan.
03:41 So,
03:43 for 50 mega bits per second, it is 0.03 per hour.
03:47 And accordingly, the charges are there.
03:50 Now, again, you don't need to remember these numbers,
03:53 but, understand that the port-hour charges
03:55 are pretty much consistent,
03:57 irrespective of which AWS Direct Connect location
04:00 you are using.
04:02 Now with that, let's move to the data transfer charges now.
8. Data Transfer 费率表
时间范围：04:07–05:14
总结 / Summary
中文
数据传入（Data Transfer In）为每 GB 0 美元；数据传出（Data Transfer Out）费率由源 AWS 区域（Source AWS Region）与目的 DX 位置（Destination DX Location）的组合决定。
English
Data Transfer In costs $0 per GB, while the Data Transfer Out rate is determined by the combination of source AWS Region and destination DX location.
Transcript
04:07 As you know, data transfer charges IN,
04:09 it is free.
04:10 So, no charges for any size of the data
04:13 that is coming from on premise data center to AWS,
04:17 but there is a data transfer OUT charges.
04:19 And as I said,
04:21 it would depend on which DX location the
04:24 data is going to,
04:26 and from which source AWS region.
04:28 Now, if you look at here,
04:31 AWS Direct Connect location is in, say, United States,
04:34 and the data transfer source region is one of these,
04:39 then you pay for $0.0200 per GB.
04:43 So, you can very well go to the AWS page
04:46 and there you will also see the list of
04:48 all DX location, and the source AWS region,
04:51 there is another table for that,
04:53 but in a simplified way,
04:55 depending on where your Direct Connect location is,
04:58 and which is the source AWS region,
05:00 which is sending data to this DX location,
05:02 the charges would be applied.
05:05 So, I hope that is clear.
05:07 And now, let's look at some of the examples of
05:11 this DX charges.
9. DX 端口与 DTO 示例拓扑
时间范围：05:14–05:36
总结 / Summary
中文
示例把 VPC、S3 和 DynamoDB 通过专用连接（Dedicated Connection）接入 DX 位置（DX Location），分别观察端口小时费用（Port-Hour Charges）和数据传出费用（DTO）。
English
The example connects a VPC, S3, and DynamoDB to a DX location over a Dedicated Connection to separate port-hour charges from DTO charges.
Transcript
05:14 So, in a simplified manner,
05:15 you have DX location and you have
05:18 AWS VPCs or public services.
05:21 Now in this case, so obviously the port-hour will be charged
05:24 based on your capacity and DTO, that is,
05:27 Data Transfer Out, charges will be
05:29 depending on the source AWS region,
05:31 as well as DX location.
05:33 Now, for dedicated connection,
10. 示例中的端口小时费率
时间范围：05:36–05:41
总结 / Summary
中文
专用连接（Dedicated Connection）的端口小时费按连接容量计收；示例列出 1、10、100 Gbps 的对应小时费率。
English
The Dedicated Connection incurs a port-hour rate based on its capacity; the example lists rates for 1, 10, and 100 Gbps.
Transcript
05:36 the port-hour charges would look something like this.
05:39 As we already saw,
11. Data Transfer In 方向
时间范围：05:41–05:44
总结 / Summary
中文
从本地网络进入 AWS 的数据传入（Data Transfer In）方向被单独标出，以区分后续的数据传出（Data Transfer Out）。
English
The example identifies the Data Transfer In direction from the on-premises network into AWS, distinguishing it from outbound transfer.
Transcript
05:41 and, data transfer IN charge, there is nothing,
12. Data Transfer In 免费
时间范围：05:44–05:46
总结 / Summary
中文
数据传入（Data Transfer In）不收费，而数据传出（Data Transfer Out）需要按源区域和 DX 位置计算费率。
English
Data Transfer In has no charge, while Data Transfer Out is priced according to the source Region and DX location.
Transcript
05:44 and for data transfer OUT, as I said,
13. DTO 依赖源 AWS Region
时间范围：05:46–05:49
总结 / Summary
中文
计算数据传出费用（DTO）时，首先要识别发送流量的源 AWS 区域（Source AWS Region）。
English
Calculating DTO first requires identifying the source AWS Region that sends the traffic.
Transcript
05:46 it would depend on the source AWS region.
14. 示例源区域：N. Virginia
时间范围：05:49–05:52
总结 / Summary
中文
第一组示例把源 AWS 区域（Source AWS Region）设为 N. Virginia，为后续匹配目的 DX 位置和费率做准备。
English
The first example sets N. Virginia as the source AWS Region before matching it to a destination DX location and rate.
Transcript
05:49 So for example, if source region is not Virginia,
15. 示例目的位置：Las Vegas
时间范围：05:52–06:01
总结 / Summary
中文
源区域 N. Virginia 的流量通过 Las Vegas 的 DX 位置（DX Location）传出，费率由这组源/目的地组合决定。
English
Traffic from N. Virginia exits through the Las Vegas DX location, so the source/destination pair determines the rate.
Transcript
05:52 and the destination DX location is Las Vegas,
05:56 then the data transfer OUT charges are $0.02 per GB.
16. N. Virginia → Las Vegas：$0.0200/GB
时间范围：06:01–06:13
总结 / Summary
中文
示例中 N. Virginia 到 Las Vegas DX 位置的数据传出费用（DTO）为每 GB 0.0200 美元。
English
In the example, DTO from N. Virginia to the Las Vegas DX location costs $0.0200 per GB.
Transcript
06:01 So, this is just one example.
06:03 Now, if you just change your AWS Direct Connect location,
06:07 and maybe you want to keep the source as
06:09 same as North Virginia region,
06:11 but now you are sending the data
17. 改用 Mumbai DX Location
时间范围：06:13–06:18
总结 / Summary
中文
保持源区域 N. Virginia 不变，将目的 DX 位置（Destination DX Location）改为 Mumbai，会因地理路径变化而使用不同费率。
English
Keeping N. Virginia as the source but changing the destination DX location to Mumbai produces a different rate because the geographic path changes.
Transcript
06:13 to a Direct Connect location in Mumbai,
06:16 then, your per hour
18. N. Virginia → Mumbai：$0.0600/GB
时间范围：06:18–06:39
总结 / Summary
中文
示例中 N. Virginia 到 Mumbai DX 位置的数据传出费用（DTO）为每 GB 0.0600 美元，高于同一地理区域内的路径。
English
In the example, DTO from N. Virginia to the Mumbai DX location costs $0.0600 per GB, higher than a path within the same geography.
Transcript
06:18 data transfer OUT charges would be $0.06.
06:21 And this is probably obvious because,
06:23 the distance between the US and India is
06:26 quite more than if you're using the DX location
06:29 in the same geography as US.
06:32 So, depending on your source region and DX location,
06:36 data transfer charges will differ.
19. 第三组 DTO 区域组合
时间范围：06:39–06:42
总结 / Summary
中文
第三组示例把源 AWS 区域（Source AWS Region）改为 Ireland，并保留 Las Vegas DX 位置，说明费率矩阵必须同时考虑两端。
English
The third example changes the source AWS Region to Ireland while using the Las Vegas DX location, reinforcing that both endpoints matter in the rate matrix.
Transcript
06:39 With that, let's move to the next part.
20. Ireland → Las Vegas：$0.0200/GB
时间范围：06:42–07:15
总结 / Summary
中文
课件示例为 Ireland 源区域到 Las Vegas DX 位置标出每 GB 0.0200 美元的数据传出费用（DTO），随后引出费用归属问题。
English
The slide shows a $0.0200-per-GB DTO rate from Ireland to the Las Vegas DX location, then transitions into the question of who pays.
Transcript
06:42 Who pays for DX charges?
06:44 So far,
06:45 we are just talking about different charges,
06:47 but actually, which AWS account pays for these charges.
06:51 Now, if it is just an
06:53 single AWS account, who owns the connection,
06:56 who owns your VIFs,
06:57 who owns the VPCs and the resources inside VPC,
07:01 of course, all these charges
07:03 will be applicable to a single AWS account.
07:06 But in real life,
07:07 typically that's not always the case.
07:09 You might have multiple AWS accounts
07:11 coming into the picture.
07:12 And in that case,
07:13 you need to see, who pays for what.
21. 谁承担 DX 费用？
时间范围：07:15–07:25
总结 / Summary
中文
在多账户场景中，必须分别判断哪个账户拥有 Direct Connect 连接，以及哪个账户拥有发送流量的资源。
English
In a multi-account design, determine separately which account owns the Direct Connect connection and which account owns the resource sending traffic.
Transcript
07:15 So let's look at those things now.
07:18 First of all, port-hour charges.
07:20 Now, this is pretty simple.
07:22 The account that owns the Direct Connect connection,
22. 连接所有者支付 Port-Hour
时间范围：07:25–08:53
总结 / Summary
中文
拥有并请求 Direct Connect 连接的 AWS 账户承担端口小时费用（Port-Hour Charges），无论连接是专用连接（Dedicated）还是托管连接（Hosted）。
English
The AWS account that owns and requested the Direct Connect connection pays the port-hour charges, whether the connection is Dedicated or Hosted.
Transcript
07:25 that is the account which requested the connection,
07:28 pays for the port-hour charges.
07:30 So, whether it's a dedicated connection
07:32 or whether it's a hosted connection,
07:35 the account with requested that connection
07:37 will pay for port-hour charges.
07:40 Now, you need to understand that
07:42 when it's a dedicated connection,
07:44 you request for a connection and then you get LOA CFA,
07:48 that you submit it to your Direct Connect partner,
07:51 or a Direct Connect location provider.
07:53 And then, the location provider will do the cross connect,
07:57 and then your connection will be available.
07:59 Now, in case, if you just request the connection,
08:02 you see that in your console,
08:04 it would be in the downstate initially.
08:06 And if you don't proceed with all these next steps,
08:10 in that case, will you be charged for port-hours or not?
08:13 So, the rule of thumb is, for dedicated connection,
08:18 you will be charged as soon as your connection
08:21 is in available state.
08:23 That means, everything is set up,
08:24 you see the good lights on to the your connection,
08:28 and the traffic can start flowing,
08:30 that means connection is available
08:31 and you start paying from that moment.
08:31 Now, in case you don't proceed with all this next step,
08:37 and the connection is in downstate,
08:40 you will be charged post 90 days.
08:43 Like, AWS gives you 90 days window
08:45 to complete this setup.
08:47 If you don't do that in that window,
08:49 you will be charged after 90 days of connection request.
23. Dedicated Connection 起始计费时间
时间范围：08:53–08:56
总结 / Summary
中文
专用连接（Dedicated Connection）在进入 Available 状态时开始端口小时计费；若未完成连接设置，AWS 仍会在请求后 90 天开始计费。
English
A Dedicated Connection starts port-hour billing when it becomes Available; if setup is not completed, billing still begins 90 days after the request.
Transcript
08:53 So just remember this.
08:53 Now, in case of hosted connection,
24. Hosted Connection 接受后开始计费
时间范围：08:56–09:19
总结 / Summary
中文
托管连接（Hosted Connection）由 Direct Connect 合作伙伴创建，客户账户接受连接请求后立即开始端口小时计费。
English
A Hosted Connection is created by a Direct Connect partner, and port-hour billing begins as soon as the customer account accepts the request.
Transcript
08:56 as soon as you accept the connection request,
08:59 your billing starts.
09:01 Because, in case of hosted connection,
09:03 connection is owned by Direct Connect partner.
09:06 And then you request your Direct Connect partner
09:08 to give you, say, 50 Mbps connection.
09:10 So, Direct Connect partner will create
09:13 a hosted connection for you,
09:14 which will be available in your AWS console to accept.
09:17 Now, the moment you accept the connection,
25. Down 状态不会停止计费
时间范围：09:19–09:56
总结 / Summary
中文
仅当专用或托管连接从 AWS 账户中删除后，端口小时计费（Port-Hour Billing）才停止；连接处于 Down 状态并不会终止费用。
English
Port-hour billing stops only when the Dedicated or Hosted Connection is deleted from the AWS account; a Down state does not stop charges.
Transcript
09:19 the billing will start for that connection.
09:21 Also, you need to understand that,
09:23 the billing for port-hour stops
09:25 when the dedicated connection or hosted connection
09:27 is deleted from your AWS account,
09:30 which means, if it is just in a downstate,
09:32 does not mean that there is no charge, right?
09:35 So, you have to explicitly go and delete that connection.
09:39 Now, in case of hosted connection,
09:41 you would ask your Direct Connect partner to disable
09:45 your hosted connection.
09:46 And then, you will be stopped billing for that.
09:49 So, this is about the port-hour charges.
09:51 The bottom line is,
09:52 the account owner who requests the Direct Connect connection
26. Data Transfer Out 费用归属
时间范围：09:56–11:06
总结 / Summary
中文
数据传出费用（DTO）通常由拥有发送流量资源的账户承担；连接可由账户 1 拥有，而 VIF、EC2 或 S3 资源由账户 2 拥有。
English
DTO charges are usually allocated to the account that owns the resource sending traffic; Account 1 can own the connection while Account 2 owns the VIF, EC2 instance, or S3 bucket.
Transcript
09:56 pays for this port-hour charges.
09:58 Now let's look at the complex part of it,
10:01 who pays for Data Transfer Out charges?
10:03 Now, generally speaking,
10:04 Data Transfer Out charges are usually located to the account
10:08 that owns the resource, sending the traffic.
10:10 Now let's understand what, what it means.
10:13 So, suppose there is a Direct Connect connection
10:15 between account 2 and account 1,
10:18 that means the connection is owned by account 1,
10:20 but the VIFs are part of the account 2.
10:24 And in this case,
10:26 EC2 machine is sending data or a private VIF,
10:29 or there is a connection to the S3,
10:31 and somebody is downloading data from the S3.
10:34 Now that is a outbound data,
10:36 which is going from S3, to the Direct Connect location,
10:39 to the on-premise network.
10:45 Now this is Data Transfer Out.
10:42 Now, in all these cases, the resource owner,
10:45 now in this case, account 2 owns the S3 bucket
10:48 or EC2 instance will pay for the Data Transfer Out charges.
10:52 And this Data Transfer Out charges would depend on again,
10:56 the source AWS region, as well as DX location.
10:59 We already saw that, but the point is who pays for that?
11:02 The resource owner will pay for the Data Transfer charges.
27. 资源账户 Account 2 支付 DTO
时间范围：11:06–11:11
总结 / Summary
中文
示例中资源位于账户 2，因此账户 2 支付数据传出费用（Data Transfer Out Charges），而不是拥有 DX 连接的账户 1。
English
Because the sending resources belong to Account 2, Account 2 pays the DTO charges rather than Account 1, which owns the DX connection.
Transcript
11:06 So, account 2 pays here for the Data Transfer Out
11:10 in this case.
28. 所有 VIF 的资源所有者规则与 S3 例外
时间范围：11:11–12:07
总结 / Summary
中文
公共、私有和中转虚拟接口（Public/Private/Transit VIF）通常都由资源所有者支付 DTO；S3 可启用请求者付费（Requester Pays），把费用转给访问数据的请求者。
English
For Public, Private, and Transit VIFs, the resource owner normally pays DTO. S3 can enable Requester Pays so the requester accessing the data pays instead.
Transcript
11:11 So, whether it's a public, private or transit VIF,
11:14 the resource owner will pay for the DTO.
11:17 Now, in case of S3,
11:19 there is an additional feature,
11:21 like you can enable the
11:23 Requester Pays flag on the S3 bucket.
11:27 Now, even if you own the S3 bucket,
11:29 so, obviously Data Transfer Out charges would be
11:33 applied to your AWS account,
11:34 but on S3 bucket, if you say Requester Pays,
11:37 then who were accessing your data,
11:40 over the Direct Connect via the S3,
11:43 pays for that Data Transfer Out charges.
11:45 Now, this is only the case, in case of S3,
11:48 but for rest of the resources,
11:50 the owner of the resource will pay
11:52 for the Data Transfer Out charges.
11:54 So, this is a pretty simple when it is a private VIF,
11:57 or a public VIF.
11:59 But again, there is some additional complexity,
12:02 if you are doing the data transfer over transit VIF.
12:05 Now, let's look at those things.
29. Transit Gateway 的 DTO 特例
时间范围：12:07–14:39
总结 / Summary
中文
流量经过中转网关（Transit Gateway，TGW）时，DTO 归属于流量到达 Direct Connect VIF 前最后一个发送资源的所有者。若 DX 连接和资源分属不同 AWS Organizations，则资源所有者按标准 AWS 服务数据传出费率（Standard AWS Service DTO Rate）计费，而非较低的 DX DTO 费率。
English
With Transit Gateway, DTO is allocated to the owner of the last resource that sends traffic before it reaches the Direct Connect VIF. If the connection and resource are in different AWS Organizations, the resource owner is charged the standard AWS service DTO rate rather than the lower DX DTO rate.
Transcript
12:07 So, in case of traffic is sent over through transit gateway,
12:12 then, Data Transfer Out is located
12:14 to the owner of the last resource,
12:16 to send traffic, before traffic hits the Direct Connect VIF.
12:19 Now, this is getting complex,
12:20 but let's try to understand that.
12:22 Now, suppose you have multiple VPCs, right?
12:25 And all these VPCs are connected to transit gateway.
12:28 And then there is a transit wave,
12:30 there is a Direct Connect gateway as well,
12:32 because you need to have that.
12:33 And then, there is a direct connect location, right?
12:37 Now, for security purpose, what you did is,
12:39 you set up one EC2 machine,
12:41 on which you have some network inspection tools,
12:44 and traffic from all VPCs first go to that EC2 instance,
12:50 and from there, it goes to the transit gateway
12:52 to the Direct Connect gateway,
12:55 to the Direct Connect location.
12:57 Now, in this case,
12:58 the resource owner of that EC2 machine,
13:03 on which you have the traffic inspection tool installed
13:06 will pay for the Data Transfer Out charges.
13:09 Now, if you see, originally the data transfer
13:11 has been originated by the other VPCs,
13:13 which are sending the traffic to the,
13:16 your firewall VPC or a firewall EC2 machine.
13:19 But, as you read this line,
13:22 the data transfer out is allocated
13:23 to the owner of the last resource to send traffic,
13:27 before traffic hits the Direct Connect VIF.
13:29 So, this is one difference,
13:31 when it comes to the transit gateway.
13:31 Now, there is one more scenario.
13:35 If there are multiple AWS organization involved,
13:38 for example, the Direct Connect connection
13:39 is owned by AWS account, which is part of
13:42 AWS organization one, and the resource
13:46 which is sending the data, is a part of an AWS account,
13:49 which is part of AWS organization two.
13:52 Now, in this case,
13:53 of course, Data Transfer Out charges will be again,
13:56 built to the account two in organization two,
14:00 however, the DTO charges are not
14:03 the Direct Connect DTO charges,
14:05 but it would be the standard AWS service DTO charges.
14:08 And you know that,
14:10 standard DTO charges for AWS services is quite high
14:14 than the Direct Connect DTO charges.
14:17 That means the account owner
14:18 will pay more charges in this case, because these
14:21 accounts are not part of the same AWS organization.
14:25 So, I think we covered quite a lot,
14:28 and different scenarios,
14:29 and it might be overwhelming to remember all this
14:32 permutation and combination.
14:34 And that's where I'm just trying to now simplify
14:36 what you need to probably remember for your exam.
30. DX Billing 总结页
时间范围：14:39–14:45
总结 / Summary
中文
总结部分把 Direct Connect（DX）计费压缩为费用类型、费率决定因素和账户归属三类考点。
English
The summary condenses Direct Connect billing into charge types, rate determinants, and account ownership rules.
Transcript
14:39 So, quick summary of the DX billing.
14:42 The DX has two type of the charges,
31. 两类核心费用
时间范围：14:45–14:49
总结 / Summary
中文
Direct Connect（DX）有两类核心费用：端口小时费用（Port-Hour Charges）和数据传出费用（Data Transfer Out，DTO）。
English
The two core DX charges are port-hour charges and Data Transfer Out charges.
Transcript
14:45 port-hour charges and Data Transfer Out charges.
32. Port-Hour 取决于容量
时间范围：14:49–15:08
总结 / Summary
中文
端口小时费用（Port-Hour Charges）取决于 DX 连接容量；各 DX 位置通常使用统一费率，日本除外。
English
Port-hour charges depend on DX connection capacity and are generally standardized across DX locations except Japan.
Transcript
14:49 And the port-hour charges depend on the DX capacity,
14:52 whether you go for 1Gbps connection
14:54 or 10 Gbps connection or sub-1 Gbps connection.
14:57 And all the port-hour charges are standard
15:00 across all DX locations, except the Japan.
15:04 Now, AWS account, which created the DX connection,
33. 创建连接的账户支付 Port-Hour
时间范围：15:08–15:18
总结 / Summary
中文
创建并拥有 Direct Connect 连接的 AWS 账户支付端口小时费用（Port-Hour Charges），无论连接类型是 Dedicated 还是 Hosted。
English
The AWS account that creates and owns the Direct Connect connection pays port-hour charges for both Dedicated and Hosted connections.
Transcript
15:08 pays for the port-hour charges, right?
15:11 Whether it's a dedicated connection
15:12 or it's a hosted connection.
15:15 And, with respect to the Data Transfer Out charges,
34. 发送资源所有者通常支付 DTO
时间范围：15:18–15:51
总结 / Summary
中文
数据传出费用（DTO）通常分配给拥有发送流量资源的账户；中转网关（Transit Gateway）场景存在“最后发送资源”例外。
English
DTO is generally allocated to the account that owns the resource sending traffic, with a last-sending-resource exception for Transit Gateway scenarios.
Transcript
15:18 generally speaking, it is allocated
15:20 to the account that owns the resource, sending the traffic,
15:23 with exception of transit gateway,
15:25 we just saw that, but I, I don't think so
15:28 you need to get into transit gateway detail.
15:30 Just understand that the resource
15:32 which initiated the traffic,
15:34 will be applicable for the Data Transfer Out charges.
15:39 And in case of multi account setup,
15:41 where the owner of the connection
15:43 and AWS resources are in different AWS organization,
15:48 the DTO is charged to the resource owner, of course.
35. 跨 Organization 使用标准 DTO 费率
时间范围：15:51–16:16
总结 / Summary
中文
若 DX 连接所有者与资源账户属于不同 AWS Organizations，DTO 仍由资源所有者支付，但采用标准 AWS 服务 DTO 费率（Standard AWS Service DTO Rate），而不是 DX DTO 费率。
English
When the connection owner and resource account belong to different AWS Organizations, the resource owner still pays DTO, but at the standard AWS service DTO rate rather than the DX DTO rate.
Transcript
15:51 It is inline with what we just saw,
15:54 but the DTO charges are not the Direct Connect DTO charges,
15:58 but the standard AWS services DTO charges, right?
16:01 So, these are essentially things that you need to remember.
16:05 Now, with that,
16:07 again,
16:08 if you are not able to make out who pays for what,
16:11 let's look at a quick knowledge check,
16:13 how you arrived to that decision.
36. Knowledge Check
时间范围：16:16–16:17
总结 / Summary
中文
知识检查（Knowledge Check）要求把端口小时费用（Port-Hour）和数据传出费用（DTO）的责任主体分别判断。
English
The knowledge check asks you to determine the responsible account separately for port-hour and DTO charges.
Transcript
16:16 So the question is,
37. 问题：Hosted VIF 谁付费？
时间范围：16:17–16:25
总结 / Summary
中文
问题要求判断托管 VIF（Hosted VIF）以及通过该 VIF 传输流量时，端口和数据费用分别由谁承担。
English
The question asks who pays for a Hosted VIF and for traffic carried over that VIF.
Transcript
16:17 who pays for charges for the hosted VIF,
16:20 and the traffic flowing over to the hosted VIF?
16:23 So what should be your answer?
38. 答题框架：分两条线思考
时间范围：16:25–16:45
总结 / Summary
中文
解题时先区分连接所有者（Connection Owner）和 VIF/资源所有者（Resource Owner），再分别判断端口小时费用与 DTO。
English
Solve the question by separating the connection owner from the VIF or resource owner, then evaluate port-hour charges and DTO independently.
Transcript
16:25 Now, think on two lines,
16:26 first,
16:28 you need to know what is hosted VIF.
16:29 Now in case of hosted VIF,
16:31 the connection is owned by someone,
16:34 that means one AWS account,
16:35 and typically VIF is owned by some other AWS account.
16:39 That's typically what hosted VIF is.
16:42 Now, go with the same analogy.
16:44 First, think about port-hours.
39. Hosted VIF 的 Port-Hour 归属
时间范围：16:45–17:01
总结 / Summary
中文
托管 VIF（Hosted VIF）的端口小时费用（Port-Hour Charges）由拥有连接的 AWS 账户承担，连接是 Dedicated 还是 Hosted 不改变该规则。
English
For a Hosted VIF, the AWS account that owns the connection pays the port-hour charges; the Dedicated-versus-Hosted distinction does not change that rule.
Transcript
16:45 Now, port-hour will be built to the AWS account,
16:48 owning the connection,
16:49 whether it's a dedicated connection
16:52 or it's a hosted connection, doesn't matter, right?
16:56 And now, let's talk about the
16:58 Data Transfer Out charges.
17:00 So, Data Transfer Out charges will be built
40. Hosted VIF 的 DTO 归属
时间范围：17:01–17:14
总结 / Summary
中文
通过托管 VIF（Hosted VIF）发送流量时，数据传出费用（DTO）由包含发送资源的 AWS 账户承担。
English
For traffic sent over a Hosted VIF, DTO is billed to the AWS account containing the resource that sends the traffic.
Transcript
17:01 to the AWS account,
17:02 which contains the resource,
17:04 sending the traffic over the hosted VIF.
17:06 So again, things are simple.
17:08 Think about port-hour charges,
17:10 and think about data transfer out charges.
17:12 So ask this two questions:
41. 记忆法：谁拥有连接，谁发送流量
时间范围：17:14–17:40
总结 / Summary
中文
判断 DX 计费只需问两个问题：谁拥有连接（Who Owns the Connection）决定 Port-Hour，谁发送流量（Who Sends the Traffic）通常决定 DTO。
English
Use two questions: who owns the connection determines port-hour charges, and who sends the traffic generally determines DTO.
Transcript
17:14 Who owns the connection?
17:15 And who sends the traffic, right?
17:17 Accordingly, these charges would be distributed.
17:20 So with that, I think,
17:22 we saw lot of things when it comes to the DX billing.
17:26 And I think it is one of the, again,
17:29 important topic to know,
17:31 because then you're very clear,
17:33 you know, when it comes to
17:34 the questions related to the billing for DX
17:37 So, thanks for watching.
整讲总结 / Overall Summary
中文
Direct Connect（DX）主要收取端口小时费用（Port-Hour Charges）和数据传出费用（Data Transfer Out，DTO）。Port-Hour 由连接容量和类型决定，并由创建/拥有连接的账户支付；Dedicated 连接进入 Available 状态或请求满 90 天后开始计费，Hosted 连接在接受后开始计费，只有删除连接才停止。DTO 按源 AWS 区域（Source AWS Region）和 DX 位置（DX Location）组合计价，通常由发送资源所有者支付；S3 请求者付费（Requester Pays）、中转网关（Transit Gateway）最后发送资源以及跨 AWS Organizations 的标准服务 DTO 费率是重要例外。最实用的判断法是分别问：谁拥有连接，谁发送流量。
English
Direct Connect primarily charges port-hours and Data Transfer Out. Port-hour rates depend on connection capacity and type and are paid by the account that creates or owns the connection. A Dedicated Connection starts billing when Available or 90 days after the request; a Hosted Connection starts when accepted, and billing stops only after deletion. DTO is priced by source AWS Region and DX location and is normally paid by the sending resource owner. S3 Requester Pays, Transit Gateway's last-sending-resource rule, and standard service DTO pricing across different AWS Organizations are key exceptions. The practical decision rule is to ask who owns the connection and who sends the traffic.
返回顶部 ↑