Skip to content

Change UseVPC to DdUseVPC in PrivateLink documentation #732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ge0Aja merged 1 commit into from
Feb 11, 2025
Merged

Change UseVPC to DdUseVPC in PrivateLink documentation #732

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion aws/logs_monitoring/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,7 +261,7 @@ You can run the Forwarder in a VPC private subnet and send data to Datadog over
1. Follow [these instructions][14] to add the Datadog `api`, `http-logs.intake`, and `trace.agent` endpoints to your VPC.
2. Follow the [instructions][15] to add the AWS Secrets Manager and S3 endpoints to your VPC.
3. When installing the Forwarder with the CloudFormation template:
1. Set `UseVPC` to `true`.
1. Set `DdUseVPC` to `true`.
2. Set `VPCSecurityGroupIds` and `VPCSubnetIds` based on your VPC settings.
3. Set `DdFetchLambdaTags` to `false`, because AWS Resource Groups Tagging API doesn't support PrivateLink.

Expand Down