Network Transports

Network Transports enable Firetiger to connect to databases and services on private networks that are not directly reachable from the public internet.

When you create a database connection that targets a host on a private network, you can attach a network transport to route traffic through a secure tunnel instead of attempting a direct connection over the public network.

How It Works

  1. You configure a network transport with credentials for a supported networking provider (e.g., Tailscale)
  2. You create a connection and set its network_transport field to reference the transport
  3. When an agent queries the connection, Firetiger’s proxy server joins the private network on-demand and tunnels the connection traffic through it

Supported Providers

Provider Description
Tailscale Connect to databases on a Tailscale tailnet using OAuth client credentials

Creating a Network Transport

Network transports can be created via the UI:

https://ui.ft-kernel.firetigerapi.com/integrations/network-transports

ftops api network-transports create --id <transport-id> --from-file transport.json

See the provider-specific documentation for the required configuration fields.

Attaching a Transport to a Connection

When creating or updating a database connection, set the network_transport field to reference the transport by name:

{
  "displayName": "Private Database",
  "description": "PostgreSQL database on private network",
  "connectionType": "CONNECTION_TYPE_POSTGRES",
  "networkTransport": "network-transports/<transport-id>",
  "connectionDetails": {
    "postgres": {
      "host": "db.internal.example.com",
      "port": 5432,
      "database": "mydb",
      "username": "firetiger",
      "password": "secret",
      "sslMode": "require"
    }
  }
}

The agent will automatically route traffic through the network transport when querying this connection.


Table of contents


This site uses Just the Docs, a documentation theme for Jekyll.