Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/agent/guide/gcp-private-service-connect.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Ensure that the IP address in the response matches the one associated with your
{{% site-region region="eu" %}}
[Private Service Connect][1] (PSC) allows you to send telemetry to Datadog without using the public internet.

Datadog exposes some of its data intake services in Google Cloud Platform as PSC [_published services_][2], as seen in the [table of published services](#published-services).
Datadog exposes some of its data intake services in Google Cloud Platform as PSC [_published services_][2], as seen in the [table of published services](#published-services-1).

You can configure a PSC endpoint to expose a private IP address for each Datadog intake service. This IP address routes traffic to the Datadog backend. You can then configure a Google Cloud [_Private DNS Zone_][3] to override the DNS names corresponding to the products for each endpoint that is consumed.

Expand All @@ -136,7 +136,7 @@ You can configure a PSC endpoint to expose a private IP address for each Datadog
{{< img src="agent/guide/psc/connect-endpoint-eu1.png" alt="Screenshot of a 'Connect endpoint' page in the Google Cloud console" >}}

- Under **Target**, select _Published service_.
- For **Target service**, enter the _PSC target name_ that corresponds to the Datadog intake service that you want to use. You can find your PSC target name in the [table of published services](#published-services).
- For **Target service**, enter the _PSC target name_ that corresponds to the Datadog intake service that you want to use. You can find your PSC target name in the [table of published services](#published-services-1).
- For **Endpoint name**, enter a unique identifier to use for this endpoint. You can use `datadog-<SERVICE>`. For example: `datadog-metrics`.
- For **Network** and **Subnetwork**, choose the network and subnetwork where you want to publish your endpoint.
- For **IP address**, click the dropdown and select _Create IP address_ to create an internal IP from your subnet dedicated to the endpoint. Select this IP.
Expand All @@ -154,7 +154,7 @@ You can configure a PSC endpoint to expose a private IP address for each Datadog

- Under **Zone type**, select _Private_.
- For **Zone name**, enter a descriptive name for your zone.
- For **DNS name**, enter the _private DNS name_ that corresponds to the Datadog intake service that you want to use. You can find your DNS name in the [table of published services](#published-services).
- For **DNS name**, enter the _private DNS name_ that corresponds to the Datadog intake service that you want to use. You can find your DNS name in the [table of published services](#published-services-1).
3. Next, create an `A` record that points to the endpoint IP. On the _Zone details_ page of the zone you created, click on **Add record set**.
{{< img src="agent/guide/psc/create-record-eu1.png" alt="Screenshot of the 'Create record set' page in the Google Cloud console." >}}

Expand Down
Loading