AWS wellarchitected documentation change
Summary
Modified redundant 'AWS Direct Connect' reference to 'Direct Connect' in cost optimization guidance
Security assessment
Minor editorial change removing redundant branding. No security implications or new security features introduced.
Diff
diff --git a/wellarchitected/2024-06-27/framework/cost_data_transfer_optimized_components.md b/wellarchitected/2024-06-27/framework/cost_data_transfer_optimized_components.md index 89c478583..c1ae074d3 100644 --- a//wellarchitected/2024-06-27/framework/cost_data_transfer_optimized_components.md +++ b//wellarchitected/2024-06-27/framework/cost_data_transfer_optimized_components.md @@ -25 +25 @@ When planning or reviewing your workload architecture, consider the following: - * **Use AWS Direct Connect** AWS Direct Connect bypasses the public internet and establishes a direct, private connection between your on-premises network and AWS. This can be more cost-effective and consistent than transferring large volumes of data over the internet. + * **Use AWS Direct Connect** Direct Connect bypasses the public internet and establishes a direct, private connection between your on-premises network and AWS. This can be more cost-effective and consistent than transferring large volumes of data over the internet.