AWS Direct Connect and Remote.It are two different solutions for connecting an on-premises network to an AWS VPC. The best choice depends on your specific needs and constraints. Here’s a comparison:
AWSダイレクトコネクト
AWS Direct Connectのメリット
-
Provides a dedicated, private connection between your on-premises network and AWS, which can offer more consistent network performance compared to internet-based connections.
-
Potentially lower data transfer costs compared to transferring data over the internet.
-
Supports multiple virtual interfaces, allowing you to connect to multiple VPCs and services within AWS over a single connection.
-
Can provide higher bandwidth options compared to internet-based connections.
AWS Direct Connectの課題
-
Requires a physical connection to an AWS Direct Connect location, which may not be available in all areas.
-
There can be significant setup and monthly costs associated with maintaining a Direct Connect connection, especially for high-bandwidth connections.
-
Might require more advanced networking knowledge to set up and manage.
AWS Direct Connectの使用例
- Ideal for high-volume data transfer use cases, such as migrating data to the cloud, backing up data to the cloud, or running high-performance, latency-sensitive applications in the cloud.
Remote.It
Remote.Itのメリット
-
Provides zero trust network connectivity, reducing the attack surface by not exposing IP addresses or requiring port forwarding.
-
Works well in multi-NAT or CGNAT environments where traditional VPNs might fail.
-
ネットワークの変更やデバイスの移動に強く、接続を自動的に再接続します。
-
Efficiently manages network resources, automates IP address planning, resolves subnet collisions, and simplifies routing tables, access control lists, and VLAN tags.
-
Remote.It connects users and devices when other solutions fail.
リモートイットの課題
-
May require additional setup and configuration compared to built-in AWS services.
-
As a third-party service, it might not have the same level of integration with other AWS services as native AWS solutions like AWS Direct Connect.
-
Pricing model and costs could be a factor depending on the size and scale of the network.
リモートイットの使用例
-
Ideal for enabling remote access on any network, including devices on CGNAT networks such as 5G and Starlink.
-
Useful for developers needing to access resources from multiple private networks simultaneously.
-
Can be integrated into OEM and embedded products before deployment.
-
Can provide access to services within Docker container networks without the need for routing tables
AWS Direct Connectの物理接続要件
AWS Direct Connectを利用するには、お客様のネットワークとAWS Direct Connectのロケーションを物理的に接続する必要があります。これは通常、以下のいずれかの方法で行われます：
-
Direct Fiber Connection: This method involves running a physical fiber connection from your data center, office, or colocation environment directly to an AWS Direct Connect location. This option often provides the highest level of performance and consistency but can be costly and logistically complex, particularly if your location is far from an AWS Direct Connect location.
-
Partner Carrier Network: If a direct fiber connection isn’t feasible, you can work with a partner carrier that already has a presence at an AWS Direct Connect location. These carriers can extend their network to your location, essentially providing a “last mile” service. This is often simpler and can be more cost-effective than a direct fiber connection, particularly for smaller data requirements or if your location is far from an AWS Direct Connect location.
いずれの場合も、AWS Direct Connectロケーションへの物理的な接続が確立されると、VPCへの仮想インターフェイスを作成できます。この仮想インターフェースにより、ネットワークはあたかも同じネットワーク上にあるかのようにVPC内のリソースにアクセスできるようになります。
It’s also worth noting that AWS Direct Connect supports Link Aggregation Group (LAG), which allows you to aggregate multiple physical connections into a single logical connection. This can provide higher bandwidth and increased redundancy.
AWS Direct Connectを実装するには、複数の関係者（社内のネットワークチーム、AWS、パートナーキャリアなど）との調整が必要であり、セットアップと管理にはかなりの技術的なネットワーク知識が必要になる可能性があることを覚えておこう。
AWS ダイレクトコネクトコスト
AWS Direct Connectの価格には、主に2つの要素がある：
-
Pricing per port hour for all AWS Direct Connect locations
-
Data transfer out fees by AWS Direct Connect locations
For example, if you order a 1GB connection to the US East region - Virginia and expect to transfer 1TB out monthly, a price per port hour of $0.30 and a data transfer per GB of $0.02 will be applied. The 1TB data transfer cost would be $216 for the port charges and $20 for the data transfer. The total cost would be $236 per month. It’s important to note that the total cost of maintaining your AWS Direct Connect link to your on-premises environment will vary depending on the volume of data transfer out of AWS and the region you select.
リモートイットの展開
Remote doesn’t have physical connection requirements or even requires exposing AWS ports to the public internet.
リモート・イット・コスト
Remote.Itでは、Direct Connectと同じAWSデータ転送料が発生します。Remote.Itには追加のデータ転送料金はかかりません。
AWS Direct ConnectとRemote.Itの概要比較
まとめると、AWS Direct Connectは、大容量で一貫したデータ転送のニーズがあり、セットアップとメンテナンスのコストに余裕がある場合に適した選択かもしれない。Remote.Itは、複雑なネットワーク環境をお持ちの場合、ゼロトラストのネットワークアクセスが必要な場合、または時間とコストの両方で追加のネットワーク設定とメンテナンスコストをかけずに、より柔軟で弾力性のある接続が必要な場合に適しています。いつものように、選択肢はお客様固有の要件や状況によって異なります。