Private endpoints
Connect your services to Azure Private Link endpoints to eliminate public internet exposure
Tiger Cloud supports private connectivity through Azure Private Link. Once configured, applications in your Azure Virtual Network reach your service through a private endpoint on Microsoft’s internal network, with no exposure to the public internet. This page walks you through authorizing your Azure subscription in Tiger Console, provisioning the private endpoint in Azure, and attaching it to your service.
Prerequisites
To follow the steps on this page:
- Create a target Tiger Cloud service with the Real-time analytics capability.
- Create an Azure account with an active subscription.
- Configure permissions to create private endpoints.
- Create an Azure Virtual Network with a subnet for the resources you will connect to Tiger Cloud.
Set up a private endpoint connection
Private endpoint connections in Tiger Cloud are currently in private preview. To request access in Tiger Console, go to Security > Private Endpoints and click Request access. Then refresh the page and follow the steps below.
Take the following steps to connect your Tiger Cloud service to a Private Link endpoint.
- Create an Azure subscription authorization
-
In Tiger Console, select
Security>Private Endpoints>Configure Private Endpoint Connection.
-
In
Cloud provider, selectAzure. -
In
Principal ID, enter your Azure subscription ID. Give your authorization a name, for convenience.WarningClick the checkmark next to
Connection nameto save your authorization. Otherwise, your input is discarded. -
Under
Alias, copy the alias for the region in which you need to create the connection. Choose the region closest to your Azure resources for optimal performance. -
Click
Done. Tiger Cloud confirms your authorization. Once it is confirmed, you can connect multiple endpoints from the same authorized subscription.
-
- Create a private endpoint in Azure
-
In Azure Portal, go to
Private endpointsand clickCreate.
-
In
Subscription, select the subscription you have previously authorized in Tiger Cloud. -
In
Resource group, select an existing resource group or create a new one for your private endpoint. -
Provide a name for your endpoint.
-
Select the region where your Virtual Network is deployed, then click
Next: Resource. -
In
Connection method, selectConnect to an Azure resource by resource ID or alias. -
In
Resource ID or alias, paste the alias you have copied from Tiger Console. -
In
Request message, enter your Tiger Cloud project ID, then clickNext: Virtual Network. -
Select the Virtual Network that contains the resources you want to connect to Tiger Cloud, then choose the subnet where the endpoint’s private IP will be created. Optionally select an application security group, then click
Next: DNS. -
Optionally configure private DNS integration and tags for your endpoint, then click
Next: Review + create. -
Review your config and click
Create. Azure creates your private endpoint. Wait for the deployment to succeed. -
Go to
Private endpointsand copy the private endpoint IP from thePrivate IPcolumn.
-
- Sync the connection
-
In Tiger Console >
Security>Private Endpoints, clickRefresh. Tiger Cloud automatically approves connections from authorized subscriptions. Your connection appears in the list.
-
Under
IP AddressclickAdd IPand paste the private endpoint IP address you have copied from Azure Portal. -
Under
ServicesclickAttach service. Select your service from the dropdown and clickAttach. You can attach a service to one private endpoint. -
From a VM inside your Azure VNet, connect to your service using a connection string with your connection details. You should be able to connect successfully.
-
Manage connections
- To detach a service from a private endpoint connection, go to
Security>Private Endpoints, expand the arrow in theServicescolumn, and click the trash icon next to the service connection string. - To edit or remove an endpoint connection, go to
Security>Private Endpointsand click the three dots next to the connection in the list. SelectEditorDisconnect, respectively. You need to detach all services from a private endpoint connection before deleting it. - To remove an authorization, click
Manage Authorizations> trash bin icon. You need to disconnect all relevant endpoint connections before removing an authorization.