Skip to main content

Sumo Logic Connector for AWS Privatelink


This feature is in Beta. To participate, contact your Sumo Logic account executive.

AWS PrivateLink provides private connectivity between VPCs, AWS services, and your on-premises networks, without exposing your traffic to the public internet.

To send data to Sumo Logic through AWS PrivateLink, you'll need to configure an internal endpoint in your VPC for Installed Collectors to send data to.

With the NLB created and ALB registered as a target, requests over AWS PrivateLink to the NLB are forwarded to the ALB.

Sumo Logic exposes AWS PrivateLink endpoints to different regions that depend on your Sumo Logic deployment. If you're using the VPC in a different region you need to set up VPC peering. Either way, you'll need to create an endpoint.

Create an endpoint to connect with the Sumo Logic endpoint service

  • The service name is provided by Sumo Logic and will accept the endpoint connection request once we know you initiated the connection.
  • Select the VPC where the Sumo Logic collector will be installed or where HTTP requests will be made for HTTP Sources.


No VPC Peering

If the VPC is in the same AWS region as your deployment you don't need to set up VPC peering. Navigate to Actions > Modify private DNS name.


Check the box to enable private DNS names.


VPC Peering

If the VPC is not in the same AWS region as your deployment, you'll need to set up VPC peering.

  1. Create the VPC peering connection between the region for the client-side VPC and the region where the Sumo Logic PrivateLink service is configured.
  2. Create a Route53 private hosted zone. Select the VPC peered in the region where our server-side region is located.
  3. With the created private hosted zone, add an A record. Select the peered VPC in region us-west-2, where the Sumo Logic server-side infrastructure is located.
  4. Add the other peered VPC in the other region into the Route53 hosted zone.
Privacy Statement
Terms of Use

Copyright © 2023 by Sumo Logic, Inc.