Saltar al contenido

CUDOS dashboard duplicated data from source stack

0

I deployed the destination stack in Account A (which hosts QuickSight) and the source stack in Account B, both within the same organization. However, the CUR data from Account B appears to include duplicate records from Account A, which caused the CUDOS summary_view to show doubled costs.

After removing the source stack from Account B, the QuickSight metrics are now accurate. Is there a parameter in the source stack that controls which accounts are included in the CUR data?

preguntada hace 2 meses51 visualizaciones
2 Respuestas
6

There is no direct “account filter” parameter, but inclusion is controlled by:

  1. CUR Configuration in the Management Account • CUR must be configured to include linked accounts. • The CUR file includes line_item_usage_account_id and bill_payer_account_id fields that identify which account the usage belongs to.
  2. Source Stack Athena Queries • The source stack uses Athena queries to transform CUR data. • These queries can be modified to filter out specific accounts using WHERE clauses like:
WHERE line_item_usage_account_id NOT IN ('AccountA', 'AccountB')
  1. S3 Replication and Glue Catalog • If both accounts are replicating the same CUR files to their own buckets and defining overlapping Glue tables, they may ingest the same data twice.
EXPERTO
respondido hace 2 meses
0

Hello,

As mentioned above, there is no direct “account filter” parameter as such.

However, as the CUR file includes the columns like "line_item_usage_account_id" and "bill_payer_account_id" that identify which account the usage belongs to.

However, the source stack uses Athena queries to transform CUR data. These queries can be modified to filter out specific accounts using WHERE clauses like:

WHERE line_item_usage_account_id NOT IN ('AccountA', 'AccountB') Or WHERE line_item_usage_account_id != 'AccountA'

If you would like to discuss more on this, please feel free to open a support case with AWS using the following link and we would be happy to help.

Link to raise case: https://support.console.aws.amazon.com/support/home#/case/create

Thanks!

AWS
respondido hace 2 meses

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.