🔐 AWS PrivateLink

This guide walks you through how to configure AWS PrivateLink for use with Levitate to send write requests over the private network.


The process consists of configuring an internal endpoint in your VPC which can talk to Levitate endpoint without going via a public network.


Get Levitate PrivateLink Service name

Currently, Levitate supports three regions - eu-west-1, us-east-1 and ap-south-1.

You can choose the service name from the following list.



This is applicable only to customers hosted on app.last9.io. If you are using an on-premise hosted Levitate offering, the Last9 Customer Success team will provide the right endpoint details to you.

Please reach out to us on [email protected].

RegionTypeService NameDNS

Create an endpoint in your VPC

Navigate to the VPC section, and select Endpoints in the left sidebar.

Click on Create Endpoint in the top right corner. Enter an appropriate Name tag, and Select Other endpoint services .

Enter the Service name provided by Last9 in the earlier step and Click Verify service.

Additional settings

  • Select the VPC for the endpoint, and in additional settings, check the box for Enable DNS Name.

  • Select the subnets where you are running the workloads that will read or write to Levitate.

  • Attach a security group to the endpoint; the endpoint must allow traffic on port 443 from your origin VPC or the specific IP address where the requests originate.
    Note: For any on-premise Levitate setups, the endpoint must allow traffic for ports 80 and 443.


After the Endpoint status becomes available, validate that the DNS records change from any machine inside a subnet in your VPC for which the Endpoint is enabled.

For example, dig app-tsdb.last9.io should not return the public IP address; instead, it should return the private IP address of the Endpoint we just created.

That's all. Happy sending data to Levitate using PrivateLink!


Please get in touch with us on Discord or Email if you have any questions.

What’s Next