Why was my account suspended?

[datasci-cmyk]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win11

Kiro Version

Version: 0.11.63

Bug Description

Can someone explained to me why my account was suspended? What is going on?

Unable to fetch account usage data: Your User ID (043834a8-5021-70f7-5d47-6773ecb94c9c) 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://support.aws.amazon.com/#/contacts/kiro

Steps to Reproduce

A prompt appears as soon as you log in saying that my account is suspend.

Expected Behavior

unlock my account

Conversation ID

043834a8-5021-70f7-5d47-6773ecb94c9c

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #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 authentication/login issues with access denied errors, though one mentions suspension while the other shows AccessDeniedException

[datasci-cmyk]

This is not a duplicate

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

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