Unable to use Kiro Chat

[Capn-Black]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Windows 11 Enterprise

Kiro Version

0.10.32

Bug Description

I attempt to use the chat feature to create code and it starts with 'working on it' then ends with "Access denied. Please check your authentication" but I'm authenticated against the same environment as others on the team.

Steps to Reproduce

1. Open Kiro authenticate in "AWS IAM Identity Center" with organization link in us-west-2 region
2. Open/Create a file to write code. -language selected is python
3. Select "Generate code" and enter desired result - create python script to add two numbers
4. CodeWhispererStreaming: AccessDenied response
5. Also open Kiro Chat on side-bar - enter simple "Hello" and receive response "Access denied. Please check your authentication."

Expected Behavior

I would expect the chat/AI features to execute and provide a response

Conversation ID

6ca8508d-2e48-48e3-9166-5983ad4f7fef
6ca8508d-2e48-48e3-9166-5983ad4f7fef

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 (85% similar)
• #4865: Can't Chat With Kiro - the chat session area goes grey every 5 mins (85% similar)
• #4681: can't login kiro (85% similar)
• #4130: "Authentication fails on Linux - token exchange not completing" (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/authorization errors when trying to use chat features, with similar 'user is not authorized' and 'Access denied' messages despite being properly authenticated

[github-actions]

This issue has been automatically closed as it appears to be a duplicate of #6051.

If you believe this is incorrect, please comment on this issue and a maintainer will review it.