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/setup/aws/lambda/dotnet.md
+66-48Lines changed: 66 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ further_reading:
21
21
Configuring App and API Protection (AAP) for AWS Lambda involves:
22
22
23
23
1. Identifying functions that are vulnerable or are under attack, which would most benefit from AAP. Find them on [the Security tab of your Software Catalog][1].
24
-
2. Setting up AAP instrumentation by using either the [Datadog CLI](https://docs.datadoghq.com/serverless/serverless_integrations/cli), [AWS CDK](https://github.com/DataDog/datadog-cdk-constructs), [Datadog Serverless Framework plugin][7], or manually by using the Datadog tracing layers.
24
+
2. Setting up AAP instrumentation by using either the [Datadog CLI](https://docs.datadoghq.com/serverless/serverless_integrations/cli), [AWS CDK](https://github.com/DataDog/datadog-cdk-constructs), [Datadog Serverless Framework plugin][2], or manually by using the Datadog tracing layers.
25
25
3. Triggering security signals in your application and seeing how Datadog displays the resulting information.
26
26
27
27
## Prerequisites
@@ -31,7 +31,7 @@ Configuring App and API Protection (AAP) for AWS Lambda involves:
31
31
32
32
## Compatibility
33
33
34
-
**Note**: Threat Protection through Remote Configuration is not supported. Use [Workflows][5] to block IPs in your [WAF][6].
34
+
**Note**: Threat Protection through Remote Configuration is not supported. Use [Workflows][3] to block IPs in your [WAF][4].
35
35
36
36
## Supported trigger types
37
37
Threat Detection supports HTTP requests as function input only, as that channel has the highest likelihood of attackers exploiting a serverless application. HTTP requests typically come from AWS services such as:
@@ -48,7 +48,7 @@ Threat Detection supports HTTP requests as function input only, as that channel
48
48
{{< tabs >}}
49
49
{{% tab "Serverless Framework" %}}
50
50
51
-
The [Datadog Serverless Framework plugin][7] can be used to automatically configure and deploy your lambda with AAP.
51
+
The [Datadog Serverless Framework plugin][2] can be used to automatically configure and deploy your lambda with AAP.
52
52
53
53
To install and configure the Datadog Serverless Framework plugin:
54
54
@@ -72,9 +72,9 @@ To install and configure the Datadog Serverless Framework plugin:
72
72
enableDDTracing: true
73
73
enableASM: true
74
74
```
75
-
See also the complete list of [plugin parameters][9] to further configure your lambda settings.
75
+
See also the complete list of [plugin parameters][5] to further configure your lambda settings.
76
76
77
-
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][3].
77
+
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][6].
78
78
79
79
{{% /tab %}}
80
80
{{% tab "Datadog CLI" %}}
@@ -97,7 +97,7 @@ The Datadog CLI modifies existing Lambda function configurations to enable instr
97
97
98
98
3. Configure the AWS credentials:
99
99
100
-
Datadog CLI requires access to the AWS Lambda service, and depends on the AWS JavaScript SDK to [resolve the credentials][10]. Ensure your AWS credentials are configured using the same method you would use when invoking the AWS CLI.
100
+
Datadog CLI requires access to the AWS Lambda service, and depends on the AWS JavaScript SDK to [resolve the credentials][7]. Ensure your AWS credentials are configured using the same method you would use when invoking the AWS CLI.
101
101
102
102
4. Configure the Datadog site:
103
103
@@ -136,12 +136,12 @@ The Datadog CLI modifies existing Lambda function configurations to enable instr
136
136
137
137
**Note**: Instrument your Lambda functions in a development or staging environment first. If the instrumentation result is unsatisfactory, run `uninstrument` with the same arguments to revert the changes.
138
138
139
-
Additional parameters can be found in the [CLI documentation][11].
139
+
Additional parameters can be found in the [CLI documentation][8].
140
140
141
141
{{% /tab %}}
142
142
{{% tab "AWS CDK" %}}
143
143
144
-
The [Datadog CDK Construct][12] automatically installs Datadog on your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog through the Datadog Lambda Extension.
144
+
The [Datadog CDK Construct][9] automatically installs Datadog on your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog through the Datadog Lambda Extension.
145
145
146
146
1. Install the Datadog CDK constructs library:
147
147
@@ -175,47 +175,67 @@ The [Datadog CDK Construct][12] automatically installs Datadog on your functions
175
175
176
176
To fill in the placeholders:
177
177
- Replace `<DATADOG_SITE>` with {{< region-param key="dd_site" code="true" >}} (ensure the correct SITE is selected on the right).
178
-
- Replace `<DATADOG_API_KEY_SECRET_ARN>` with the ARN of the AWS secret where your [Datadog API key][13] is securely stored. The key needs to be stored as a plaintext string (not a JSON blob). The `secretsmanager:GetSecretValue` permission is required. For quick testing, you can use `apiKey` instead and set the Datadog API key in plaintext.
178
+
- Replace `<DATADOG_API_KEY_SECRET_ARN>` with the ARN of the AWS secret where your [Datadog API key][10] is securely stored. The key needs to be stored as a plaintext string (not a JSON blob). The `secretsmanager:GetSecretValue` permission is required. For quick testing, you can use `apiKey` instead and set the Datadog API key in plaintext.
179
179
180
-
More information and additional parameters can be found on the [Datadog CDK documentation][12].
180
+
More information and additional parameters can be found on the [Datadog CDK documentation][9].
181
181
182
182
{{% /tab %}}
183
183
{{% tab "Custom" %}}
184
184
185
-
1. Install the Datadog tracer by configuring the layer ARN that matches your deployment. Replace `<AWS_REGION>` with a valid AWS region such as `us-east-1`:
2. Install the Datadog Lambda Extension by configuring the layers for your Lambda function using the ARN in one of the following formats. Replace `<AWS_REGION>` with a valid AWS region such as `us-east-1`:
Replace `<AWS_REGION>` with a valid AWS region, such as `us-east-1`.
224
+
225
+
3. Set the required environment variables
226
+
227
+
- Set `AWS_LAMBDA_EXEC_WRAPPER` to `/opt/datadog_wrapper`.
228
+
- Set `DD_SITE` to {{< region-param key="dd_site" code="true" >}} (ensure the correct SITE is selected on the right).
229
+
- Set `DD_API_KEY_SECRET_ARN` to the ARN of the AWS secret where your [Datadog API key][10] is securely stored. The key needs to be stored as a plaintext string (not a JSON blob). The `secretsmanager:GetSecretValue` permission is required. For quick testing, you can use `DD_API_KEY` instead and set the Datadog API key in plaintext.
230
+
231
+
4. Enable AAP by adding the following environment variables on your function deployment:
210
232
```yaml
211
233
environment:
212
234
AWS_LAMBDA_EXEC_WRAPPER: /opt/datadog_wrapper
213
235
DD_SERVERLESS_APPSEC_ENABLED: true
214
236
```
215
237
216
-
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][3].
Copy file name to clipboardExpand all lines: content/en/security/application_security/setup/aws/lambda/go.md
+20-24Lines changed: 20 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ further_reading:
21
21
Configuring App and API Protection (AAP) for AWS Lambda involves:
22
22
23
23
1. Identifying functions that are vulnerable or are under attack, which would most benefit from AAP. Find them on [the Security tab of your Software Catalog][1].
24
-
2. Setting up AAP instrumentation by using either the [Datadog CLI](https://docs.datadoghq.com/serverless/serverless_integrations/cli), [AWS CDK](https://github.com/DataDog/datadog-cdk-constructs), [Datadog Serverless Framework plugin][7], or manually by using the Datadog tracing layers.
24
+
2. Setting up AAP instrumentation by using either the [Datadog CLI](https://docs.datadoghq.com/serverless/serverless_integrations/cli), [AWS CDK](https://github.com/DataDog/datadog-cdk-constructs), [Datadog Serverless Framework plugin][2], or manually by using the Datadog tracing layers.
25
25
3. Triggering security signals in your application and seeing how Datadog displays the resulting information.
26
26
27
27
## Prerequisites
@@ -31,7 +31,7 @@ Configuring App and API Protection (AAP) for AWS Lambda involves:
31
31
32
32
## Compatibility
33
33
34
-
**Note**: Threat Protection through Remote Configuration is not supported. Use [Workflows][5] to block IPs in your [WAF][6].
34
+
**Note**: Threat Protection through Remote Configuration is not supported. Use [Workflows][3] to block IPs in your [WAF][4].
35
35
36
36
The Datadog Go tracer is distributed as a Go module rather than a Lambda layer. Ensure your functions vendor the latest `github.com/DataDog/datadog-lambda-go` release when enabling AAP.
37
37
@@ -50,7 +50,7 @@ Threat Detection supports HTTP requests as function input only, as that channel
50
50
{{< tabs >}}
51
51
{{% tab "Serverless Framework" %}}
52
52
53
-
The [Datadog Serverless Framework plugin][7] can be used to automatically configure and deploy your lambda with AAP.
53
+
The [Datadog Serverless Framework plugin][2] can be used to automatically configure and deploy your lambda with AAP.
54
54
55
55
To install and configure the Datadog Serverless Framework plugin:
56
56
@@ -74,9 +74,9 @@ To install and configure the Datadog Serverless Framework plugin:
74
74
enableDDTracing: true
75
75
enableASM: true
76
76
```
77
-
See also the complete list of [plugin parameters][9] to further configure your lambda settings.
77
+
See also the complete list of [plugin parameters][5] to further configure your lambda settings.
78
78
79
-
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][3].
79
+
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][6].
80
80
81
81
{{% /tab %}}
82
82
{{% tab "Datadog CLI" %}}
@@ -99,7 +99,7 @@ The Datadog CLI modifies existing Lambda function configurations to enable instr
99
99
100
100
3. Configure the AWS credentials:
101
101
102
-
Datadog CLI requires access to the AWS Lambda service, and depends on the AWS JavaScript SDK to [resolve the credentials][10]. Ensure your AWS credentials are configured using the same method you would use when invoking the AWS CLI.
102
+
Datadog CLI requires access to the AWS Lambda service, and depends on the AWS JavaScript SDK to [resolve the credentials][7]. Ensure your AWS credentials are configured using the same method you would use when invoking the AWS CLI.
103
103
104
104
4. Configure the Datadog site:
105
105
@@ -138,12 +138,12 @@ The Datadog CLI modifies existing Lambda function configurations to enable instr
138
138
139
139
**Note**: Instrument your Lambda functions in a development or staging environment first. If the instrumentation result is unsatisfactory, run `uninstrument` with the same arguments to revert the changes. After the CLI completes, update your source code to depend on the latest `datadog-lambda-go` module release to enable App and API Protection.
140
140
141
-
Additional parameters can be found in the [CLI documentation][11].
141
+
Additional parameters can be found in the [CLI documentation][8].
142
142
143
143
{{% /tab %}}
144
144
{{% tab "AWS CDK" %}}
145
145
146
-
The [Datadog CDK Construct][12] automatically installs Datadog on your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog through the Datadog Lambda Extension.
146
+
The [Datadog CDK Construct][9] automatically installs Datadog on your functions using Lambda Layers, and configures your functions to send metrics, traces, and logs to Datadog through the Datadog Lambda Extension.
147
147
148
148
1. Install the Datadog CDK constructs library:
149
149
@@ -176,9 +176,9 @@ The [Datadog CDK Construct][12] automatically installs Datadog on your functions
176
176
177
177
To fill in the placeholders:
178
178
- Replace `<DATADOG_SITE>` with {{< region-param key="dd_site" code="true" >}} (ensure the correct SITE is selected on the right).
179
-
- Replace `<DATADOG_API_KEY_SECRET_ARN>` with the ARN of the AWS secret where your [Datadog API key][13] is securely stored. The key needs to be stored as a plaintext string (not a JSON blob). The `secretsmanager:GetSecretValue` permission is required. For quick testing, you can use `apiKey` instead and set the Datadog API key in plaintext.
179
+
- Replace `<DATADOG_API_KEY_SECRET_ARN>` with the ARN of the AWS secret where your [Datadog API key][10] is securely stored. The key needs to be stored as a plaintext string (not a JSON blob). The `secretsmanager:GetSecretValue` permission is required. For quick testing, you can use `apiKey` instead and set the Datadog API key in plaintext.
180
180
181
-
More information and additional parameters can be found on the [Datadog CDK documentation][12].
181
+
More information and additional parameters can be found on the [Datadog CDK documentation][9].
182
182
183
183
{{% /tab %}}
184
184
{{% tab "Custom" %}}
@@ -207,9 +207,8 @@ The [Datadog CDK Construct][12] automatically installs Datadog on your functions
207
207
DD_SERVERLESS_APPSEC_ENABLED: true
208
208
```
209
209
210
-
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][3].
210
+
4. Redeploy the function and invoke it. After a few minutes, it appears in [AAP views][6].
0 commit comments