AWS prescriptive-guidance documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the document, including section headers and documentation links. Adjusted terminology consistency for the service name.
Security assessment
The changes are branding/terminology updates rather than security-related modifications. While the document discusses routing policies and prefix filtering (security best practices), these were already present in the original text. The edits don't introduce new security content or address vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/multicloud-vdi.md b/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/multicloud-vdi.md index 4db31c7c1..809521e49 100644 --- a//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/multicloud-vdi.md +++ b//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/multicloud-vdi.md @@ -5 +5 @@ -RequirementsConfiguring Megaport MCR with VXCConfiguring AWS Direct ConnectConfiguring Megaport MCR with SECConfigure Salesforce Hyperforce +RequirementsConfiguring Megaport MCR with VXCConfiguring Direct ConnectConfiguring Megaport MCR with SECConfigure Salesforce Hyperforce @@ -9 +9 @@ RequirementsConfiguring Megaport MCR with VXCConfiguring AWS Direct ConnectConfi -This use case covers a scenario where you have a virtual desktop infrastructure (VDI) running in another cloud provider that has a private connection to Megaport and is used as an on-ramp to AWS Direct Connect +This use case covers a scenario where you have a virtual desktop infrastructure (VDI) running in another cloud provider that has a private connection to Megaport and is used as an on-ramp to Direct Connect @@ -11 +11 @@ This use case covers a scenario where you have a virtual desktop infrastructure -Using Megaport MCR with AWS Direct Connect gives your VDI users private connectivity to Salesforce Hyperforce. VDI users use their desktops for their daily work, and the VDI provides an on-ramp to AWS Direct Connect by using a Megaport location. +Using Megaport MCR with Direct Connect gives your VDI users private connectivity to Salesforce Hyperforce. VDI users use their desktops for their daily work, and the VDI provides an on-ramp to Direct Connect by using a Megaport location. @@ -13 +13 @@ Using Megaport MCR with AWS Direct Connect gives your VDI users private connecti - + @@ -23 +23 @@ Using Megaport MCR with AWS Direct Connect gives your VDI users private connecti - * You own an AWS account to manage the AWS Direct Connect hosted connection with Megaport. + * You own an AWS account to manage the Direct Connect hosted connection with Megaport. @@ -43 +43 @@ For step-by-step instructions, see the following Megaport documentation: - * The prefixes advertised by AWS Direct Connect must not be advertised beyond the network boundaries of your connection. For example, these prefixes must not be included in any public internet routing table. For more information, see [Public virtual interface routing policies](https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#routing-policies) in the AWS Direct Connect documentation. + * The prefixes advertised by Direct Connect must not be advertised beyond the network boundaries of your connection. For example, these prefixes must not be included in any public internet routing table. For more information, see [Public virtual interface routing policies](https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#routing-policies) in the Direct Connect documentation. @@ -48 +48 @@ For step-by-step instructions, see the following Megaport documentation: -## Configuring AWS Direct Connect +## Configuring Direct Connect @@ -52 +52 @@ For step-by-step instructions, see the following Megaport documentation: -In your AWS account, accept the VXC created previously as a hosted connection. For instructions, see the [AWS Direct Connect documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/hosted_connection.html#accept-hosted-connection). +In your AWS account, accept the VXC created previously as a hosted connection. For instructions, see the [Direct Connect documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/hosted_connection.html#accept-hosted-connection). @@ -60 +60 @@ In your account, provision a public VIF under the connection you accepted from M - * Public IPv4 addresses for peering (typically `/31` CIDR). You can own these or request them from Support. For more information, see _Peer IP addresses_ in the section [Prerequisites for virtual interfaces](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#vif-prerequisites) in the AWS Direct Connect documentation. + * Public IPv4 addresses for peering (typically `/31` CIDR). You can own these or request them from Support. For more information, see _Peer IP addresses_ in the section [Prerequisites for virtual interfaces](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#vif-prerequisites) in the Direct Connect documentation. @@ -65 +65 @@ In your account, provision a public VIF under the connection you accepted from M -To create a public VIF, follow the steps in the [AWS Direct Connect documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html#create-public-vif). +To create a public VIF, follow the steps in the [Direct Connect documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html#create-public-vif). @@ -71 +71 @@ After you create the public VIF, you need to make sure that the BGP authenticati -Using a public VIF to connect to AWS from your on-premises or multicloud environment changes the way traffic is routed from AWS public prefixes to your users. We recommend that you use a prefix filter (route map) to make sure that the accepted Amazon prefixes are limited to the Hyperforce infrastructure and any other necessary AWS resources. For more information, see [Public virtual interface prefix advertisement rules](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#advertise-prefixes) in the AWS Direct Connect documentation and [Hyperforce External IPs](https://compliance.salesforce.com/en/documents/a006e0000121zduAAA) in the Salesforce documentation. +Using a public VIF to connect to AWS from your on-premises or multicloud environment changes the way traffic is routed from AWS public prefixes to your users. We recommend that you use a prefix filter (route map) to make sure that the accepted Amazon prefixes are limited to the Hyperforce infrastructure and any other necessary AWS resources. For more information, see [Public virtual interface prefix advertisement rules](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#advertise-prefixes) in the Direct Connect documentation and [Hyperforce External IPs](https://compliance.salesforce.com/en/documents/a006e0000121zduAAA) in the Salesforce documentation.