kiro账号被封禁

[yangyan98]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

mscOS15.3

Kiro Version

0.11.63

Bug Description

Unable to fetch account usage data: Your User ID(74a88498-f061-7033-c1b1-015c6b3f9d2c)temporarily is suspended. We've locked your accountas a security precaution.

Steps to Reproduce

无法获取账户使用情况数据：您的用户 ID (74a88498-f061-7033-c1b1-015c6b3f9d2c) 已被暂时停用。出于安全考虑，我们已锁定您的账户。要恢复访问权限，请联系我们的支持团队验证您的身份：https://support.aws.amazon.com/#/contacts/kiro

Expected Behavior

可以正常使用

Conversation ID

74a88498-f061-7033-c1b1-015c6b3f9d2c

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 (85% similar)
• #5678: Sync Fetch Account Usage Data Between Multiple Kiro Windows (85% similar)
• #4681: can't login kiro (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 'Unable to fetch account usage data' errors related to account authorization/suspension issues, though one mentions suspension while the other mentions authorization

[yangyan98]

这严重影响了我使用该设备，请立即修复。

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

[kongxiangLlong]

蹲

[AnilMaktala]

Thanks for raising this. Account suspensions and related appeals are handled directly by the AWS support team, as they require account-level verification that we're unable to process through GitHub issues.

What to do now:

1. Contact support directly at https://support.aws.amazon.com/#/contacts/kiro — include your User ID from the error message
2. If you've already contacted support and haven't received a response, please allow up to 24–48 hours for the team to process the backlog