Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 19e7bb4

Browse files
committed
Update privatelink-service.md
1 parent b1e3767 commit 19e7bb4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/cloud/project/privatelink-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Choose one of the PrivateLink connection types best suited for your {{site.data.
4242
- A connection between the Adobe VPC and the customer VPC
4343

4444
{:.bs-callout-tip}
45-
Work with your network administrator or Cloud platform provider for help with selecting the PrivateLink connection type, or help with VPC setup and administration. See your Cloud platform PrivateLink documentation: [AWS PrivateLink][] or [Azure Private Link][].
45+
Work with your network administrator or Cloud platform provider for help with selecting the PrivateLink connection type, or help with VPC setup and administration. See Cloud platform PrivateLink documentation: [AWS PrivateLink][] or [Azure Private Link][].
4646

4747
## Request PrivateLink enablement
4848

@@ -53,7 +53,7 @@ Enabling PrivateLink can take up to _five_ business days. Providing incomplete o
5353

5454
- {:.fix}A Cloud account (AWS or Azure) in the same region as the {{site.data.var.ece}} instance.
5555
- {:.fix}A VPC in the customer environment that hosts the services to connect via PrivateLink. See the AWS or Azure documentation for help with VPC setup or contact your network administrator.
56-
- {:.fix}For bidirectional PrivateLink connections, you must create the endpoint service configuration for your application or service, and create an endpoint in your VPC environment before requesting PrivateLink enablement. See [Set up for bidirectional PrivateLink connections](#set-up-for-bidirectional-privateLink-connections).
56+
- {:.fix}For bidirectional PrivateLink connections, you must create the endpoint service configuration for your application or service, and create an endpoint in your VPC environment before requesting PrivateLink enablement. See [Set up for bidirectional PrivateLink connections](#set-up-for-bidirectional-privatelink-connections).
5757
- {:.fix}Gather the following data required for PrivateLink enablement:
5858

5959
- **Customer Cloud account number** (AWS or Azure)–Must be in the same region as the {{site.data.var.ece}} instance

0 commit comments

Comments
 (0)