Currently the AWS billing module takes in an arbitrary number of group_by dimensions. However it uses each one individually pairing it with a group_by tag. Not having multi dimension search makes the data for consolidated billing much less useful.
For example,
If you have 10 accounts and you scan your management account with LINKED_ACCOUNT and SERVICES dimensions.
With the current AWS Billing Module, you'll get two sets of documents.
- Documents with a summary of total service usage across all accounts.
- Documents with a summary of total bill for each account.
This means that you cannot drill into how much usage each account had by service.
Ideally the module would accept pairs of group_by values. If you pass those same two group_by dimensions to the api together you get one document per account per service, which allows much deeper filtering.
There are some more details here.
Currently the AWS billing module takes in an arbitrary number of group_by dimensions. However it uses each one individually pairing it with a group_by tag. Not having multi dimension search makes the data for consolidated billing much less useful.
For example,
If you have 10 accounts and you scan your management account with LINKED_ACCOUNT and SERVICES dimensions.
With the current AWS Billing Module, you'll get two sets of documents.
This means that you cannot drill into how much usage each account had by service.
Ideally the module would accept pairs of group_by values. If you pass those same two group_by dimensions to the api together you get one document per account per service, which allows much deeper filtering.
There are some more details here.