AWS prescriptive-guidance documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the document, aligning with branding changes and documentation consistency. No technical changes to configuration steps or security recommendations.
Security assessment
The changes are purely terminological (branding updates from 'AWS Direct Connect' to 'Direct Connect') and do not introduce new security guidance or address vulnerabilities. Existing security recommendations (e.g., prefix filtering for public VIFs) remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/branch-offices.md b/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/branch-offices.md index b68177b56..ad741c08b 100644 --- a//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/branch-offices.md +++ b//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/branch-offices.md @@ -5 +5 @@ -RequirementsConfiguring Megaport Port with VXCConfiguring your network devicesConfiguring AWS Direct ConnectConfiguring Megaport Port with SECConfiguring Salesforce Hyperforce +RequirementsConfiguring Megaport Port with VXCConfiguring your network devicesConfiguring Direct ConnectConfiguring Megaport Port with SECConfiguring Salesforce Hyperforce @@ -9 +9 @@ RequirementsConfiguring Megaport Port with VXCConfiguring your network devicesCo -This use case covers a scenario where you have a physical router in one Megaport location, and you use it as an on-ramp to AWS Direct Connect. In this scenario, you also have one or more branch offices connected to this location through private circuits. +This use case covers a scenario where you have a physical router in one Megaport location, and you use it as an on-ramp to Direct Connect. In this scenario, you also have one or more branch offices connected to this location through private circuits. @@ -11 +11 @@ This use case covers a scenario where you have a physical router in one Megaport -Using Megaport Port with AWS Direct Connect gives your users who work in branch offices private connectivity to Salesforce Hyperforce. The branch offices consist of a single office or a cluster of offices inter-networked across a metropolitan area network (MAN). The offices on-ramp to AWS Direct Connect by using a Megaport location. The following diagram shows the architecture for this use case. +Using Megaport Port with Direct Connect gives your users who work in branch offices private connectivity to Salesforce Hyperforce. The branch offices consist of a single office or a cluster of offices inter-networked across a metropolitan area network (MAN). The offices on-ramp to Direct Connect by using a Megaport location. The following diagram shows the architecture for this use case. @@ -13 +13 @@ Using Megaport Port with AWS Direct Connect gives your users who work in branch - + @@ -21 +21 @@ Using Megaport Port with AWS Direct Connect gives your users who work in branch - * 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. @@ -30 +30 @@ Using Megaport Port with AWS Direct Connect gives your users who work in branch -The Megaport Port is configured with a VXC and provides the private Layer 2 network segment to AWS. The AWS Direct Connect connection is provisioned as a hosted connection and attached to a public VIF. For step-by-step instructions, see the following Megaport documentation: +The Megaport Port is configured with a VXC and provides the private Layer 2 network segment to AWS. The Direct Connect connection is provisioned as a hosted connection and attached to a public VIF. For step-by-step instructions, see the following Megaport documentation: @@ -41 +41 @@ The Megaport Port is configured with a VXC and provides the private Layer 2 netw -Network devices that are deployed at the Megaport location within your rack are configured to support the connectivity to the Hyperforce instances through AWS Direct Connect. These devices might include a router, switch, firewall, or a combined network stack of multiple devices. The vendor and model types are optional, depending on your requirements. We recommend that you work with your network administrator to configure these devices. +Network devices that are deployed at the Megaport location within your rack are configured to support the connectivity to the Hyperforce instances through Direct Connect. These devices might include a router, switch, firewall, or a combined network stack of multiple devices. The vendor and model types are optional, depending on your requirements. We recommend that you work with your network administrator to configure these devices. @@ -49 +49 @@ The device that is used to establish the physical cross connect to the Megaport - * 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. @@ -54 +54 @@ The device that is used to establish the physical cross connect to the Megaport -## Configuring AWS Direct Connect +## Configuring Direct Connect @@ -58 +58 @@ The device that is used to establish the physical cross connect to the Megaport -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). @@ -66 +66 @@ 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 AWS 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 AWS 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. @@ -71 +71 @@ 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). @@ -77 +77 @@ 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 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 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.