Unable to save and publish dataset

Question & Answer
,
1

Hello I have to maintain a dashboard.

But the dataset has to be updated manually. I did not build the dashboard but I do have to maintain it. In trying to update the manual file I am getting below message: Error details
region:
us-east-1
timestamp:
1753352000509
requestId:
1a587e46-76ac-4931-b93b-fb7561f8443e
sourceErrorCode:
ACL_SECURITY_EXCEPTION
sourceErrorMessage:
AccountId: 764946308314 UserId: arn:aws:ds:us-east-1:764946308314:user/d-9067271e9d/S-1-5-21-1407069837-2091007605-538272213-49248537 does not have sn:Read permission for object with id 39a37819-d4c6-46e6-bd89-4f2fc443ee59|10.

2

Hello @soodnita Hope this message finds you well!! Welcome to community :smiley:

The ACL_SECURITY_EXCEPTION error indicates that the user or the associated AWS account lacks the necessary permissions to access or update the specified object in QS. This typically arises due to improper permission configurations in IAM, resource policies (such as an S3 bucket), or QS specific permissions. To resolve this, ensure the user has the appropriate IAM permissions, such as quicksight:UpdateDataSetPermissions, and service-specific permissions, like s3:GetObject for S3 buckets. Additionally, review the access policies of the associated resource (e.g., the S3 bucket policy or the dataset permissions in QS) to confirm that both QS and the user have the required read/write access. If needed, consult the account administrator or the dashboard creator to adjust the permissions accordingly.

Please, tell me if it helps you!

3

Hi @soodnita,
It’s been awhile since we last heard from you, did you have any additional questions regarding your initial post?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you

4

I was not able to solve this issue. The owner has granted me all permissions and I still cannot update the dataset that needs manual update. The system is stating error that I do not have permissions.

5

Hi @soodnita,
It sounds more like you’re missing a permission in the IAM console as opposed to QuickSight itself. If the proper permissions have been granted to your account through IAM, then there may be a bug and I would suggest creating a support ticket for more in depth assistance.