Linking Lambda as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Lambda connector syncs instances, instance types, filesystems, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Lambda API key to pull your Lambda (Lambda Labs) GPU cloud data.
You can create an API key in the API keys section of your Lambda dashboard. The key has account-wide access.
You'll be asked for:
- API key: for example
secret_....
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some Lambda tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
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 | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.