AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2025-11-19 · Documentation low

File: whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/conclusion.md

Summary

Replaced 'AWS Direct Connect' with 'Direct Connect' in service listing

Security assessment

Stylistic change to service name references. No modification to security architecture recommendations or vulnerability disclosures.

Diff

diff --git a/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/conclusion.md b/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/conclusion.md
index 1904dc873..978da3b65 100644
--- a//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/conclusion.md
+++ b//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/conclusion.md
@@ -7 +7 @@
-As you scale your usage of AWS and deploy applications in the AWS Landing Zone, the number of VPCs and networking components increases. This whitepaper explained how you can manage this growing infrastructure ensuring scalability, high availability, and security while keeping costs low. Making the right design decisions when using services such as Transit Gateway, Shared VPC, AWS Direct Connect, VPC endpoints, Gateway Load Balancer, AWS Network Firewall, Amazon Route 53, and third-party software appliances becomes critical. It is important to understand the key considerations of each approach and work backwards from your requirements and analyze as to which option or combination of options fit you best.
+As you scale your usage of AWS and deploy applications in the AWS Landing Zone, the number of VPCs and networking components increases. This whitepaper explained how you can manage this growing infrastructure ensuring scalability, high availability, and security while keeping costs low. Making the right design decisions when using services such as Transit Gateway, Shared VPC, Direct Connect, VPC endpoints, Gateway Load Balancer, AWS Network Firewall, Amazon Route 53, and third-party software appliances becomes critical. It is important to understand the key considerations of each approach and work backwards from your requirements and analyze as to which option or combination of options fit you best.