You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/security/application_security/threats/setup/threat_detection/gcp-service-extensions.md
+26-26Lines changed: 26 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -40,14 +40,14 @@ Before you begin, ensure you have:
40
40
41
41
## Enabling threat detection
42
42
43
-
To set up the ASM Service Extension in your GCP environment, use the Google Cloud Console or Terraform scripts and complete the following steps.
43
+
To set up the AAP Service Extension in your GCP environment, use the Google Cloud Console or Terraform scripts and complete the following steps.
44
44
45
-
**Note:** Google Cloud provides guides for creating [a callout backend service][4] and [configuring a Service Extension as a traffic extension][5]. The following steps use the same general setup but include custom configurations specific to Datadog’s Application Security Management integration.
45
+
**Note:** Google Cloud provides guides for creating [a callout backend service][4] and [configuring a Service Extension as a traffic extension][5]. The following steps use the same general setup but include custom configurations specific to Datadog's App and API Protection integration.
46
46
47
47
{{< tabs >}}
48
48
{{% tab "Google Cloud Console" %}}
49
49
50
-
1. Create a VM Compute instance using the [Datadog ASM Service Extensions Docker image][1].
50
+
1. Create a VM Compute instance using the [Datadog AAP Service Extensions Docker image][1].
51
51
52
52
See [Configuration](#configuration) for available environment variables when setting up your VM instance.
53
53
@@ -79,7 +79,7 @@ To set up the ASM Service Extension in your GCP environment, use the Google Clou
79
79
1. To send all traffic to the extension, insert `true` in the **Match condition**.
80
80
2. For **Programability type**, select `Callouts`.
81
81
3. Select the backend service you created in the previous step.
82
-
4. Select all **Events** from the list where you want ASM to run detection (Request Headers and Response Headers are **required**).
82
+
4. Select all **Events** from the list where you want AAP to run detection (Request Headers and Response Headers are **required**).
83
83
84
84
</br>
85
85
{{% appsec-getstarted-2-plusrisk %}}
@@ -91,7 +91,7 @@ To set up the ASM Service Extension in your GCP environment, use the Google Clou
91
91
92
92
{{% tab "Terraform" %}}
93
93
94
-
You can use Terraform to automate the deployment of the ASM GCP Service Extension. This simplifies the process of setting up the service extension to work with your existing load balancer.
94
+
You can use Terraform to automate the deployment of the AAP GCP Service Extension. This simplifies the process of setting up the service extension to work with your existing load balancer.
95
95
96
96
### Prerequisites for Terraform deployment
97
97
@@ -112,16 +112,16 @@ The Terraform deployment will create the following components:
112
112
113
113
### Deployment Steps
114
114
115
-
The ASM Service Extension deployment requires several components that work together. We'll create a Terraform module that encapsulates all these components, making the deployment process repeatable and easier to maintain.
115
+
The AAP Service Extension deployment requires several components that work together. We'll create a Terraform module that encapsulates all these components, making the deployment process repeatable and easier to maintain.
116
116
117
117
1. Create a new directory and the necessary Terraform files:
2. Add the following code to your `main.tf` file. This file defines all the infrastructure components needed for the ASM Service Extension, including network rules, VM instances, and load balancer configuration:
124
+
2. Add the following code to your `main.tf` file. This file defines all the infrastructure components needed for the AAP Service Extension, including network rules, VM instances, and load balancer configuration:
125
125
126
126
```hcl
127
127
# main.tf
@@ -131,7 +131,7 @@ The ASM Service Extension deployment requires several components that work toget
@@ -467,7 +467,7 @@ Configure the container to send traces to your Datadog Agent using the following
467
467
<strong>Note:</strong> The GCP Service Extensions integration is built on top of the Datadog Go Tracer. It follows the same release process as the tracer, and its Docker images are tagged with the corresponding tracer version.
468
468
</div>
469
469
470
-
The GCP Service Extensions integration uses the [Datadog Go Tracer][6] and inherits all environment variables from the tracer. You can find more configuration options in [Configuring the Go Tracing Library][7] and [ASM Library Configuration][8].
470
+
The GCP Service Extensions integration uses the [Datadog Go Tracer][6] and inherits all environment variables from the tracer. You can find more configuration options in [Configuring the Go Tracing Library][7] and [AAP Library Configuration][8].
0 commit comments