AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2025-11-19 · Documentation low

File: prescriptive-guidance/latest/backup-recovery/hybrid-arch.md

Summary

Changed 'AWS Direct Connect' to 'Direct Connect' in hybrid architecture documentation

Security assessment

Terminology update for service name consistency. The change does not affect security guidance about using Direct Connect for secure hybrid connectivity.

Diff

diff --git a/prescriptive-guidance/latest/backup-recovery/hybrid-arch.md b/prescriptive-guidance/latest/backup-recovery/hybrid-arch.md
index 486ce0bf4..e41e76855 100644
--- a//prescriptive-guidance/latest/backup-recovery/hybrid-arch.md
+++ b//prescriptive-guidance/latest/backup-recovery/hybrid-arch.md
@@ -9 +9 @@ The cloud-native and on-premises deployments discussed in this guide can be comb
-This is becoming a common scenario for enterprise workloads. Many enterprises have data centers of their own and use AWS to augment capacity. These customer data centers are often connected to the AWS network by high-capacity network links. For example, with [AWS Direct Connect](https://aws.amazon.com/directconnect/), you can establish private, dedicated connectivity from your on-premises data center to AWS. This provides the bandwidth and consistent latency to upload data to the cloud for the purposes of data protection. It also provides consistent performance and latency for hybrid workloads. The following diagram provides one example of a hybrid environment approach.
+This is becoming a common scenario for enterprise workloads. Many enterprises have data centers of their own and use AWS to augment capacity. These customer data centers are often connected to the AWS network by high-capacity network links. For example, with [Direct Connect](https://aws.amazon.com/directconnect/), you can establish private, dedicated connectivity from your on-premises data center to AWS. This provides the bandwidth and consistent latency to upload data to the cloud for the purposes of data protection. It also provides consistent performance and latency for hybrid workloads. The following diagram provides one example of a hybrid environment approach.