When testing Direct Connect (DX) type of connections, there are multiple aspects to check:
- Redundancy: Ensure that the connections are redundant. How they terminated within or across DX location determines what level of redundancy that can be achieved. See AWS Direct Connect Resiliency Recommendations
- Backup: Ensure you have backup path over VPN (Internet) when all DX connections are down. This should be part of backup link testing.
- Failover convergence and recovery of traffic testing: Test how much time is getting elapsed after a given connection is down and before a new path is available for the traffic
- Bandwidth, throughput, latency: Tools like iperf can be useful. You may have to run those tests with parallel streams (-P parameter) to measure full performance, for 10Gbps connections and run them long enough (for e.g., ~10mins).
Direct Connect switching from 1G to 10GAccepted Answerasked 3 years ago
Direct Connect Failover with two Virtual Interfaces (VIFs)Accepted Answerasked 2 years ago
Single DC-GW connected to multiple direct-connect linksAccepted Answerasked 7 months ago
VPN over Direct Connect with Direct Connect GatewayAccepted Answerasked 2 years ago
Can I split an AWS Direct Connect connection and assign specific bandwidths to different resources?Accepted Answerasked 2 years ago
Private link access over direct connect - Direct Connect GatewayAccepted Answerasked 4 years ago
Direct Connect TestingAccepted Answerasked 3 years ago
Moving from 1G to 10G Direct ConnectAccepted Answerasked 3 years ago
Is it better to have a single Direct Connect Gateway or multiple Direct Connect Gateways?Accepted AnswerEXPERTasked 6 months ago
AWS charging for direct connectasked a day ago