Failed to create Kiro subscription for IAM Identity Center user in us-east-1

Based on the error you're experiencing with Amazon Q Developer Pro subscription assignment, there are several potential causes and troubleshooting steps to consider:

Common causes for subscription assignment failures:

1. IAM Identity Center Configuration Issues: Ensure your IAM Identity Center instance is properly configured and the user account is in an active state. Verify that the user has completed any required setup steps in IAM Identity Center.

2. Service Availability: While you mentioned this is reproducible in us-east-1, Amazon Q Developer may have specific regional requirements or temporary service issues. Consider checking AWS Service Health Dashboard for any ongoing issues.

3. Account Limits or Quotas: Even with admin access and available credits, there may be service-specific quotas that need to be increased for Amazon Q Developer Pro subscriptions.

4. Billing and Payment Verification: Although you have a payment method and promotional credits, ensure that:

• The payment method is fully validated
• There are no holds or restrictions on the account
• The promotional credits are applicable to Amazon Q Developer Pro

5. IAM Identity Center Instance Type: If you're using an external identity provider or have a complex IAM Identity Center setup, there may be integration issues affecting the subscription provisioning.

Recommended troubleshooting steps:

• Try assigning the subscription to a different IAM Identity Center user to isolate whether it's user-specific
• Verify that your IAM Identity Center instance has the necessary permissions and trust relationships
• Check CloudTrail logs for more detailed error information about the failed subscription creation
• Contact AWS Support with the specific error details, as this may be a backend provisioning issue that requires investigation by the service team

Since this is consistently reproducible and occurs at the final assignment step after all validations pass, this suggests a backend provisioning issue that would benefit from AWS Support engagement.

While the generic troubleshooting steps are a good start (former answer - re:Post Agent), this specific error in us-east-1 can stems from one of the following two technical blockers:

• Identity Center Instance Type: Amazon Q Developer Pro requires an Organization Instance of IAM Identity Center. If your instance is set to "Account Instance" (standalone), the subscription assignment will consistently fail at the final step. Check this under IAM Identity Center > Settings.
• Organization Service Access: Ensure that Service Access is enabled for Amazon Q within your AWS Organization. You can verify this in the Management Account under Organizations > Services. Look for Amazon Q (or its legacy name CodeWhisperer) and ensure the status is "Access enabled".
• Service-Linked Role (SLR): Verify that the AWSServiceRoleForAmazonQDeveloper role has been correctly provisioned in your account. Without this role, the backend cannot complete the subscription handshake.

Hello, this is still unassigned.

I have now verified that my IAM Identity Center setup is a standalone/account instance, not an organization instance, and AWS Organizations is not enabled on this account.

The IAM Identity Center user is visible and selectable, the region is us-east-1, and AWSServiceRoleForAmazonQDeveloper exists in IAM. However, Amazon Q Developer Pro / Kiro subscription assignment still fails at the final step and no subscription is created.

Please confirm whether:

1. standalone/account-instance IAM Identity Center is unsupported for this subscription flow, or
2. this is a backend provisioning issue on the Amazon Q / Kiro side.

This issue needs human review.