AWS prescriptive-guidance documentation change
Summary
Updated references to 'AWS Direct Connect' to 'Direct Connect' throughout the document, removing redundant 'AWS' branding from service names and partner references. No technical changes to guidance or requirements.
Security assessment
The changes are purely terminological, removing 'AWS' from 'AWS Direct Connect' for consistency. No security vulnerabilities, mitigations, or new security features are introduced or modified. Existing security recommendations (e.g., prefix filtering, routing policies) remain unchanged in substance.
Diff
diff --git a/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/components.md b/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/components.md index 81d8b7399..ffae52168 100644 --- a//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/components.md +++ b//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/components.md @@ -5 +5 @@ -AWS Direct ConnectSalesforceMegaport +Direct ConnectSalesforceMegaport @@ -9 +9 @@ AWS Direct ConnectSalesforceMegaport -AWS Direct Connect requires you to either create your own [dedicated connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/dedicated_connection.html) to AWS, or work with an AWS Direct Connect Partner to create a [hosted connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/hosted_connection.html). This article provides guidance for using Megaport as an AWS Direct Connect Partner to facilitate hybrid and multiple use cases for connecting to Salesforce Hyperforce. +Direct Connect requires you to either create your own [dedicated connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/dedicated_connection.html) to AWS, or work with an Direct Connect Partner to create a [hosted connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/hosted_connection.html). This article provides guidance for using Megaport as an Direct Connect Partner to facilitate hybrid and multiple use cases for connecting to Salesforce Hyperforce. @@ -11 +11 @@ AWS Direct Connect requires you to either create your own [dedicated connection] -## AWS Direct Connect +## Direct Connect @@ -13 +13 @@ AWS Direct Connect requires you to either create your own [dedicated connection] -AWS Direct Connect establishes a private, dedicated network connection between on-premises data centers and AWS. This direct link helps organizations bypass the public internet and provides reliable and private communication with AWS resources. +Direct Connect establishes a private, dedicated network connection between on-premises data centers and AWS. This direct link helps organizations bypass the public internet and provides reliable and private communication with AWS resources. @@ -15 +15 @@ AWS Direct Connect establishes a private, dedicated network connection between o -Although Hyperforce runs on AWS infrastructure, using AWS Direct Connect to access it requires you to manage an AWS account for billing and configuration of the connection. Using AWS Direct Connect to connect to the Salesforce-managed Hyperforce AWS account isn't supported. +Although Hyperforce runs on AWS infrastructure, using Direct Connect to access it requires you to manage an AWS account for billing and configuration of the connection. Using Direct Connect to connect to the Salesforce-managed Hyperforce AWS account isn't supported. @@ -19 +19 @@ Although Hyperforce runs on AWS infrastructure, using AWS Direct Connect to acce -A [hosted connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithConnections.html) is a physical Ethernet connection that an AWS Direct Connect Partner provisions on behalf of a user. The use cases and architectures covered in this guide use a hosted connection with the AWS Direct Connect Partner, [Megaport](https://www.megaport.com/). Hosted connections offer bandwidth ranges between 50 Mbps to 25 Gbps in multiple increments, whereas dedicated connections are provided in 1 Gbps, 10 Gbps, and 100 Gbps capacities. For more information about AWS Direct Connect bandwidth and costs, see [AWS Direct Connect pricing](https://aws.amazon.com/directconnect/pricing/). +A [hosted connection](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithConnections.html) is a physical Ethernet connection that an Direct Connect Partner provisions on behalf of a user. The use cases and architectures covered in this guide use a hosted connection with the Direct Connect Partner, [Megaport](https://www.megaport.com/). Hosted connections offer bandwidth ranges between 50 Mbps to 25 Gbps in multiple increments, whereas dedicated connections are provided in 1 Gbps, 10 Gbps, and 100 Gbps capacities. For more information about Direct Connect bandwidth and costs, see [Direct Connect pricing](https://aws.amazon.com/directconnect/pricing/). @@ -27 +27 @@ The Hyperforce architecture requires access to the public IP address space of AW - * Using a public VIF requires the use of unique public IPv4 addresses. You will need to provide your own IPv4 CIDR or request a `/31` CIDR from [AWS Support](https://aws.amazon.com/support/createCase). For more information, see the [prerequisites for virtual interfaces](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#vif-prerequisites) in the AWS Direct Connect documentation. + * Using a public VIF requires the use of unique public IPv4 addresses. You will need to provide your own IPv4 CIDR or request a `/31` CIDR from [AWS Support](https://aws.amazon.com/support/createCase). For more information, see the [prerequisites for virtual interfaces](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html#vif-prerequisites) in the Direct Connect documentation. @@ -29 +29 @@ The Hyperforce architecture requires access to the public IP address space of AW - * 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, review [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) on the Salesforce website. + * 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, review [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) on the Salesforce website. @@ -31 +31 @@ The Hyperforce architecture requires access to the public IP address space of AW - * The prefixes that are 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 information, review [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 that are 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 information, review [public virtual interface routing policies](https://docs.aws.amazon.com/directconnect/latest/UserGuide/routing-and-bgp.html#routing-policies) in the Direct Connect documentation. @@ -46 +46 @@ Salesforce is a customer relationship management (CRM) platform that's designed -[Salesforce Express Connect (SEC)](https://www.salesforce.com/campaign/salesforce-express-connect/) enables private, reliable connectivity from users to Salesforce-operated data centers. Ensuring private connectivity to Hyperforce currently requires a SEC connection in conjunction with AWS Direct Connect. +[Salesforce Express Connect (SEC)](https://www.salesforce.com/campaign/salesforce-express-connect/) enables private, reliable connectivity from users to Salesforce-operated data centers. Ensuring private connectivity to Hyperforce currently requires a SEC connection in conjunction with Direct Connect. @@ -50 +50 @@ Salesforce is a customer relationship management (CRM) platform that's designed - * A limited number of Salesforce services still run in Salesforce-managed infrastructure. To maintain connectivity to all services in Salesforce-managed infrastructure and Hyperforce, users who require private network access to Salesforce must continue to run SEC along with AWS Direct Connect. + * A limited number of Salesforce services still run in Salesforce-managed infrastructure. To maintain connectivity to all services in Salesforce-managed infrastructure and Hyperforce, users who require private network access to Salesforce must continue to run SEC along with Direct Connect. @@ -73 +73 @@ Your network device requires either 10 or 100 Gbps interfaces with 10GBASE-LR (d -[Megaport Virtual Edge (MVE)](https://docs.megaport.com/mve/) is a network functions virtualization (NFV) platform that provides virtual infrastructure for network services at the edge of Megaport's global SDN. You can use MVE to deploy a virtual network stack (or point of presence) without any physical data center presence or hardware. MVE is available in 27 metro regions across the globe and is aligned closely with AWS Direct Connect peering locations (NNIs). MVE supports third-party VNF appliances from vendors such as Aruba, Cisco, Fortinet, Palo Alto Networks, Versa Networks, and VMware. +[Megaport Virtual Edge (MVE)](https://docs.megaport.com/mve/) is a network functions virtualization (NFV) platform that provides virtual infrastructure for network services at the edge of Megaport's global SDN. You can use MVE to deploy a virtual network stack (or point of presence) without any physical data center presence or hardware. MVE is available in 27 metro regions across the globe and is aligned closely with Direct Connect peering locations (NNIs). MVE supports third-party VNF appliances from vendors such as Aruba, Cisco, Fortinet, Palo Alto Networks, Versa Networks, and VMware.