AWS prescriptive-guidance documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in a sentence about private connectivity requirements.
Security assessment
This is a terminology consistency update rather than a security-related change. The sentence describes an existing security recommendation (using private connectivity), but the edit itself doesn't modify the security guidance or address a specific vulnerability.
Diff
diff --git a/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/use-cases.md b/prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/use-cases.md index f0a01c111..b86ce0549 100644 --- a//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/use-cases.md +++ b//prescriptive-guidance/latest/salesforce-hyperforce-connectivity-dx-megaport/use-cases.md @@ -28 +28 @@ The use cases in the following sections provide examples for how you can enable - * Some aspects of user application logins to Hyperforce still require network connectivity to Salesforce-managed data centers. For this reason, if you require fully private connectivity, you must use SEC with AWS Direct Connect. + * Some aspects of user application logins to Hyperforce still require network connectivity to Salesforce-managed data centers. For this reason, if you require fully private connectivity, you must use SEC with Direct Connect.