AWS Backend: Fixing Kiro Subscription Creation Failures for 2 Users

Select Language:

Here’s a simple, step-by-step guide to help you troubleshoot issues with creating subscriptions for Amazon Q users, especially when everything appears to be set up correctly but the problem persists.

First, it’s important to verify that your service quotas are in order. You can do this by running a couple of commands:

For Amazon Q:
aws service-quotas list-service-quotas --service-code amazonq --region us-east-1
For user subscriptions:
aws service-quotas list-service-quotas --service-code user-subscriptions --region us-east-1

If these commands don’t return quota information (which is expected for newer services), it’s usually not an issue, but it’s worth confirming.

Next, check the status of your IAM Identity Center users. Make sure both users are enabled and properly configured. Use your dashboard or admin commands to verify that the user status shows as “ENABLED”. Confirm their email addresses and creation/update timestamps to ensure they are active and correctly set up.

Then, verify that your AWS Organizations are correctly connected. Run this command:
aws organizations list-aws-service-access-for-organization
You should see service principals like sso.amazonaws.com, user-subscriptions.amazonaws.com, and iam.amazonaws.com listed and enabled. These are necessary for the services to communicate properly.

Check your regional settings too. Your IAM Identity Center instance should be set in the correct region, such as eu-central-1, and your Amazon Q console should be in us-east-1. Confirm that cross-region configurations are properly in place and working for your Amazon Q applications.

After all these checks, review your configuration summary:

IAM Identity Center is correctly set up.
AWS Organizations features are fully active.
All necessary services are enabled.
User assignments are complete.
User statuses and permissions are verified.
Regional settings are properly aligned.

Once everything is verified and appears correct, but you still encounter an error like “Failed to create Kiro subscriptions for 2 users,” it indicates an issue beyond your configuration. It’s likely a backend problem with Amazon Q’s subscription provisioning system.

The best step now is to contact AWS Support directly. They can investigate this backend issue, which isn’t something you can fix from your side.

In summary, after running these checks, if everything looks good but the problem persists, escalate the case to AWS Support for a deeper investigation into the backend provisioning system.