- Newest
- Most votes
- Most comments
I guess the "Account does not meet requirements" error and the CLI failure are caused by three specific configuration gaps, not a lack of permissions:
1. Identity Center Instance Type: Amazon Q Developer Pro requires an Organization Instance of IAM Identity Center. If you are using an "Account Instance" (limited to a single account), the subscription will fail.
2. Outdated AWS CLI: The error invalid choice 'q' means your local AWS CLI version predates the launch of Amazon Q. You must update to the latest AWS CLI v2 to recognize the aws q command.
3. Incorrect Service Principal: The service principal q.amazonaws.com is often not recognized for manual organization enablement. You should use codewhisperer.amazonaws.com, as Amazon Q Developer still operates under this underlying service principal for many organizational features.
How to Fix:
- Update CLI: Run the latest installer for AWS CLI v2.
- Upgrade Identity Center: Ensure your IAM Identity Center is enabled for the entire Organization (check "Settings" in the Identity Center console).
- Enable Service Access: Use the correct principal:
aws organizations enable-aws-service-access --service-principal codewhisperer.amazonaws.com - Console Setup: Always use the Amazon Q Developer console (not the standard Amazon Q Business console) to trigger the initial handshake.
Based on the error you're encountering, there are several potential issues to address:
Verify Your Permissions: Ensure you have the minimum permissions required to subscribe users to Amazon Q Developer Pro. You need specific IAM permissions to access and use the Amazon Q Developer console. After obtaining the necessary permissions, reload the console page to access Amazon Q.
Confirm You're in the Correct Console: Make sure you're accessing the Amazon Q Developer console specifically, not the Amazon Q console. These are separate services with different interfaces.
Check Regional Support: Verify that you're operating in a supported AWS Region for Amazon Q Developer. While you mentioned trying us-east-1 and us-west-2, confirm these regions support the Q Developer console and Q Developer profile functionality.
Follow the Correct Workflow: Since you're working with an AWS Organization Management account, ensure you're following the appropriate workflow for subscribing users in a management account. The process differs depending on whether you're using a standalone account, management account, or member account.
Identity Center Configuration: For IAM Identity Center workforce users, verify that identity-enhanced console sessions are enabled. This feature is only available with organization instances of IAM Identity Center. Note that account instances of IAM Identity Center don't support console access for Amazon Q Developer Pro subscriptions.
The "account does not meet requirements" error typically indicates a configuration issue with permissions, Identity Center setup, or the subscription workflow rather than an account-level restriction or allowlist requirement.
Sources
Users unable to use their subscription on AWS websites - Amazon Q Developer
Unable to subscribe users - Amazon Q Developer
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
