AWS Guide: Fixing Kiro Subscription Failures for IAM Identity Center User in US-East-1

Select Language:

If you’re having trouble assigning a Kiro / Amazon Q Developer Pro subscription in the us-east-1 region, here’s a simple step-by-step solution that can help you fix the problem.

First, ensure you have admin access to your AWS account and that your IAM Identity Center user is set up and visible within your account. Confirm that you have selected the correct subscription plan, such as Kiro Pro, and that your payment method is active and valid. Also, verify that your account has available AWS promotional credits, which can sometimes affect subscription assignments.

Next, check the region you’re working in. Make sure you’re in the correct AWS region, specifically us-east-1, as the issue seems to be region-specific.

When you try to assign the subscription to the IAM Identity Center user, you might see an error message like: “Failed to create Kiro subscription for 1 user. An error occurred while trying to create Kiro subscriptions.” This indicates that something is preventing the system from completing the assignment.

If everything looks correct—you’re in the right region, the user is visible and selectable, and your console is correct—but the problem persists at the final assignment step, then here are some common causes to consider:

– Your account may have restrictions or limitations that are causing the issue.
– There could be a temporary backend provisioning problem on Amazon’s side.
– The IAM Identity Center instance type might not be compatible or properly configured for the subscription.

To troubleshoot, try the following:

1. Make sure all account settings are up to date, including promotional credits and payment details.
2. Refresh your IAM Identity Center setup and ensure the user exists and is correctly configured.
3. Attempt the assignment again after some time, as backend issues sometimes resolve quickly.
4. Contact AWS support if the issue continues, providing details of the error message and your environment setup.

In many cases, ensuring the correct region, confirming account and user settings, and waiting briefly can resolve these assignment failures. If problems still occur, reaching out to AWS support with detailed information will help get a targeted solution.