Failed to create Kiro subscription - backend provisioning issue (Support case ignored for 54+ hours)

I am unable to create Kiro subscriptions for any users in my AWS Organization. This issue has persisted for over 72 hours since organization creation, and all configuration requirements have been verified.

Error Message: When attempting to assign a Kiro subscription to a user, the following error appears: "Das Kiro-Abonnement für 1 Benutzer konnte nicht erstellt werden. Beim Versuch, Kiro-Abonnements zu erstellen, ist ein Fehler aufgetreten."

(Translated: "Failed to create Kiro subscription for 1 user. An error occurred while trying to create Kiro subscriptions.")

Environment Setup:

• Region: eu-central-1 (Frankfurt)
• IAM Identity Center: Organization instance (not standalone)
• Kiro profile: Created in eu-central-1 (same region as IAM Identity Center)
• AWS Organizations: Enabled with all features
• Time elapsed: 72+ hours since organization and IAM Identity Center setup

Configuration Verified (All Requirements Met): ✅ IAM Identity Center enabled as organization instance ✅ Kiro profile successfully created in eu-central-1 ✅ Identity-enhanced console sessions: ENABLED in IAM Identity Center settings ✅ Multiple users created and tested - same error for all users ✅ All users have active status with accepted invitations and passwords set ✅ Attempting subscription assignment under IAM administrator user (not root) ✅ IAM admin user has AdministratorAccess policy ✅ All components in same region (eu-central-1) ✅ Waited 72+ hours for backend service principal provisioning

Troubleshooting Completed:

1. Created multiple new users with different configurations - same error
2. Verified identity-enhanced console sessions are enabled
3. Confirmed subscription assignment performed under IAM admin, not root
4. Verified AWS Organizations service access properly configured
5. Checked all components are in supported region
6. Waited well beyond the documented 24-hour provisioning window

Analysis: Based on this similar case: https://repost.aws/questions/QUIGL5xRFgScmXwScHwdGIcw

This error pattern matches the known backend provisioning bug where q.amazonaws.com service principal is not properly registered for the organization, or there is a backend mapping issue between IAM Identity Center and the Kiro subscription service.

As confirmed in that thread: "This is a known backend bug where the account gets stuck in a faulty provisioning state. It will not self-heal and requires manual intervention from AWS backend team."

AWS Support Case Status: I submitted an AWS Support case 54+ hours ago (Case ID: 17835095249036​2, submitted 2026-07-08 11:18:44). The case status remains "Nicht zugewiesen" (Not assigned) with NO response from AWS Support for over 2 days.

Request: This appears to be the known backend provisioning bug that requires manual AWS engineering intervention. Could someone from the AWS team please:

1. Investigate the backend provisioning status for Kiro subscription service in my organization
2. Verify that q.amazonaws.com service principal is properly registered
3. Check the mapping between my IAM Identity Center instance and Kiro subscription backend
4. Resolve the backend issues preventing subscription creation
5. Provide update on my ignored Support case

I have verified all user-configurable settings are correct. This is a systemic backend problem, not a configuration error, and is blocking our ability to use the paid Kiro service we are trying to purchase.

Thank you for your urgent assistance.