- Newest
- Most votes
- Most comments
I understand you're experiencing a "Failed to create Kiro subscription" error when trying to set up Amazon Q Developer Pro subscriptions, despite having verified your configuration and having active startup program credits.
Based on the symptoms you're describing—particularly the failure occurring at the final assignment step when adding subscribers—this does appear to be a backend provisioning issue that requires AWS Support intervention. The error pattern you're seeing, where the subscription creation fails consistently despite correct configuration, typically indicates an issue that cannot be resolved through console actions alone.
For this type of issue, I recommend taking the following steps:
Immediate Action: Contact AWS Support through the AWS Support Center (https://console.aws.amazon.com/support/) and create a new support case. When creating your case:
- Select "Account and billing support" as the case type
- Choose "Amazon Q" as the service
- Provide the technical details you've already gathered (though please avoid including your account ID or other sensitive information in any public correspondence)
- Request that the case be routed to the team that handles Amazon Q Developer provisioning issues
What to Include in Your Support Case:
- Description of the error message you're receiving
- Confirmation that you're using an Organization instance of IAM Identity Center
- Details about your startup program credits
- The specific step where the failure occurs (user assignment)
- Any error codes or additional details from browser developer tools if available
Regarding Your Startup Credits: Your startup program credits should be applicable to Amazon Q Developer Pro subscriptions. However, the subscription creation failure needs to be resolved first before the credits can be utilized. The support team will be able to verify that your credits are properly configured and investigate any backend provisioning issues.
Since this appears to be a service-side issue rather than a configuration problem on your end, AWS Support will need to engage with the internal teams responsible for Amazon Q Developer provisioning to resolve this for you.
Relevant content
- AWS OFFICIALUpdated 2 years ago
