Account Suspension Error: "Unable to fetch account usage data"

[sefyp2025]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Window 11

Kiro Version

0.10.32

Bug Description

Upon attempting to access account usage data or cloud-integrated features, the application returns a security suspension error. The UI displays: "Unable to fetch account usage data: Your User ID (256274921830) temporarily is suspended." It appears Kiro is unable to handshake with AWS due to an account-level security lock.

Expected Behavior

The application should display usage metrics or, if the account is flagged, provide a clear path to re-authenticate or a graceful "Logged Out/Suspended" state rather than a raw data-fetch error.

Conversation ID

No response

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #6051: Unable to fetch account usage data : user is not authorized to make a call on initial Chat Load (95% similar)
• #5810: Streamline re-authentication flow when login tokens expire for Enterprise IAM Identity Center customers. (85% similar)
• #5678: Sync Fetch Account Usage Data Between Multiple Kiro Windows (85% similar)
• #4681: can't login kiro (85% similar)
• #4550: kiro-cli无法完成您的请求，请稍后重试，导致我无法登录使用kiro cli (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both report identical 'Unable to fetch account usage data' error with user authorization issues when accessing account/usage features

[sefyp2025]

"While this issue shares a similar error string with #6051 and #5810, I believe it is unique and should remain open for the following reasons:

Specific Error State: Unlike #6051 (generic authorization) or #5810 (token expiration), my error explicitly cites a temporary suspension for User ID 256274921830. This suggests an account-level security flag rather than a standard handshake or sync failure.

AWS Handshake Failure: The logs indicate a specific failure to communicate with the AWS backend, which isn't addressed in the multi-window sync issues mentioned in #5678.

UI/UX Improvement: The core of this bug report is that the application does not provide a graceful fallback or re-authentication path when a suspension occurs, leading to a raw data-fetch error.

Please keep this open so the team can investigate why the UI is failing to handle this specific security state properly."

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[AnilMaktala]

Hey @sefyp2025, thanks for reaching out. Account suspensions are handled by the AWS account team and aren't something we can resolve through this GitHub repo. Please contact AWS Customer Support directly to get your account status reviewed and restored:

They'll be able to look into the suspension on your account and help you get unblocked.

[iampopg]

im having the same issue here, Im a paying user, i have verify my AWS account before, which makes me believe that the suspension is from Kiro, i have email you guys through the suppose page provided, please FREE MY DAMN ACCOUNT....... THIS IS TOTALLY A BUG/GLITCH...