Private Link

Nimbus lets you set up private connectivity between your cloud provider and Nimbus.

How it Works

Datadog to Nimbus

With Nimbus Private Link, you can directly connect your VPC with Nimbus using AWS VPC Endpoints. Note that this is currently only supported for AWS accounts in region us-east-1.

Benefits

• cost reduction: with private link, your egress cost go down by 90% (regular egress on AWS is $0.09/GB. With private link, this becomes $0.01/GB)

• compliance and security: prevent sensitive data from traversing the public internet

Setup

1. Create a VPCEndpoint using our cloudformation template

Ensure Cloudformation stack is in status CREATE_COMPLETE and VPC Endpoint is Available with has Private DNS names enabled before proceeding

Nimbus Private Link Setup

2. Verify the connection

You can test the endpoint by sending data to $API_KEY-http-intake.privatelink.logs.us1.nimbus.dev in a connected subnet

curl -v -d "{msg: ping}" https://$API_KEY-http-intake.privatelink.logs.us1.nimbus.dev 

NOTE: Sending the request outside of the connected VPC will result in 403 response

3. Update your Nimbus Endpoints

To switch over to private link, update your Nimbus endpoint. to the new schema by adding privatelink to your Nimbus endpoint.

See integrations specific docs for your integration endpoints.

- https://$API_KEY-$INTEGRATION-intake.logs.us1.nimbus.dev
+ https://$API_KEY-$INTEGRATION-intake.privatelink.logs.us1.nimbus.dev