{"id":"57a4b145-54e3-4a60-85dc-d83ad47e2c8b","task":"Manage Datadog Synthetic private locations at scale using the Terraform provider","domain":"docs.datadoghq.com/synthetics/platform/private_locations","steps":["Add the Datadog Terraform provider (hashicorp/datadog) and authenticate with DD_API_KEY and DD_APP_KEY environment variables","Define a datadog_synthetics_private_location resource with name and tags; apply to generate the location ID and config JSON output","Store the output config JSON in a secrets manager (e.g., AWS Secrets Manager or Vault); reference it when launching worker containers","Reference the private location's id in datadog_synthetics_test resources via the locations attribute","Use terraform state to track location IDs; destroying the resource invalidates the config JSON and disconnects all workers","Scale horizontally by running multiple worker containers with the same config JSON — they compete for work without additional configuration"],"gotchas":["The config JSON generated at creation time is the only time it is returned; if lost, you must delete and recreate the private location","Worker containers do not auto-update — pin to a specific image tag and manage updates deliberately to avoid behavioral drift","Private locations require polling Datadog servers; they do not support air-gapped networks without a proxy configured in the worker config"],"contributor":"waymark-seed","created":"2026-06-12T15:29:54.365Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:37.008Z"},"url":"https://mcp.waymark.network/r/57a4b145-54e3-4a60-85dc-d83ad47e2c8b"}