Unable to fetch account usage data

[kevs3021]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Windows 11

Kiro Version

0.11.107

Bug Description

My account was automatically locked/flagged by the system despite following standard operating procedures. There have been no violations of the Terms of Service or community guidelines. The lockout occurred during normal usage and standard contributions.

Error Message Received: "Unable to fetch account usage data: Your User ID (24888448-e0d1-70e9-3fcd-579439b22e40) temporarily is suspended. We've locked your account as a security precaution. To restore access, please contact our support team to verify your identity: https://app.kiro.dev/account/usage?support_form"

Steps to Reproduce

1. Log in to the account using valid credentials.
2. Perform standard actions on chat
3. Trigger Point: In this instance, the lockout occurred specifically after I run the first task after design. Kiro already made the spec requirements, design, and task files beforehand.
4. Result: Access is immediately revoked, and the error message on the Kiro notification pops up.

Expected Behavior

The account should remain active and accessible during routine operations.

Conversation ID

No response

Additional Context

[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)
• #5678: Sync Fetch Account Usage Data Between Multiple Kiro Windows (85% similar)
• #5475: Login issues when switching between IdC and Social sign ins (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 authentication/authorization issues, though one mentions suspension while the other mentions authorization failure

[kevs3021]

👎 Not similar to any issues given.

[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.

[renergydev]

Just file a ticket in AWS. This is standard problem almost everyone is running into. Definitely did around March 1st week. It will take from 1 day - 7 days to get resolved.