Understanding Quicksight "Over Capacity" Usage

Q&A
, ,
1

Hello everyone!

I have some questions about “over capacity” SPICE usage in QuickSight.

According to my QuickSight SPICE panel, I have a total purchased capacity of 440GB with the “Auto-purchase” feature disabled. However, in the “SPICE usage” section, I’m seeing 416GB of “over capacity” usage - meaning I’m using approximately 856GB total.

quicksight-spice
quicksight-spice2285×496 35.5 KB

My main concern: Based on my bill, it appears this “over capacity” usage is being charged. I specifically disabled Auto-purchase to avoid incurring additional charges without explicit approval. However, if over capacity usage is still charged regardless, then disabling Auto-purchase doesn’t actually prevent the issue I was trying to avoid.

I’ve already reviewed the QuickSight pricing documentation and the SPICE capacity management documentation, but couldn’t find any information explaining this “over capacity” usage and how it’s billed.

Can someone help me to understand how “over capacity” usage works and how it’s charged?
How can I actually prevent over capacity usage from occurring if Auto-purchase is already disabled?

Any help would be much appreciated!

2

Hi @willian,

Welcome to the Quick Community! This is definitely interesting behavior that is being displayed. Since this is a public user forum, we are not able to provide account-related assistance. However, I would definitely recommend reaching out to AWS Support by creating a support ticket, as they may be able to help provide a solution. I have seen a post related to a similar issue in the past, and it could potentially be an internal issue within SPICE capacity that is making it raise “Over Capacity” despite it not being so.

Hope this helps!

1 Like
3

Hi @willian

I experienced this issue once where we went over capacity but QuickSight continued to work; but then one fine day started giving errors during dataset refresh.

I would assume you have gone over capacity recently and then cycle that QuickSight goes through (may be related to billing) has not yet kicked in; because when it does you will not be able to refresh your datasets without increasing the capacity.

Check to see if there was any newly created dataset that may have suddenly spiked your usage and determine how to deal with it.

Regards,
Giri

2 Likes
4

Thanks for your reply! :slightly_smiling_face:

I had the same feeling that something wasn’t right. I’ve already opened a support ticket and am awaiting their response.

If I get anything interesting, I’ll let you know here.

1 Like
5

That’s interesting, thanks!

It’s been more than a month since this started and the over-capacity is still there. I’ll investigate this further and update here if I find anything.

1 Like