Pre-flight
Before requesting an integration from the Bifrost team, gather the information below. Having these details ready ensures we can set up your business unit, register your controller schemas, and grant access to your cloud account in a single pass.
Business unit
Every IoT Gateway is associated with a business unit so Bifrost knows where to route its telemetry and who manages the device. Check the Roadmap first to see if your business unit is already integrated. If it is not listed, prepare:
- A. Name: The display name of your business unit (for example,
Lynx Fleet Container). - B. Key: A short, lowercase identifier (for example,
lfc). Bifrost uses this key to name your IAM roles and telemetry stream, as shown in Integration deliverables.
Controllers
An IoT Gateway collects data from one or more edge controllers (such as a TRU controller or a battery pack manager). Check the Roadmap to see which controllers are already supported. For each new controller your integration requires, confirm:
- C. Telemetry schema: The Protobuf (
.proto) definition describing the controller's payload. Bifrost registers this schema so incoming messages can be decoded downstream. See Schemas. - D. Firmware integration status: Confirmation of whether the controller and IoT Gateway firmware already emit payloads matching that schema.
Make sure your firmware integration is tracking alongside your onboarding request. Bifrost can register the .proto schema ahead of time, but until the device firmware is communicating using that agreed schema, payloads cannot be decoded and no telemetry will be available for consumption via the Data API or the telemetry stream.
Consumer account
All authentication in Bifrost uses AWS IAM roles. Prepare:
- E. AWS Account ID: The 12-digit AWS account ID that will be the principal allowed to assume your business unit's roles. See Authenticating.