Skip to content

Document the limitations of AWS Billing integration in supporting multiple tags and dimensions. #9278

@agithomas

Description

@agithomas

When using an AWS billing configuration that groups by a combination of tags and dimensions, such as SERVICE and multiple tags (for example, team, project, aws:createdBy), we may end up with multiple duplicates of the same data. This is due to a limitation of the GetCostAndUsage API, which only allows grouping by two groups at once.

Update the AWS Billing integration documentation to highlight this limitation.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions