Accounts and integrations
Dashbird provides a flexible way of managing and organising AWS environments into logical groupings. This enables organisations to manage access across different environments and products and also configure resource or user-level access policies.
There are three entities to account management: Organisation, Account and Integration. This is how they relate to each-other:
Organisation is a top-level entity in Dashbird and usually corresponds to a company or a group that is using Dashbird. Organisation holds accounts and users.
Everything under an account is centralised into one Dashbird interface. The events, inventory, dashboard and other features always show information across one account. As a user, you can switch between accounts of your organisation from the bottom left corner of your screen.
Accounts can we defined as environments or products depending on your preferred structure. You can create as many AWS accounts under an organisation as necessary. Usually we see our customers using accounts to separate between development stages such as Production, Development, Staging etc. or in some cases by different products of a company. An account can have one or multiple integrations (AWS accounts) connected to it.
Also, user permissions can be managed based on accounts, enabling you to manage access between certain environments. Read more about user permission management.
Integrations equal AWS accounts. One account can have one or many delegations attached to it.
Note that one AWS account should never be attached multiple times to Dashbird as it is likely to break the integration or cause unexpected issues.
To add an integration, navigate to Settings -> (Account) Integrations.
You can read more about managing integrations and resources in “Selecting resources to monitor” page.