- Newest
- Most votes
- Most comments
There could be a delay for the quota to become effective after you add the first dataset. How long has it been since you created QuickSight account in us-east-1? Let it retry itself. If you continue to experience the issue, please open a support case as none of us here would be able to look into your account. Contacting support is the best way to resolve such issue.
It has been more than 1 day and the it is still showing ACCOUNT_CAPACITY_LIMIT_EXCEEDED when trying to import / update the dataset. I don't have a technical support plan as it is for testing purpose only, and the AWS support asked me to post a question here.
This is quoted from support team reply on 2024-05-08.
The team confirmed that they have identified an issue of QuickSight console shows incorrect SPICE capaicty for some customers. The actual SPICE capacity used for billing and deciding whether you can import more data to SPICE is correct. We are in the process of rolling out the fix to all QuickSight regions. You are recommended to enable SPICE capacity auto-purchase option to unblock if you are impacted by this issue.
And I still yet to wait for the corrected capacity.
Relevant content
- asked 9 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago