Accounts
Bifrost isolates its deployment stages into separate AWS accounts so that platform development, integration testing, and live production fleet traffic never share infrastructure or credentials. Every account runs an independent instance of the platform in the eu-west-1 (Ireland) region, giving you a dedicated boundary for validating your integration before moving to production.
Because each account is a standalone deployment, isolation applies on both sides of the platform. Downstream consumers use different endpoints and IAM roles for each environment, and IoT Gateway devices also require an environment-specific claim certificate and communicate with a different device endpoint depending on which account they connect to.
Make sure your IoT Gateways and your downstream services target the same Bifrost environment. A device flashed with a test claim certificate and endpoint will only provision and publish telemetry in the test account, and will not be visible when querying the production account.
When you authenticate with Bifrost, construct the target IAM role ARN using the AWS Account ID and Key of the environment you want to reach: arn:aws:iam::{accountId}:role/bifrost-{env}-{level}-{businessUnitKey}-role.
Environment accounts
| Environment | Key | AWS Account ID | Region |
|---|---|---|---|
| Production | prod | 121573399545 | eu-west-1 |
| Pre-production | preprod | — | eu-west-1 |
| Test | test | 506491559852 | eu-west-1 |
| Development | dev | 478815938374 | eu-west-1 |