Hi all,
I would like get cost and usage report data from multiple accounts as different datasets in Quicksight in order to create one dashboard showing cross-account costs for e.g. the resources tagged as “tag-z”.
Let’s assume that I need to manage three accounts, each including its own S3 bucket for cost and usage report:
Account A: S3 bucket for cur_A
Account B: S3 bucket for cur_B
Account C: S3 bucket for cur_C
I log into Quicksight from account A and I create my dashboard including cur_A.
Now, from my Quicksight account A, I want to include cur_B and cur_C as datasets.
I already added cur_B and cur_C as S3 buckets You can Access Across AWS under Manage Quicksight > Security & permissions > Access granted to * services > Manage > Amazon S3 .
However, after selecting Datasets > New dataset > S3 and uploading a .json manifest file, I get this error: We can’t connect to the S3 file. Make sure any S3 file you specify exists. The S3 bucket for this file also must be associated with the AWS account used to create this QuickSight account.
How can I overcome this issue to get data from cur_B and cur_C that reside into two different accounts?
Thanks!
Hello @GaBon, my recommendation would be to share the data stored in the Account B and Account C S3 buckets, with a bucket in Account A that you could then retrieve in QuickSight. Here is some documentation on how to manage that data transfer:
This documentation even includes the permissions you will need to provide to the source account and destination account to share the data. Let me know if you have any further questions!
Hello @GaBon, since we have not heard back from you with any further questions, I will mark my previous response as the solution. Let me know if you still need assistance with this issue and I can guide you further. Thank you!
However, when importing the datasets I get this error I am currently struggling with:
[Simba]AthenaJDBC An error has been thrown from the AWS Athena client. com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: …; S3 Extended Request ID: …; Proxy: null), S3 Extended Request ID: … (Bucket: cur-B, Key: cur-B4/year=2023/month=11/cur-b00001.snappy.parquet) [Execution ID: …]
I suppose we’re still missing something related to the permissions… would you have any suggestions?