AWS prescriptive-guidance documentation change
Summary
Updated navigation links, modified section title, improved formatting (added italics), and made minor text clarifications about AWS Transit Gateway and VPC Lattice
Security assessment
Changes focus on content clarity and formatting rather than security aspects. While the content discusses network segmentation (a security concept), the modifications don't introduce new security guidance or address specific vulnerabilities. The existing security implications of network isolation remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/network-connectivity.md b/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/network-connectivity.md index f2d9c061c..36319065f 100644 --- a//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/network-connectivity.md +++ b//prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/network-connectivity.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Transitioning to multiple AWS accounts](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Transitioning to multiple AWS accounts](introduction.html) @@ -7 +7 @@ -Connecting VPCsConnecting applicationsBest practices +Connecting VPCsConnecting applicationsBest practices for network connectivity @@ -9 +9 @@ Connecting VPCsConnecting applicationsBest practices -# Network connectivity for a multi-account architecture +# Network connectivity @@ -15 +15 @@ Many companies use VPC peering in Amazon Virtual Private Cloud (Amazon VPC) to c -If you have multiple development, test, and staging environments that host non-production data across multiple AWS accounts, you might want to provide network connectivity between all of those VPCs but disallow any access to production environments. You can use [AWS Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html) to connect multiple VPCs across multiple accounts. You can separate the route tables to prevent development VPCs from communicating to production VPCs through the transit gateway, which acts as centralized router. For more information, see [Centralized router](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-centralized-router.html) (Transit Gateway documentation). +If you have multiple development, test, and staging environments that host non-production data across multiple AWS accounts, you might want to provide network connectivity between all of those VPCs but disallow any access to production environments. You can use [AWS Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/what-is-transit-gateway.html) to connect multiple VPCs across multiple accounts. You can separate the route tables to prevent development VPCs from communicating to production VPCs through the transit gateway, which acts as centralized router. For more information, see [Centralized router](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-centralized-router.html) (AWS Transit Gateway documentation). @@ -17 +17 @@ If you have multiple development, test, and staging environments that host non-p -Transit Gateway also supports peering with other transit gateways, including those in different AWS accounts or AWS Regions. Because Transit Gateway is a fully managed, highly available service, you need to provision only one transit gateway for each Region. +AWS Transit Gateway also supports peering with other transit gateways, including those in different AWS accounts or AWS Regions. Because Transit Gateway is a fully managed, highly available service, you need to provision only one transit gateway for each Region. @@ -23 +23 @@ For more information and detailed network architectures, see [Building a Scalabl -If you need to establish communication between applications in different AWS accounts in the same environment (such as production), you can use one of the following options: +If you need to establish communication between applications in different accounts in the same environment (such as production), you can use one of the following options: @@ -29 +29 @@ If you need to establish communication between applications in different AWS acc - * [Amazon VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/what-is-vpc-service-network.html) associates services, such as applications, across multiple accounts and VPCs and collects them into a service network. Clients in VPCs associated with the service network can send requests to all other services that are associated with the service network, regardless of whether they’re in the same account. VPC Lattice integrates with AWS Resource Access Manager (AWS RAM) so that you can share resources with other accounts or through AWS Organizations. You can associate a VPC with only one service network. This solution doesn’t require use of VPC peering or AWS Transit Gateway to communicate across accounts. + * [Amazon VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/what-is-vpc-service-network.html) associates services, such as applications, across multiple accounts and VPCs and collects them into a _service network_. Clients in VPCs associated with the service network can send requests to all other services that are associated with the service network, regardless of whether they're in the same account. VPC Lattice integrates with AWS Resource Access Manager (AWS RAM) so that you can share resources with other accounts or through AWS Organizations. You can associate a VPC with only one service network. This solution doesn't require use of VPC peering or AWS Transit Gateway to communicate across accounts.