HNCOST03-BP01 Implement tiered connectivity based on workload requirements
Hybrid networking connectivity must balance performance, reliability, and cost. Workloads with varying requirements for throughput, latency, and uptime should leverage different connectivity solutions. For example, non-critical workloads (for example, development or testing) can use cost-effective internet-based VPNs, while mission-critical production workloads may require dedicated connections like AWS Direct Connect. A tiered approach ensures you only pay for the level of connectivity your workloads actually need.
Desired outcome: Cost savings through workload-aligned connectivity, with no overpayment for unnecessary bandwidth or redundancy.
Level of risk exposed if this best practice is not established: Medium
Benefits of establishing this best practice:
-
Reduces costs for non-critical workloads
-
Ensures high performance for production workloads
-
Simplifies scaling as requirements evolve
Implementation guidance
-
Use IPSec VPN connections for non-mission critical workloads
-
Use dedicated connections for production workloads
-
Scale from IPSec VPN connections in testing phase to dedicated connections after bandwidth requirements are defined
-
Use direct connectivity to single cloud network connectivity to avoid additional cloud transit costs, For example, you can use Direct Connect private VIF to connect directly to VPC.
-
Use cloud transit connectivity to connect to multiple cloud networks. For example, you can use Direct Connect transit VIF to connect to Transit Gateway for VPCs in the same region, or Cloud WAN core network for VPCs in multiple regions
Resources
