Importing old CUR reports into CUDOS/CID

0

We have recently migrated all our accounts from an organization built within one payer account to another organization with a different payer account. Is there a way to import the old CURs into the new organization's CUDOS dashboards?

LaPOP
asked a year ago639 views
3 Answers
2
Accepted Answer

Adding a new reply, as I need to format it which is not possible if i provide a comment to your previous question. I am hoping Payer got converted to a linked account when it was moved under the new Organization. If yes, you can check and do something like below.

Prior to Move:

Old Payer (contain 1 Payer and 1 linked account)
 - Nov-2022-cur.parquet
 - Dec-2022-cur.parquet 
New Payer (contain 1 Payer and 2 linked accounts)
- Nov-2022-cur.parquet 
- Dec-2022-cur.parquet 

After Old Payer is moved to the new Payer Org starting Jan 2023:

Old Payer (contain 1 Payer and 1 linked account)
 - Nov-2022-cur.parquet
 - Dec-2022-cur.parquet 
 - NO CUR GENERATED FOR JAN 2023 --> please validate if this is true
New Payer (contain 1 Payer and 4 linked accounts - 2 from new and 2 from old)
- Nov-2022-cur.parquet 
- Dec-2022-cur.parquet 
- Jan-2023-cur.parquet 

For your CUDOS dashboard, a below format will ensure you have option to query both historical and current CUR data from old and new payer.

s3://<prefix>-<destination-accountid>-shared/
	cur/<old-payer-1>/cid/cid/year=2022/month=12/*.parquet
	cur/<new-payer-1>/cid/cid/
                     year=2022/
                            month=12/*.parquet
                     year=2023/
                            month=01/*.parquet
AWS
EXPERT
Gokul
answered a year ago
  • Sorry that I didn't reply sooner. The issue was indeed related to the paths of the two CUR data. Once that got sorted out, everything works fine! Thank you for the help!

  • Is this option worked?

1

It is possible to integrate the cost dashboards on top of multiple Management (Payer) Accounts or multiple linked accounts, using the Advanced Setup documented in well architected labs. In your case, you can check to see the existing CUR structure and see if you can extend it by moving your CUR reports in the structure like below.

s3://<prefix>-<destination-accountid>-shared/
	cur/<src-account1>/cid/cid/year=XXXX/month=YY/*.parquet
	cur/<src-account2>/cid/cid/year=XXXX/month=YY/*.parquet
	cur/<src-account3>/cid/cid/year=XXXX/month=YY/*.parquet
AWS
EXPERT
Gokul
answered a year ago
0

Thank you for your reply. I wanted to ask one additional question - the old payer account is now part of the new organization. Would this scenario work as well?

LaPOP
answered a year ago
  • When you move the old payer to the new org, it will loose a capacity to produce CUR for linked accounts but it will still produce CUR for himself. It make sense to make sure this information is not duplicated (coming from both - the old and the new payer). Other than that it should work.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions