- 최신
- 최다 투표
- 가장 많은 댓글
Hello, There are several possible reasons for the failed refreshes.
-
The format of the data going into the S3 bucket has changed. I understand that you have verified the format, however please recheck it with the previous format.
-
The application generating the data is having a problem and is uploading corrupted data.
-
Something is causing the manifest file to change after the initial dataset creation but before the refresh.
-
Without access to the bucket policy itself, it is difficult to confirm whether the permissions are indeed correct.
The process that occurs internally to handle a refresh also depends on the way QuickSight connects to the data store. Unfortunately, we will need more information to narrow down the issue.
For more information, please see the documentation on refreshing data in QuickSight: https://docs.aws.amazon.com/quicksight/latest/user/refreshing-data.html
If you are using a SPICE dataset, this documentation may help you ensure that the refresh is set up properly: https://docs.aws.amazon.com/quicksight/latest/user/refreshing-imported-data.html
Is the data in S3 encrypted with a KMS key? I've found I've received similar errors when having encrypted data, and Quicksight didn't have access to the key (either identity based or resource-based denials)
Thanks for the suggestion but I never set it up to be encrypted unless something changed completely on its own. I haven't changed anything in AWS configuration and these errors suddenly began out of the blue. Very strange. I guess I'm just going to have to cave and pay for AWS support.