AWS prescriptive-guidance documentation change
Summary
Updated navigation link from 'welcome.html' to 'introduction.html', fixed apostrophe formatting, and changed image path to a new UUID-based location.
Security assessment
Changes are limited to navigation, typography, and image paths. Existing security discussion about transit gateway architecture remains unchanged. No new security content or vulnerability fixes were added.
Diff
diff --git a/prescriptive-guidance/latest/integrate-third-party-services/architecture-3-1.md b/prescriptive-guidance/latest/integrate-third-party-services/architecture-3-1.md index 5e31e2b5c..aaf96f062 100644 --- a//prescriptive-guidance/latest/integrate-third-party-services/architecture-3-1.md +++ b//prescriptive-guidance/latest/integrate-third-party-services/architecture-3-1.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Integrating third-party services in the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Integrating third-party services in the AWS Cloud](introduction.html) @@ -32 +32 @@ In AWS RAM, your account is the _sharer_ , and the third-party account is the _a -The following architecture diagram shows how you use AWS RAM to share a transit gateway with the third-party service provider. For security, you create a new transit gateway in your account. You connect the new transit gateway to the third-party’s VPCs. You use a peering connection to connect the new transit gateway to an existing transit gateway in your account, which is attached to your VPCs. You enable appliance mode on the new transit gateway in order connect with the elastic network interface in the inspection VPC. For more information about the inspection VPC, see [Centralizing network inspection](./architecture-3.html#centralized-network-inspection). +The following architecture diagram shows how you use AWS RAM to share a transit gateway with the third-party service provider. For security, you create a new transit gateway in your account. You connect the new transit gateway to the third-party's VPCs. You use a peering connection to connect the new transit gateway to an existing transit gateway in your account, which is attached to your VPCs. You enable appliance mode on the new transit gateway in order connect with the elastic network interface in the inspection VPC. For more information about the inspection VPC, see [Centralizing network inspection](./architecture-3.html#centralized-network-inspection). @@ -34 +34 @@ The following architecture diagram shows how you use AWS RAM to share a transit - +