Kiro Windows App - No profiles available | profileArn is required | Subscription stuck in Pending

[MWPROD11]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win32

Kiro Version

0.11.132

Bug Description

Critical: Kiro Windows App & CLI - No profiles available | profileArn is required

I am experiencing a complete service blockage. Although the login process completes successfully ("Logged in"), the application is non-functional.

EXTENSIVE TROUBLESHOOTING PERFORMED:

• Tested on TWO (2) different computers with the same result.
• Performed multiple full reinstalls of the Kiro Desktop App and CLI.
• Cleared all local metadata, including the .kiro folder and .aws/sso cache.

Issues Observed:

• Model Selection: The model dropdown is empty or unresponsive. I cannot select default models like Claude 3.5 Sonnet or Sonnet 4.6.
• Chat Failure: The AI does not respond, showing the error: "An unknown error occurred: profileArn is required but no profiles are available."
• Profile Status: The profile icon indicates that the "profileArn could not be resolved."

AWS Account ID: 377114445398
Region: eu-central-1

Steps to Reproduce

1. Open Kiro Windows Desktop Application.
2. Log in using the Pro/Identity Center option with my AWS Start URL.
3. Observe the "Logged in" confirmation message.
4. Try to open a chat and select a model (Claude 3.5/4.6 Sonnet).
5. Observe the empty model list and the "profileArn is required" error toast.

Expected Behavior

The application should correctly resolve the profileArn after a successful login, allowing me to select available models and start a chat session without errors, especially since the AWS account is verified and active.

Conversation ID

No response

Additional Context

The issue has been verified on two separate Windows machines to rule out local hardware or OS corruption. I have already contacted AWS Billing Support (Agent: Brandon), who confirmed the account is in good standing and not suspended.

Despite the account being active, the Kiro Subscription panel in the AWS Console shows the user as "Pending". This confirms the bug is a backend provisioning failure that prevents the profileArn from being generated, regardless of the machine used.

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #7333: Invalid model. Please select a different model to continue. (85% similar)
• #7137: Total Lockout: Debugging the "Unauthorized Client" Mystery in Kiro CLI & AWS SSO (85% similar)
• #7089: Kiro subscription assignment fails on Organizations management account and routes to standalone CreateAssignment path (85% similar)
• #6395: kiro stopped working or responding (85% similar)
• #6167: Domain verification stuck on "Pending" indefinitely (85% similar)
• #5810: Streamline re-authentication flow when login tokens expire for Enterprise IAM Identity Center customers. (85% similar)
• #5475: Login issues when switching between IdC and Social sign ins (85% similar)
• #7068: Kiro subscription creation fails for all AWS Organizations accounts - wrong subscriptionType Q_DEVELOPER_STANDALONE_PRO used (82% 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 issues report model selection problems on Windows with similar symptoms - empty/unresponsive model dropdown and inability to select models like Claude 3.5 Sonnet, though the new issue has additional profileArn errors

[MWPROD11]

This is NOT a duplicate. While symptoms are similar, the core error is 'profileArn is required but could not be resolved' on a fresh AWS account after a full cleanup. The bot is misidentifying the root cause.

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

[MWPROD11]

AWS Billing Support (Case 177686997600325) has officially confirmed that my account has no billing issues, but they are unable to help with the profileArn resolution error.

They pointed me here because this is a service-side technical failure. The Profile ARN exists in my console but the app/CLI cannot resolve it. I'm essentially paying for a subscription I can't use due to a backend provisioning loop.

[MWPROD11]

hey again, i managed to get the developer tools console logs and i found the smoking gun. the extension host is throwing a hard error at resolveProfileArn inside kiro.kiro-agent/dist/extension.js.

exact error:
Error: profileArn is required but could not be resolved at resolveProfileArn (extension.js:504883:13)

immediately followed by:
dt4: Validation error

it's clear the agent is failing to resolve the professional profile arn from the sso token, causing all backend calls to fail validation. since i've already recreated the sso instance, this looks like a bug in how the agent handles sso session mapping for certain account types. can any dev look at that specific line in the extension?"