A city utility must connect on-premises SCADA historians to an analytics VPC with consistent low latency and dedicated bandwidth for continuous telemetry. Which hybrid connectivity approach best fits these requirements?
Select an answer to reveal the explanation.
Short Explanation
SCADA telemetry wants a private lane with predictable speed, not a ride-share trip across the public internet. Direct Connect gives that dedicated path into AWS. A lone Site-to-Site VPN can work as backup, but it is not the primary answer when dedicated bandwidth and steady latency are must-haves.
Full Explanation
When hybrid designs require predictable latency and dedicated capacity, AWS Direct Connect provides a private circuit from the on-premises or co-location environment into AWS rather than depending only on encrypted tunnels over the public internet. Site-to-Site VPN remains valuable for encrypted connectivity and failover, but it does not by itself guarantee dedicated bandwidth or consistent latency for continuous SCADA historian feeds. Public exposure of historians increases attack surface, and VPC peering does not replace hybrid on-premises connectivity.