AWS wellarchitected documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in cost optimization context
Security assessment
Branding change without security implications. Focus remains on cost optimization through private network connections.
Diff
diff --git a/wellarchitected/latest/cost-optimization-pillar/cost_data_transfer_optimized_components.md b/wellarchitected/latest/cost-optimization-pillar/cost_data_transfer_optimized_components.md index 3eccfad33..f1a0aca3e 100644 --- a//wellarchitected/latest/cost-optimization-pillar/cost_data_transfer_optimized_components.md +++ b//wellarchitected/latest/cost-optimization-pillar/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.