Overview
Lyft Data connects to common object stores, analytics platforms, and SIEM destinations. Use this overview to verify what is production-ready and decide which detailed guide to follow next.
Supported today
| Integration | Source inputs | Destination outputs |
|---|---|---|
| Amazon S3 & compatible object storage | s3 | s3 |
| Azure Blob Storage | azure-blob | azure-blob |
| CrowdStrike Falcon LogScale | — | http-post, splunk-hec, s3 |
| FileStore (local object store) | file-store | file-store |
| Google Analytics (GA4) | s3, gcs | — |
| Google Ad Manager (GAM) | s3, gcs | — |
| Google Cloud Storage (GCS) | gcs | gcs |
| Grafana JSON datasource | — | http-post |
| Splunk Cloud / Enterprise | — | splunk-hec |
| Twilio Segment | s3, azure-blob, gcs, http-poll | — |
Coming soon (gated)
The following connectors are still being documented and are hidden from the public site until the guides are ready:
- CrowdStrike Detection Monitoring (input)
- Elastic (output)
- Logsign (output)
- Microsoft Sentinel (input / output)
- Microsoft Windows (input)
- Scuba Analytics (input / output)
Reach out through the Lyft Data community if you need help with one of the gated connectors.
Where to go next
- Review connector prerequisites in the Integrations index to jump straight to setup guides.
- Start with storage patterns such as S3 or GCS if you are moving files today.
- When wiring SaaS or SIEM destinations, combine these pages with the CI/CD automation guide so promotions stay predictable.
- For new integrations, capture feedback and gaps in the product backlog so the catalog stays current.
Need a printable summary? Use the Integrations index table and filter on the direction that matches your use case.