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: aws/logs_monitoring/README.md
-18Lines changed: 0 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -310,18 +310,6 @@ You can run the Forwarder in a VPC private subnet and send data to Datadog over
310
310
2. Set `VPCSecurityGroupIds` and `VPCSubnetIds` based on your VPC settings.
311
311
3. Set `DdFetchLambdaTags`, `DdFetchStepFunctionsTags` and `DdFetchS3Tags` to `false`, because AWS Resource Groups Tagging API doesn't support PrivateLink.
312
312
313
-
#### DdUsePrivateLink is deprecated
314
-
315
-
The `DdUsePrivateLink` option has been deprecated since [v3.41.0][16]. This option was previously used to instruct the Forwarder to use a special set of PrivateLink endpoints for data intake: `pvtlink.api.{{< region-param key="dd_site" code="true" >}}`, `api-pvtlink.logs.{{< region-param key="dd_site" code="true" >}}`, and `trace-pvtlink.agent.{{< region-param key="dd_site" code="true" >}}`. Since v3.41.0, the Forwarder can send data over PrivateLink to Datadog using the regular DNS names of intake endpoints: `api.{{< region-param key="dd_site" code="true" >}}`, `http-intake.logs.{{< region-param key="dd_site" code="true" >}}`, and `trace.agent.{{< region-param key="dd_site" code="true" >}}`. Therefore, the `DdUsePrivateLink` option is no longer needed.
316
-
317
-
If you have an older deployment of the Forwarder with `DdUsePrivateLink` set to `true`, then you may find mismatches between your configured PrivateLink endpoints and the [ones documented in Datadog][14], which is expected. Although the older PrivateLink endpoints were removed from that doc, they remain to function. When upgrading the Forwarder, there is no change required, that is, you can keep `DdUsePrivateLink` enabled and continue to use the older endpoints.
318
-
319
-
However, if you are interested in switching to the new endpoints, you need to follow the updated instructions above to:
320
-
321
-
1. Set up the new endpoints to `api.{{< region-param key="dd_site" code="true" >}}`, `http-intake.logs.{{< region-param key="dd_site" code="true" >}}`, and `trace.agent.{{< region-param key="dd_site" code="true" >}}`.
322
-
2. Set `DdUseVPC` to `true`.
323
-
3. Set `DdUsePrivateLink` to `false`.
324
-
325
313
### AWS VPC and proxy support
326
314
327
315
If you must deploy the Forwarder to a VPC without direct public internet access, and you cannot use AWS PrivateLink to connect to Datadog (for example, if your organization is hosted on the Datadog EU site: `datadoghq.eu`), then you can send data through a proxy.
@@ -467,9 +455,6 @@ To test different patterns against your logs, turn on [debug logs](#troubleshoot
467
455
`PermissionsBoundaryArn`
468
456
: ARN for the Permissions Boundary Policy.
469
457
470
-
`DdUsePrivateLink` (DEPRECATED)
471
-
: Set to true to enable sending logs and metrics through AWS PrivateLink. See [Connect to Datadog over AWS PrivateLink][2].
472
-
473
458
`DdHttpProxyURL`
474
459
: Sets the standard web proxy environment variables HTTP_PROXY and HTTPS_PROXY. These are the URL endpoints your proxy server exposes. Do not use this in combination with AWS Private Link. Make sure to also set `DdSkipSslValidation` to true.
475
460
@@ -613,9 +598,6 @@ To test different patterns against your logs, turn on [debug logs](#troubleshoot
613
598
`PERMISSIONS_BOUNDARY_ARN`
614
599
: ARN for the Permissions Boundary Policy.
615
600
616
-
`DD_USE_PRIVATE_LINK` (DEPRECATED)
617
-
: Set to true to enable sending logs and metrics through AWS PrivateLink. See [Connect to Datadog over AWS PrivateLink][2].
618
-
619
601
`DD_HTTP_PROXY_URL`
620
602
: Sets the standard web proxy environment variables HTTP_PROXY and HTTPS_PROXY. These are the URL endpoints your proxy server exposes. Do not use this in combination with AWS Private Link. Make sure to also set `DD_SKIP_SSL_VALIDATION` to true.
Copy file name to clipboardExpand all lines: aws/logs_monitoring/template.yaml
+12-24Lines changed: 12 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -180,13 +180,6 @@ Parameters:
180
180
- true
181
181
- false
182
182
Description: Set to false to disable log compression. Only valid when sending logs over HTTP.
183
-
DdUsePrivateLink:
184
-
Type: String
185
-
Default: false
186
-
AllowedValues:
187
-
- true
188
-
- false
189
-
Description: DEPRECATED, DO NOT CHANGE. See README.md for details. Set to true to deploy the Forwarder to a VPC and send logs, metrics, and traces via AWS PrivateLink. When set to true, must also set VPCSecurityGroupIds and VPCSubnetIds.
190
183
DdUseVPC:
191
184
Type: String
192
185
Default: false
@@ -205,11 +198,11 @@ Parameters:
205
198
VPCSecurityGroupIds:
206
199
Type: CommaDelimitedList
207
200
Default: ""
208
-
Description: Comma separated list of VPC Security Group Ids. Used when DdUsePrivateLink or DdUseVPC is enabled.
201
+
Description: Comma separated list of VPC Security Group Ids. Used when DdUseVPC is enabled.
209
202
VPCSubnetIds:
210
203
Type: CommaDelimitedList
211
204
Default: ""
212
-
Description: Comma separated list of VPC Subnet Ids. Used when DdUsePrivateLink or DdUseVPC is enabled.
205
+
Description: Comma separated list of VPC Subnet Ids. Used when DdUseVPC is enabled.
0 commit comments