Skip to content

QuickSight charges still appearing after account termination — will they stop next month?

-1

I terminated my QuickSight account on June 2, 2026, but I'm still seeing charges in my billing dashboard AND Cost Explorer is forecasting a massive $310.25/month spend going forward. I want to confirm whether these charges and the forecast will stop, or if there's something else I need to do.

Current QuickSight charges (June, post-cancellation):

  • Amazon Q in QuickSight (USE1-Amazon-Q-QS-Fee): USD 10.42 — billed as 0.042 Month at $250/month
  • QuickSight Author Pro Enterprise (USE1-Author-Pro-Enterprise-Month): USD 1.67 — billed as 0.042 User at $40/user/month
  • QuickSight Index (USE1-QuickSuite-Index): USD 0.00 after bundled discount
  • Total QuickSight this month: USD 12.16**
  • Previous month (May 2026):** USD 81.72 for QuickSight (0.606 month usage)

Cost Explorer Forecast concern:** After cancelling, my Cost Explorer is showing:

  • Average historical cost per month: $15.35
  • Average forecasted cost per month: $310.25
  • Total (historical + forecasted): $714.41
  • The chart shows a sharp spike projected for June and July 2026

I believe this forecast is being extrapolated from the May spike caused by QuickSight, and does not account for the fact that I have already terminated the subscription. But I want to confirm from the community:

My questions:

  1. Are QuickSight charges flat-rate monthly, or truly prorated by usage days? The 0.042 month figure suggests prorated — can anyone confirm?
  2. Since I terminated on June 2, will I be charged for the full month of June or just the ~1–2 days I used?
  3. Is there anything else I need to cancel (Amazon Q subscription, user licenses, SPICE capacity) to ensure $0 QuickSight charges from July onward?
  4. How can I validate the subscription is fully terminated and no further charges will accrue?
  5. Will the Cost Explorer forecast correct itself over the coming days as it sees no new QuickSight usage? Or does the $310/month forecast indicate there are still active resources I've missed?

Any confirmation from the community or AWS team would be greatly appreciated. Thank you!

1 Answer
0

Based on AWS billing practices, when you close or terminate a service, usage and billing stops accruing at that point. You will be billed for any usage that has accrued up until the time you terminated the service, and your final charges will be billed at the beginning of the following month.

Regarding your specific situation:

1. Prorated Charges: The 0.042 month figure you're seeing strongly suggests that QuickSight charges are prorated based on actual usage days. This means you're being charged proportionally for the time the service was active in June before termination.

2. June Billing: Since you terminated on June 2, you should only be charged for the approximately 1-2 days of usage in June, which appears to be what's happening with your current charges of $12.16.

3. Ensuring Zero Future Charges: To confirm no future charges will accrue, verify in the QuickSight console that:

  • All user subscriptions have been cancelled
  • The Amazon Q enablement has been disabled
  • Any SPICE capacity has been released
  • The QuickSight account itself has been unsubscribed/deleted

4. Validating Termination: Check your QuickSight console to ensure the account shows as terminated or unsubscribed. You can also review your AWS Cost Explorer and billing dashboard over the next few days to confirm no new QuickSight usage is being recorded.

5. Cost Explorer Forecast: Cost Explorer forecasts are based on historical usage patterns and typically take time to adjust after service termination. The $310/month projection is likely extrapolating from your May usage spike and hasn't yet recognized the termination. As the system observes zero usage in the coming days and weeks, the forecast should automatically correct itself to reflect the actual state of your account.

If charges continue to appear beyond the prorated June amount, I recommend checking the AWS Support Center to review your account configuration and ensure all QuickSight components have been properly terminated.
Sources
AWS Premium Support FAQs

answered 11 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.