Lambda
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect Lambda to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your Lambda API key to pull your Lambda (Lambda Labs) GPU cloud data into the PostHog Data warehouse.
You can create an API key in the API keys section of your Lambda dashboard. The key has account-wide access.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Linking Lambda to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Lambda
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
instances | Your running Lambda GPU cloud instances, including their instance type, region, and network details. | Full refresh | — | — |
instance_types | The catalog of available Lambda instance types with pricing, hardware specs, and regional availability. | Full refresh | — | — |
filesystems | Your shared filesystems that can be mounted to instances. | Full refresh | — | — |
images | The machine images available in Lambda Cloud for launching instances. | Full refresh | — | — |
ssh_keys | The SSH keys stored on your account that can be used to access instances over SSH. | Full refresh | — | — |
firewall_rulesets | Collections of firewall rules that can be associated with instances. | Full refresh | — | — |
regions | The Lambda Cloud regions available to your account. | Full refresh | — | — |
audit_events | Your account's audit log: a historical, immutable stream of actions performed against Lambda resources. | Incremental, Full refresh | event_time | — |
tickets | Your Lambda support tickets, including their status, severity, and comment history. | Full refresh | — | — |