AWS wellarchitected documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
Branding change without security implications. No modification to security guidance or vulnerability addressing.
Diff
diff --git a/wellarchitected/latest/hybrid-networking-lens/cost-optimization-pillar.md b/wellarchitected/latest/hybrid-networking-lens/cost-optimization-pillar.md index c20a16196..c1e9d150b 100644 --- a//wellarchitected/latest/hybrid-networking-lens/cost-optimization-pillar.md +++ b//wellarchitected/latest/hybrid-networking-lens/cost-optimization-pillar.md @@ -57 +57 @@ Choose hybrid networking connectivity for workloads with varying requirements fo -Start off with Internet-based hybrid networking connections while in the testing phase of any workload migration or deployment and then migrate to more permanent connections only after baseline bandwidth requirements have been identified. For example, leveraging an internet based solution like AWS Site-to-Site VPN and then migrating to a dedicated connection like AWS Direct Connect. This enables you to start-off with a cost effective solution that can also be easily decommissioned prior to deploying a more permanent hybrid networking connection. +Start off with Internet-based hybrid networking connections while in the testing phase of any workload migration or deployment and then migrate to more permanent connections only after baseline bandwidth requirements have been identified. For example, leveraging an internet based solution like AWS Site-to-Site VPN and then migrating to a dedicated connection like Direct Connect. This enables you to start-off with a cost effective solution that can also be easily decommissioned prior to deploying a more permanent hybrid networking connection.