From b151899370a2867449103a279a230bd850f15820 Mon Sep 17 00:00:00 2001 From: perzycharles Date: Thu, 15 Jan 2026 14:27:13 +0900 Subject: [PATCH 1/2] correct privatelink wording --- aws/logs_monitoring/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/aws/logs_monitoring/README.md b/aws/logs_monitoring/README.md index 41055dcfc..f335b15b4 100644 --- a/aws/logs_monitoring/README.md +++ b/aws/logs_monitoring/README.md @@ -349,7 +349,7 @@ You can run the Forwarder in a VPC private subnet and send data to Datadog over 3. When installing the Forwarder with the CloudFormation template: 1. Set `DdUseVPC` to `true`. 2. Set `VPCSecurityGroupIds` and `VPCSubnetIds` based on your VPC settings. - 3. Set `DdFetchLambdaTags`, `DdFetchStepFunctionsTags`, and `DdFetchS3Tags` to `false`, because AWS Resource Groups Tagging API doesn't support PrivateLink. + 3. If you set any of `DdFetchLambdaTags`, `DdFetchStepFunctionsTags`, or `DdFetchS3Tags` to `true`, add the [AWS Resource Groups Tagging API endpoint][26] to your VPC. If you set `DdFetchLogGroupTags` to `true`, add the Amazon CloudWatch Logs endpoint to your VPC. ### AWS VPC and proxy support @@ -859,3 +859,4 @@ Additional helpful documentation, links, and articles: [23]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html [24]: https://docs.datadoghq.com/logs/log_configuration/processors/?tab=ui#log-date-remapper [25]: https://github.com/DataDog/datadog-serverless-functions/blob/master/aws/logs_monitoring/CHANGELOG.md +[26]: https://docs.aws.amazon.com/vpc/latest/privatelink/aws-services-privatelink-support.html \ No newline at end of file From 658421ea4fbe702886ee5d3e7a703fdd434e5843 Mon Sep 17 00:00:00 2001 From: Georgi Date: Thu, 15 Jan 2026 09:27:27 +0100 Subject: [PATCH 2/2] add more links --- aws/logs_monitoring/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/aws/logs_monitoring/README.md b/aws/logs_monitoring/README.md index f335b15b4..eba5ab0aa 100644 --- a/aws/logs_monitoring/README.md +++ b/aws/logs_monitoring/README.md @@ -349,7 +349,7 @@ You can run the Forwarder in a VPC private subnet and send data to Datadog over 3. When installing the Forwarder with the CloudFormation template: 1. Set `DdUseVPC` to `true`. 2. Set `VPCSecurityGroupIds` and `VPCSubnetIds` based on your VPC settings. - 3. If you set any of `DdFetchLambdaTags`, `DdFetchStepFunctionsTags`, or `DdFetchS3Tags` to `true`, add the [AWS Resource Groups Tagging API endpoint][26] to your VPC. If you set `DdFetchLogGroupTags` to `true`, add the Amazon CloudWatch Logs endpoint to your VPC. + 3. If you set any of `DdFetchLambdaTags`, `DdFetchStepFunctionsTags`, or `DdFetchS3Tags` to `true`, add the [AWS Resource Groups Tagging API endpoint][26] to your VPC. If you set `DdFetchLogGroupTags` to `true`, add the [Amazon CloudWatch Logs endpoint][26] to your VPC. Check [this link][27] for further information on how to create required Datadog endpoints, and [this link][28] for creating AWS services endpoints. ### AWS VPC and proxy support @@ -859,4 +859,6 @@ Additional helpful documentation, links, and articles: [23]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html [24]: https://docs.datadoghq.com/logs/log_configuration/processors/?tab=ui#log-date-remapper [25]: https://github.com/DataDog/datadog-serverless-functions/blob/master/aws/logs_monitoring/CHANGELOG.md -[26]: https://docs.aws.amazon.com/vpc/latest/privatelink/aws-services-privatelink-support.html \ No newline at end of file +[26]: https://docs.aws.amazon.com/vpc/latest/privatelink/aws-services-privatelink-support.html +[27]: https://docs.datadoghq.com/agent/guide/private-link/?tab=crossregionprivatelinkendpoints#create-your-vpc-endpoint +[28]: https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint