# Getting started with Amazon Q Developer
This section provides comprehensive guidance on getting started with Amazon Q Developer. It covers the different tiers of service (Free and Pro), explains the various sign-in methods available, and walks you through the setup process for personal accounts (Builder IDs) and workforce identities in AWS IAM Identity Center. Whether you're an individual developer or an administrator setting up Amazon Q Developer for your organization, this section will help you choose the right approach for getting started quickly with Amazon Q.
**Topics**
+ [Tiers of service for Q Developer – Free and Pro](q-tiers.md)
+ [Getting started with a personal account (Builder ID)](getting-started-builderid.md)
+ [Getting started with IAM Identity Center](getting-started-idc.md)
+ [Amazon Q Developer Pro subscriptions](q-admin-setup-subscribe-general.md)
+ [Upgrade to Kiro](upgrade-to-kiro.md)
# Tiers of service for Q Developer – Free and Pro
With Amazon Q Developer, you either use Amazon Q Developer at the Free or Pro tier. Review the following information to understand what's offered at each tier.
## Free tier
Amazon Q Developer offers a perpetual Free tier with monthly limits.
For more information about what's available at the Free tier, see the [Amazon Q Developer pricing page](https://aws.amazon.com/q/developer/pricing).
The Free tier is available to users with [personal accounts](getting-started-builderid.md) (Builder IDs), users with identities in [IAM Identity Center](getting-started-idc.md), and users with IAM credentials. Consult the following table to understand the availability of Amazon Q in various interfaces at the Free tier depending on your sign in method.
| | Sign in method (Free tier) | Interface | Personal account (Builder ID) | IAM Identity Center | IAM credentials |
| --- | --- | --- | --- | --- | --- |
| [AWS Management Console, and AWS apps and websites](q-on-aws.md) | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes |
| [IDE](q-in-IDE.md) | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No |
| [Command line](command-line.md) | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No |
For more information about how content is used to improve the service at the Free tier, see [Amazon Q Developer service improvement](service-improvement.md).
## Pro tier
The *Pro tier*, also known as *Amazon Q Developer Pro*, is a paid version of the Amazon Q Developer service that offers higher usage limits than the Free tier. It also gives you access to advanced features.
For information about pricing for the Pro tier, see the [Amazon Q Developer pricing page](https://aws.amazon.com/q/developer/pricing).
The Pro tier is available to users with [personal accounts](getting-started-builderid.md) (Builder IDs), and users who have identities in [IAM Identity Center](getting-started-idc.md). Consult the following table to understand the availability of Amazon Q in various interfaces at the Pro tier depending on your sign in method.
| | Sign in method (Pro tier) | Interface | Personal account (Builder ID) | IAM Identity Center |
| --- | --- | --- | --- | --- |
| [AWS Management Console, and AWS apps and websites](q-on-aws.md) | ![\[No\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-no.png) No | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes |
| [IDE](q-in-IDE.md) | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes |
| [Command line](command-line.md) | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes | ![\[Yes\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/icon-yes.png) Yes |
# Getting started with a personal account (Builder ID)
If you want to use Amazon Q Developer for personal projects, and you don't need to administer other users, you'll want to get started with a personal account, also known as a Builder ID. A *Builder ID* is a special type of AWS account that gives you the ability to use Amazon Q in your Integrated Development Environment (IDE) and your terminal's command line. Unlike a regular AWS account, a Builder ID is meant to be used by you and you alone, does not allow access to the AWS Management Console, and cannot be assigned IAM roles or permissions.
You can set up a Builder ID for free to start. When you're ready, you can [upgrade to the Pro tier](upgrade-to-pro.md#upgrade-builder-id) by connecting your Builder ID to an AWS account to take advantage of higher usage limits.
For a list of features available at the Pro tier, see the [Amazon Q Developer pricing](https://aws.amazon.com/q/developer/pricing) page.
**Topics**
+ [Before you begin: Understand the limitations of personal accounts (Builder IDs)](#builder-id-limitations)
+ [Step 1: Sign up](#builder-id-signup)
+ [Step 2: Install Amazon Q](#builder-id-install)
+ [Step 3: (Optional) Upgrade to the Pro tier](#builder-id-upgrade-optional)
## Before you begin: Understand the limitations of personal accounts (Builder IDs)
Before you create a personal account (Builder ID) for use with Amazon Q, understand its limitations.
+ With a Builder ID at the Free tier, you will be subject to usage limits. For information about what these limits are, see the [pricing page](https://aws.amazon.com/q/developer/pricing/). If you need higher usage limits, subscribe your Builder ID to the Pro tier using the instructions that follow, or use IAM Identity Center following the guidance in [Getting started with IAM Identity Center](getting-started-idc.md).
+ With a Builder ID at the Pro tier, you'll get *higher usage limits*, but you won't get all Pro tier-only *features*. For a list of Pro tier features that are not available to you, see the footnote at the bottom of the [Amazon Q Developer pricing page](https://aws.amazon.com/q/developer/pricing/). If you need Pro tier features, use IAM Identity Center. For more information, see [Getting started with IAM Identity Center](getting-started-idc.md).
+ With a Builder ID at both the Free and Pro tiers, Amazon Q is only supported in the IDE and at the command line. It is not supported [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md). If you need to use Q in the AWS Management Console, and on AWS apps and websites, use IAM Identity Center. For more information, see [Getting started with IAM Identity Center](getting-started-idc.md).
## Step 1: Sign up
Sign up for a free personal account (Builder ID). You can sign up using your email address or an existing Google account. For more information, see [Create your AWS Builder ID](https://docs.aws.amazon.com/signin/latest/userguide/create-aws_builder_id.html) in the *AWS Sign-In User Guide*.
## Step 2: Install Amazon Q
Install Amazon Q in your Integrated Development Environment (IDE) or at the command line, and then authenticate using your personal account (Builder ID). For installation and authentication information, see:
+ [Installing the Amazon Q Developer extension or plugin in your IDE](q-in-IDE-setup.md)
+ [Install the Kiro CLI.](https://kiro.dev/docs/cli)
## Step 3: (Optional) Upgrade to the Pro tier
Upgrade to the Pro tier to take advantage of increased limits. See [Upgrading a personal account (Builder ID)](upgrade-to-pro.md#upgrade-builder-id).
# Getting started with IAM Identity Center
*IAM Identity Center* is a service that is used by administrators to manage the identities of end users. In the context of Amazon Q Developer, administrators use IAM Identity Center to manage the identities of those whom they plan on subscribing to Amazon Q Developer Pro.
Users who have identities in IAM Identity Center or in a directory or database that is connected to IAM Identity Center are called *IAM Identity Center workforce users* in this guide.
You should get started with IAM Identity Center if:
+ **You're an administrator** who wants to set up multiple users with Amazon Q Developer at the Pro tier. By using IAM Identity Center, your users get the full suite of Amazon Q Developer features, plus you get enterprise controls over the Amazon Q Developer subscriptions you administer. For example, you can cancel users' subscriptions, subscribe users in bulk, and track Amazon Q usage on a dashboard.
+ **You're an individual user**, and you can't use a personal account (Builder ID) because of [its limitations](getting-started-builderid.md#builder-id-limitations).
Use the following instructions to get started with IAM Identity Center.
**Topics**
+ [Step 1: Choose a deployment option](deployment-options.md)
+ [Step 2: Subscribe workforce users to Amazon Q Developer Pro](subscribe-users.md)
# Step 1: Choose a deployment option
Before you can subscribe users, you'll need to decide which AWS account or accounts you'll be working in. You'll need to make three key decisions:
+ **Decision 1: Where to enable IAM Identity Center** – For more information about IAM Identity Center, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.
+ **Decision 2: Where to create the Amazon Q Developer profile** – For more information about the profile, see [What is the Amazon Q Developer profile?](subscribe-understanding-profile.md).
+ **Decision 3: Where to subscribe workforce users** – For more information about subscriptions, see [Amazon Q Developer Pro subscriptions](q-admin-setup-subscribe-general.md).
Your specific combination of these three decisions constitutes your *deployment option*.
Deployment options are described in the following table. Pick an option before moving on to [Step 2: Subscribe workforce users to Amazon Q Developer Pro](subscribe-users.md).
The table uses the following terms:
+ *Standalone account* — An AWS account that is *not* part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html).
+ *Management account* — An AWS account that is part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html). It is the ultimate owner of the organization, and is responsible for paying all charges accrued by the accounts in its organization.
+ *Member account* — An AWS account, other than the management account, that is part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html).
| Deployment option | Description | Advantages | Disadvantages |
| --- | --- | --- | --- |
| **Deployment option 1 (easiest)**: Deploy in a standalone account | Use this option if you're an end user and you want to subscribe yourself (and optionally, a small team of users) to quickly evaluate the features of Amazon Q. With this deployment option, in your **standalone** account, you: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/deployment-options.html) | **Good for demos**. You can try out Pro tier features for yourself without having to do an enterprise-wide implementation. **More features than personal accounts (Builder IDs)**. For more information, see [Limitations of Builder IDs](getting-started-builderid.md#builder-id-limitations). | **Fewer features** Because IAM Identity Center is enabled in a standalone account, it is considered to be an *account instance*, which has fewer features than organization instances1. |
| **Deployment option 2**: Deploy in management and member accounts | Use this option if you're an administrator of multiple users. With this deployment option: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/deployment-options.html) | **More features**. Because IAM Identity Center is installed in a management account, it is considered to be an *organization instance*, which has more features than account instances2. **Distributed management**. Subscription management tasks are distributed across member accounts, which is a best practice. | **Complexity**. Requires coordination across accounts by multiple administrators. **Account restrictions**. You can subscribe users in a maximum of 20 accounts per AWS Region, per organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html). If your user base is spread across more than 20 accounts in the same Region under one organization, choose another option. |
| **Deployment option 3**: Deploy in a member account only | Use this option if you're an adminstrator of multiple users. With this deployment option, in a **member** account, you: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/deployment-options.html) | **Quick setup**. Individual member account administrators can deploy without waiting or needing approval for an enterprise-wide implementation. **Flexibility for complex organizations**. Use this option when you don't have a unified identity provider or identity store containing the entire user base that you want to subscribe to the Pro tier. | **Fewer features**. Because IAM Identity Center is enabled in a member account, it is considered to be an *account instance*, which has fewer features than organization instances1. |
| **Deployment option 4**: Deploy in a management account only | Use this option if you're an adminstrator of multiple users. With this deployment option, in the **management** account, you: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/deployment-options.html) For detailed instructions, see [Subscribe users to Amazon Q Developer Pro in a management account](subscribe-management.md). | **More features**. Because IAM Identity Center is installed in a management account, it is considered to be an *organization instance*, which has more features than account instances2. | **Does not comply with best practices**. Because users are subscribed in the management account, and because of a limitation in Amazon Q Developer where [delegated administration](https://docs.aws.amazon.com/singlesignon/latest/userguide/delegated-admin.html) is not supported, management account administrators must handle subscription management tasks. You cannot follow the [recommended practice](https://docs.aws.amazon.com/singlesignon/latest/userguide/delegated-admin.html#delegated-admin-best-practices) of delegating tasks to member accounts. |
1 Account instances support fewer features than organization instances. For example, account instances don't support permission sets, which means that users cannot use their Pro tier subscriptions [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md). For a list of the limitations of account instances, see [Account instance considerations](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html#about-account-instance) in the *AWS IAM Identity Center User Guide*.
2 Organization instances offer a broader range of features compared to account instances, encompassing all IAM Identity Center capabilities. For a list of features supported by organization instances, see [When to use an organization instance](https://docs.aws.amazon.com/singlesignon/latest/userguide/organization-instances-identity-center.html#when-to-use-organization-instance) in the *AWS IAM Identity Center User Guide*.
# Step 2: Subscribe workforce users to Amazon Q Developer Pro
After choosing a deployment option as described in [Step 1: Choose a deployment option](deployment-options.md), you are ready to subscribe workforce users. Subscribing workforce users involves three main steps: Enabling IAM Identity Center, creating the Amazon Q Developer profile, and subscribing users. Instructions on how to complete all steps are included in each of the following sections. You might need to read multiple sections if you're planning on performing steps in multiple accounts.
+ [Subscribe users to Amazon Q Developer Pro in a standalone account](subscribe-standalone.md)
+ [Subscribe users to Amazon Q Developer Pro in a management account](subscribe-management.md)
+ [Subscribe users to Amazon Q Developer Pro in a member account](subscribe-member.md)
# Subscribe users to Amazon Q Developer Pro in a standalone account
A *standalone* account is one that is *not* part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html).
If you are the owner of a standalone AWS account, use the following instructions to subscribe yourself (and a few others) to Amazon Q Developer Pro to evaluate the service’s features and functionality.
After completing the steps on this page, read [What resources were created?](#subscribe-standalone-resources) at the end to understand which resources were installed and configured on your behalf when you subscribed. This will help you cleanly remove everything when you're finished testing.
## Prerequisites
Before you begin, make sure that:
+ You have a **standalone** AWS account.
+ You have the minimum permissions required to subscribe users and manage Amazon Q Developer settings. For more information, see [Allow administrators to use the Amazon Q console](id-based-policy-examples-admins.md#q-admin-setup-admin-users-sub), and [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
+ (Optional) You have an account instance of IAM Identity Center set up in your standalone account. This IAM Identity Center contains the identities of the users you want to subscribe to Amazon Q Developer Pro, and must be deployed in a supported AWS Region, as described in [IAM Identity Center Regions supported by Amazon Q Developer](q-admin-setup-subscribe-regions.md#pro-subscription-regions). If you don't have an IAM Identity Center instance installed, that's ok. One will be installed when you subscribe the first user (yourself). The IAM Identity Center instance will be installed in the AWS Region where you subscribed the first user. For more information about IAM Identity Center, see [Organization and account instances of IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-center-instances.html) in the *AWS IAM Identity Center User Guide*.
**Note**
The instructions on this page assume you have not already installed an IAM Identity Center instance in your standalone account.
## Step 1: Create the Amazon Q Developer Pro profile and subscribe yourself
1. Sign in to the AWS Management Console using your standalone AWS account. Sign in as the root user, or as an IAM user with the permissions described in [Prerequisites](#subscribe-standalone-prereqs).
1. Switch to the **Amazon Q Developer** console.
1. Make sure you're in the AWS Region where you want to create the [Amazon Q Developer profile](subscribe-understanding-profile.md) and where you want to store user data. For supported Regions, see [Supported Regions for the Q Developer console and Q Developer profile](q-admin-setup-subscribe-regions.md#qdev-console-and-profile-regions).
1. Choose the **Get started** button.
**Note**
If you see a **Settings** button instead of **Get started** button, it means that you've already run through the 'Get started' workflow and can skip to [Step 2: Subscribe team members](#subscribe-standalone-sub-team).
A **Create your user** dialog box appears.
1. Enter your information. The email address can be the same or different from the one you used to sign up for your AWS account.
Choose **Continue**.
The **Create Amazon Q Developer profile** dialog box appears.
1. Review the contents of the dialog box and provide a name for your profile in **Profile name**. For help with cross-region inferencing, see [Cross-region processing in Amazon Q Developer](cross-region-processing.md). For help with disabling dashboard metrics, see [Disabling the Amazon Q Developer dashboard](dashboard-disabling.md).
Choose **Create application**.
The Amazon Q Developer profile and managed application are created, and your subscription is created.
1. (Optional) Verify that your subscription was created:
1. In the Amazon Q Developer console, in the navigation pane, choose **Subscriptions**.
1. In the main pane, choose the **Users** tab.
Your subscription should appear in the list in the **Pending** state. If not, refresh your browser tab.
**Note**
Your subscription will change to the **Active** state after your first use of Amazon Q Developer features.
Now that you are subscribed, you must activate your subscription. You can do this now, or after you've subscribed team members, as described in the next section. To activate your subscription, check your inbox for emails titled **Invitation to join AWS IAM Identity Center** and **Activate Your Amazon Q Developer Pro Subscription**. Follow the instructions in these emails to activate your Amazon Q Developer Pro subscription and set up Amazon Q Developer Pro in your IDE. You should receive these emails within 24 hours.
## Step 2: Subscribe team members
You might want to subscribe other team members so that they can try out Amazon Q Developer Pro with you. To subscribe them, use the following instructions.
**To add team members**
1. Switch to the IAM Identity Center console (not the IAM console).
**Note**
IAM Identity Center was set up on your behalf when you subscribed yourself. For more information about the IAM Identity Center that was set up, see [What resources were created?](#subscribe-standalone-resources).
1. Add users and groups. For instructions, see [Add users to your IAM Identity Center directory](https://docs.aws.amazon.com/singlesignon/latest/userguide/addusers.html) in the *AWS IAM Identity Center User Guide*.
![\[The IAM Identity Center page showing two users.\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/subscribe/Sub-8.png)
1. Go to the next procedure to subscribe team members.
**To subscribe team members**
1. Return to the Amazon Q Developer console.
1. In the navigation pane, choose **Subscriptions**, and then choose **Subscribe**.
The **Assign users and groups** dialog box appears.
1. Start typing the name of a team member or group that you added. The name should auto-populate.
**Note**
The dialog box only matches on user names or group names. It does not match on email addresses.
1. Choose **Assign**.
1. Have users check their email. They should receive an email titled **Activate Your Amazon Q Developer Pro Subscription** within 24 hours. In this email, users will find guidance on how to begin using their Amazon Q Developer Pro license in the AWS Management Console and their Integrated Development Environment (IDE). The email includes users' unique Start URL and AWS Region for authentication, and provides quickstart steps for using Amazon Q Developer in their IDE. This email streamlines the onboarding process and saves you valuable time by eliminating the need for you to manually notify each new user.
## What resources were created?
When you subscribed yourself (and optionally, team members), Amazon Q created the following AWS resources on your behalf:
+ **An account instance of IAM Identity Center**. For more information about account instances of IAM Identity Center, see [Account instances of IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html) in the *AWS IAM Identity Center User Guide*.
**Note**
Account instances of IAM Identity Center have [limitations](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html#about-account-instance). For example, account instances don't support console access. (Users can still use Amazon Q in the console, it's just that they'll be subject to the Free tier monthly limits.) If you want to use Amazon Q Developer Pro in the console and other AWS websites, you must be a user in an *organization instance* of IAM Identity Center, in a management account. For more information, see [Subscribe users to Amazon Q Developer Pro in a management account](subscribe-management.md).
**Note**
You can't convert or merge an account instance of IAM Identity Center into an organization instance.
+ **The first user**, in IAM Identity Center. You might have manually added team members too.
+ **Pro tier subscriptions** for the first user and team members, in Amazon Q Developer.
+ **An Amazon Q Developer profile**, in the Amazon Q Developer console, under **Settings**.
+ **A managed application** called **QDevProfile-*region***, in the IAM Identity Center that is set up in your standalone account. The application is associated with the Amazon Q Developer profile. Like the Amazon Q Developer profile, the application is created once and shared between all Amazon Q subscribers in your standalone account.
# Subscribe users to Amazon Q Developer Pro in a management account
A *management account* is an AWS account that is part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html). It is the ultimate owner of the organization, and is responsible for paying all charges accrued by the accounts in its organization.
If you are the owner of a management account, use the following instructions to subscribe users to Amazon Q Developer Pro in your account.
**Note**
If possible, subscribe users in member accounts instead of your management account. For more information, see [Step 1: Choose a deployment option](deployment-options.md).
For more information about organizations and management accounts, see [Terminology and concepts for AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html) in the *AWS Organizations User Guide*.
## Prerequisites
Before you begin, make sure that:
+ You have a **management** AWS account.
+ You have the minimum permissions required to subscribe users and manage Amazon Q Developer settings. For more information, see [Allow administrators to use the Amazon Q console](id-based-policy-examples-admins.md#q-admin-setup-admin-users-sub), and [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
+ You have an organization instance of IAM Identity Center set up in your management account. This IAM Identity Center contains the identities of the users you want to subscribe to Amazon Q Developer Pro, and must be deployed in a supported AWS Region, as described in [IAM Identity Center Regions supported by Amazon Q Developer](q-admin-setup-subscribe-regions.md#pro-subscription-regions). For more information about IAM Identity Center, see [Organization instances of IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/organization-instances-identity-center.html) in the *AWS IAM Identity Center User Guide*.
## Step 1: Create the Amazon Q Developer profile
1. Sign in to the AWS Management Console using your AWS management account.
1. Switch to the **Amazon Q Developer** console.
1. Make sure you're in the AWS Region where you want to create the [Amazon Q Developer profile](subscribe-understanding-profile.md) and where you want to store user data. For supported Regions, see [Supported Regions for the Q Developer console and Q Developer profile](q-admin-setup-subscribe-regions.md#qdev-console-and-profile-regions).
1. Choose **Get started**.
The **Create Amazon Q Developer profile** dialog box appears.
1. Review the contents of the dialog box and provide a name for your profile in **Profile name**. For help with:
+ Cross-region inferencing, see [Cross-region processing in Amazon Q Developer](cross-region-processing.md).
+ The **Share Amazon Q Developer settings with member account** check box, see [Enabling profile sharing in Amazon Q Developer](q-admin-profile-sharing.md) and [Step 1: Choose a deployment option](deployment-options.md).
+ Disabling dashboard metrics, see [Disabling the Amazon Q Developer dashboard](dashboard-disabling.md).
Choose **Create application**.
The Amazon Q Developer profile and managed application are created.
## Step 2: Subscribe users
1. In the Amazon Q Developer console, from the navigation pane, choose **Subscriptions**.
1. Choose **Subscribe**.
The **Assign users and groups** dialog box appears.
1. Start typing the group or user you want to subscribe. The group or user will auto-populate with the ones available in the IAM Identity Center set up in your management account.
**Note**
The dialog box only matches on user names or group names. It does not match on email addresses.
1. Choose **Assign**.
1. Have users check their email. They should receive an email titled **Activate Your Amazon Q Developer Pro Subscription** within 24 hours with instructions on how to begin using their Amazon Q Developer Pro license.
## Step 3: Enable identity-enhanced console sessions
If you want to allow users to use their Amazon Q Developer Pro subscription [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md), enable identity-enhanced console sessions. For more information, see [Enabling identity-enhanced console sessions](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-aware-sessions.html) in the *AWS IAM Identity Center User Guide*.
**Note**
If you don't enable identity-enhanced console sessions, users can still use Amazon Q in the AWS Management Console, and on AWS apps and websites, but they'll be limited to the Free tier.
## What resources were created?
When you created the Amazon Q Developer profile and subscribed users in your management account, Amazon Q created the following resources on your behalf:
+ **Pro tier subscriptions** for users, in Amazon Q Developer.
+ **An Amazon Q Developer profile**, in the Amazon Q Developer console, under **Settings**.
+ **A managed application** called **QDevProfile-*region***, in the IAM Identity Center that is set up in your management account. The application is associated with the Amazon Q Developer profile. Like the Amazon Q Developer profile, the application is created once and shared between all Amazon Q subscribers in your management account.
**Note**
Amazon Q can create the **QDevProfile-*region*** managed application in a maximum of 20 AWS accounts per AWS Region within an organization.
# Subscribe users to Amazon Q Developer Pro in a member account
A *member account* is an AWS account, other than the management account, that is part of an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html).
If you are the owner of a member account, use the following instructions to subscribe users to Amazon Q Developer Pro in your account.
Not sure whether to subscribe users in a member or management account? See [Step 1: Choose a deployment option](deployment-options.md) for help.
For more information about organizations, member accounts, and management accounts, see [Terminology and concepts for AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html) in the *AWS Organizations User Guide*.
## Prerequisites
Before you begin, make sure that:
+ You have a **member** AWS account.
+ You have the minimum permissions required to subscribe users and manage Amazon Q Developer settings. For more information, see [Allow administrators to use the Amazon Q console](id-based-policy-examples-admins.md#q-admin-setup-admin-users-sub), and [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
+ (Optional) You have an organization instance of IAM Identity Center set up in the *management account* or an account instance of IAM Identity Center set up in your *member account*. This IAM Identity Center intance contains the identities of the users you want to subscribe to Amazon Q Developer Pro, and must be deployed in a supported AWS Region, as described in [IAM Identity Center Regions supported by Amazon Q Developer](q-admin-setup-subscribe-regions.md#pro-subscription-regions). If you don't have an IAM Identity Center instance installed, that's ok. One will be installed in your member account when you subscribe the first user. The IAM Identity Center instance will be installed in the AWS Regionn where you subscribed the first user. For more information about IAM Identity Center, see [Organization and account instances of IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-center-instances.html) in the *AWS IAM Identity Center User Guide*.
## Step 1: Create the Amazon Q Developer Pro profile and subscribe the first user
1. Sign in to the AWS Management Console using your member AWS account.
1. Switch to the **Amazon Q Developer** console.
1. Make sure you're in the AWS Region where you want to create the [Amazon Q Developer profile](subscribe-understanding-profile.md) and where you want to store user data. For supported Regions, see [Supported Regions for the Q Developer console and Q Developer profile](q-admin-setup-subscribe-regions.md#qdev-console-and-profile-regions).
1. Choose the **Get started** button.
**Note**
If you see a **Settings** button instead of **Get started** button, it means that you've already run through the 'Get started' workflow and can skip to [Step 2: Subscribe other users](#subscribe-member-new-other).
1. Follow the on-screen prompts to subscribe your first user.
+ If the first user's email address matches one in an existing IAM Identity Center in either your member account or a management account, then Amazon Q connects to that IAM Identity Center.
+ If the first user's email address doesn't match one in an existing IAM Identity Center, then Amazon Q creates an IAM Identity Center account instance in your member account, and adds the first user to it. Note that:
+ Amazon Q only creates an IAM Identity Center account instance if there is no IAM Identity Center already in your member account.
+ If there is an IAM Identity Center account instance in your member account, but the user is not in it, then Amazon Q creates the user in the existing IAM Identity Center.
The **Create Amazon Q Developer profile** dialog box appears.
1. Review the contents of the dialog box and provide a name for your profile in **Profile name**. For help with cross-region inferencing, see [Cross-region processing in Amazon Q Developer](cross-region-processing.md). For help with disabling dashboard metrics, see [Disabling the Amazon Q Developer dashboard](dashboard-disabling.md).
Choose **Create application**.
The Amazon Q Developer profile and managed application are created, and the first user is subscribed.
1. (Optional) Verify that the first user's subscription was created:
1. In the Amazon Q Developer console, in the navigation pane, choose **Subscriptions**.
1. In the main pane, choose the **Users** tab.
The subscription of the first user should appear in the list in the **Pending** state. If not, refresh your browser tab.
**Note**
The subscription will change to the **Active** state after the user's first use of Amazon Q Developer features.
1. Have the first user check their email. They should receive an email titled **Activate Your Amazon Q Developer Pro Subscription** within 24 hours. In this email, users will find guidance on how to begin using their Amazon Q Developer Pro license in the AWS Management Console and their Integrated Development Environment (IDE). The email includes users' unique Start URL and AWS Region for authentication, and provides quickstart steps for using Amazon Q Developer in their IDE. This email streamlines the onboarding process and saves you valuable time by eliminating the need for you to manually notify each new user.
## Step 2: Subscribe other users
To subscribe other users, add them to your IAM Identity Center instance if they're not already there, and then subscribe them to Amazon Q Developer Pro by choosing **Subscribe** in the Amazon Q Developer console.
For instructions on adding users to IAM Identity Center, see [Add users to your IAM Identity Center directory](https://docs.aws.amazon.com/singlesignon/latest/userguide/addusers.html) in the *AWS IAM Identity Center User Guide*.
## Step 3: Enable identity-enhanced console sessions
If you want to allow users to use their Amazon Q Developer Pro subscription [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md), enable identity-enhanced console sessions. For more information, see [Enabling identity-enhanced console sessions](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-aware-sessions.html) in the *AWS IAM Identity Center User Guide*.
If you don't enable identity-enhanced console sessions, users can still use Amazon Q in the AWS Management Console, and on AWS apps and websites, but they'll be limited to the Free tier.
**Note**
The ability to enable identity-enhanced console sessions—and therefore the ability to use Amazon Q Developer Pro subscriptions in the AWS Management Console, and on AWS apps and websites—is only supported with organization instances of IAM Identity Center, not account instances.
## What resources were created?
When you subscribed users in your member account, Amazon Q created the following AWS resources on your behalf:
+ **An account instance of IAM Identity Center**. This instance is only created if the first user you subscribed wasn't found in an existing IAM Identity Center in the member account or management account. For more information about account instances of IAM Identity Center, see [Account instances of IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html) in the *AWS IAM Identity Center User Guide*.
**Note**
Account instances of IAM Identity Center have [limitations](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html#about-account-instance). For example, account instances don't support console access. (Users can still use Amazon Q in the console, it's just that they'll be subject to the Free tier monthly limits.) If you want your users to be able to use Amazon Q Developer Pro in the console and other AWS websites, they must exist in an *organization instance* of IAM Identity Center, in a management account. For more information, see [Subscribe users to Amazon Q Developer Pro in a management account](subscribe-management.md).
**Note**
You can't convert or merge an account instance of IAM Identity Center into an organization instance.
+ **The first user**, in IAM Identity Center. (You might have added team members too.)
+ **Pro tier subscriptions** for the first user and other users, in Amazon Q Developer.
+ **An Amazon Q Developer profile**, in the Amazon Q Developer console, under **Settings**.
+ **A managed application** called **QDevProfile-*region***, in IAM Identity Center. The application is associated with the Amazon Q Developer profile. Like the Amazon Q Developer profile, the application is created once and shared between all Amazon Q Developer Pro subscribers in your member account.
**Note**
Amazon Q can create the **QDevProfile-*region*** managed application in a maximum of 20 AWS accounts per AWS Region within an organization.
# Amazon Q Developer Pro subscriptions
An *Amazon Q Developer Pro subscription*, also called a *Pro tier subscription*, is a paid version of the Amazon Q Developer service. It offers enhanced AI development capabilities designed for professional developers and teams who require advanced features and higher usage limits beyond the Free tier offering. For more information about pricing tiers and feature availability, see the [Amazon Q Developer pricing page](https://aws.amazon.com/q/developer/pricing/).
This chapter covers essential information for managing Amazon Q Developer Pro subscriptions for both personal accounts (Builder IDs) and workforce users (IAM Identity Center). It describes Region availability and support, billing details, and subscription status information. It also provides step-by-step guidance for key tasks such as unsubscribing, and upgrading to the Pro tier.
**Topics**
+ [Amazon Q Developer Pro Region support](q-admin-setup-subscribe-regions.md)
+ [Amazon Q Developer Pro subscription billing](tracking-across-org-cost-usage.md)
+ [Amazon Q Developer subscription statuses](q-admin-setup-subscribe-status.md)
+ [Finding the Start URL for use with Amazon Q Developer](manage-account-details.md)
+ [Managing the encryption method in Amazon Q Developer](manage-encryption.md)
+ [What is the Amazon Q Developer profile?](subscribe-understanding-profile.md)
+ [Troubleshooting Amazon Q Developer Pro subscriptions](q-admin-setup-subscribe-troubleshooting.md)
+ [Viewing an aggregated list of Amazon Q Developer subscriptions](subscribe-visibility.md)
+ [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md)
+ [Upgrading to Amazon Q Developer Pro](upgrade-to-pro.md)
# Amazon Q Developer Pro Region support
Region information for the Pro tier varies depending on whether you're an end-user with a personal account (Builder ID), or you're an administrator of IAM Identity Center workforce users.
## Personal account (Builder ID) users
If you're the owner of a personal account (Builder ID), your Pro tier subscription is supported in the following Region:
+ US East (N. Virginia)
## IAM Identity Center workforce users
Read this section if you're an administrator of IAM Identity Center workforce users.
**Topics**
+ [IAM Identity Center Regions supported by Amazon Q Developer](#pro-subscription-regions)
+ [Supported Regions for the Q Developer console and Q Developer profile](#qdev-console-and-profile-regions)
+ [Subscribing users to Amazon Q Developer Pro across AWS Regions](#subscribe-multi-region)
### IAM Identity Center Regions supported by Amazon Q Developer
The workforce users that you want to subscribe to Amazon Q Developer Pro must have identities in an IAM Identity Center instance (or a connected identity provider) in one of the Regions listed on the [Supported Regions page](regions.md#default-regions), except for opt-in Regions. If your users have identities in an IAM Identity Center instance in an opt-in Region, they can't be subscribed, which means they will only have access to the Free tier [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md), and they won’t have access to Amazon Q in the IDE or at the command line.
Amazon Q stores the subscriptions of IAM Identity Center workforce users in the same Region as your IAM Identity Center instance.
Regardless of the IAM Identity Center Region, data is stored in the Region where you create the Amazon Q Developer profile.
For more information about Amazon Q Developer profiles, see [What is the Amazon Q Developer profile?](subscribe-understanding-profile.md).
For more information about data protection, see [Data protection in Amazon Q Developer](data-protection.md).
### Supported Regions for the Q Developer console and Q Developer profile
The **Amazon Q Developer console** and **Amazon Q Developer profile** are supported in the following Regions:
+ US East (N. Virginia)
+ Europe (Frankfurt)
For more information about the Amazon Q Developer profile, see [What is the Amazon Q Developer profile?](subscribe-understanding-profile.md).
**Note**
The following features aren’t supported for Q Developer profiles created in the Europe (Frankfurt) Region:
[Chatting with Support](support-chat.md)
[Troubleshooting resources with Amazon Q](chat-actions-troubleshooting.md)
[.NET transformations in the IDE](transform-dotnet-IDE.md)
[Amazon Q in chat applications (for Slack)](q-in-chat-applications.md)
Amazon Q in the AWS Console Mobile Application
[GitLab Duo with Amazon Q](gitlab-with-amazon-q.md)
[Amazon Q for GitHub](amazon-q-for-github.md)
### Subscribing users to Amazon Q Developer Pro across AWS Regions
When you subscribe an IAM Identity Center workforce user to Amazon Q Developer Pro, you might need to work in two different AWS Regions:
+ One Region for the IAM Identity Center instance (where user identities are managed, and where subscriptions are stored)
+ Another Region for the Amazon Q Developer console (where the [Amazon Q Developer profile](subscribe-understanding-profile.md), customizations, and subscriptions are managed)
The Regions are not always the same because the Amazon Q Developer console is supported in fewer Regions than IAM Identity Center.
In a scenario where your IAM Identity Center is in a different Region from your Amazon Q Developer console, use the guidance in the following example to subscribe users.
#### Example subscription process in a multi-Region scenario
Let's walk through subscribing a user where:
+ The IAM Identity Center instance is in **US West (N. California)**.
+ The Amazon Q Developer console is in **US East (N. Virginia)**. This is the closest Region to the IAM Identity Center instance that the Amazon Q Developer console supports.
**To subscribe the user**
1. Add the user in your IAM Identity Center instance in **US West (N. California)**.
1. Switch to the Amazon Q Developer console in the **US East (N. Virginia)**.
1. Subscribe the user through the Amazon Q Developer console in **US East (N. Virginia)**.
Upon being subscribed:
+ The user's subscription is created in **US West (N. California)**.
+ The user's subscription is associated with their user entry in **US West (N. California)**.
+ The user's subscription is associated with the Amazon Q Developer profile in **US East (N. Virginia)**.
Additionally, any data that Amazon Q Developer needs to store on the user's behalf will be stored in **US East (N. Virginia)**. For more information about data storage and security, see [Encryption at rest](data-encryption.md#encryption-rest).
For detailed instructions on subscribing users, see [Getting started with IAM Identity Center](getting-started-idc.md).
# Amazon Q Developer Pro subscription billing
Billing information for the Pro tier varies depending on whether you're an end-user with a personal account (Builder ID), or you're an administrator of IAM Identity Center workforce users.
## Personal account (Builder ID) users
If you subscribed to the Pro tier with a personal account (Builder ID), you will be billed monthly. The AWS account that is linked to your Builder ID gets the bill.
The very first month you are subscribed, you are charged a prorated fee. For example, if you subscribe April 15th, you'll be charged half the subscription fee. After that, you'll be charged the full amount.
If you unsubscribe, billing stops at the end of the billing cycle. For more information, see [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md).
## IAM Identity Center workforce users
If you're an administrator who has subscribed a set of IAM Identity Center workforce users to the Pro tier, you will be billed monthly for each user that you subscribe. For more information, see [Amazon Q Developer pricing](https://aws.amazon.com/q/developer/pricing).
If your business has [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html) set up, billing for Amazon Q Developer Pro usage is per AWS organization. The management account gets the bill. If the same user is subscribed to Amazon Q Developer in multiple accounts within the same organization, you will not be double-billed.
If you don't have AWS Organizations set up, the AWS account under which your users are subscribed gets the bill.
You can view your bill in the Billing and Cost Management console. The Amazon Q expenses are listed on the **Charges by service** tab, under **Q**. For more information about the Billing and Cost Management console, see [What is AWS Billing and Cost Management?](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-what-is.html) in the *AWS Billing User Guide*.
You can identify the cost of Amazon Q subscriptions for specific users with resource IDs through AWS Billing and Cost Management. To do so, in the Billing and Cost Management console under [Data Exports](https://console.aws.amazon.com/costmanagement/home#/bcm-data-exports), create either a standard data export or a legacy CUR export with the **Include resource IDs** option selected. To learn more, refer to [Creating data exports](https://docs.aws.amazon.com/cur/latest/userguide/dataexports-create.html?icmpid=docs_costmanagement_hp-dataexports-export-type) in the *AWS Data Exports User Guide*.
If you unsubscribe users, billing stops at the end of the billing cycle. For more information, see [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md).
# Amazon Q Developer subscription statuses
Subscription status information varies depending on whether you're an end-user with a personal account (Builder ID), or you're an administrator of IAM Identity Center workforce users.
## Personal account (Builder ID) users
If you are a user with a personal account (Builder ID), you can view the status of your Amazon Q Developer Pro subscription on the **Subscriptions** page of the Amazon Q Developer console.
The possible statuses of your subscription are:
+ **Active** – You have activated your subscription by using Amazon Q Developer features. You are being charged for your subscription.
+ **Canceled** – You canceled your subscription by unsubscribing from the Pro tier. You can no longer access Amazon Q Developer features and limits. For more information, see [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md).
## IAM Identity Center workforce users
If you're an administrator who has subscribed a set of IAM Identity Center workforce users to the Pro tier, you can view the status of your users' subscriptions on the **Subscriptions** page of the Amazon Q Developer console.
The statuses will be slightly different depending on whether you’re looking at the **Groups** tab or the **Users** tab.
The statuses on the **Groups** tab are:
+ **Subscribed** – The group is subscribed to Amazon Q Developer Pro. You will be charged for active user subscriptions in the group.
+ **Canceled** – The group was canceled (unsubscribed) by an administrator. Users in the group can no longer access Amazon Q Developer Pro features. For more information, see [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md).
The statuses on the **Users** tab are:
+ **Active** – The user has activated their subscription by using Amazon Q Developer features. You are being charged for this subscription.
+ **Pending** – The user is subscribed but has not activated their subscription. You are not being charged for this subscription.
+ **Canceled** – The user's subscription was canceled (unsubscribed) by an administrator, and the user can no longer access Amazon Q Developer features. For more information, see [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md).
**Note**
The **Users** tab of the Amazon Q Developer console does *not* show users who are subscribed as part of a group. To see these users, navigate to the Amazon Q console's (*not* the Amazon Q Developer console's) **Subscriptions** page. On this page, group-subscribed users will appear with a status of **Unavailable**. To see their actual status, choose a user from the table, and look for their status under **User associations**.
# Finding the Start URL for use with Amazon Q Developer
**Note**
This section does not apply to personal accounts (Builder IDs).
If you're an administrator who has subscribed a set of IAM Identity Center workforce users to the Pro tier, those users will need to sign in to Amazon Q in their IDE or at the command line using your IAM Identity Center's Start URL and Region. If you need to provide this URL to your users, you can find it in the Amazon Q Developer console, on the **Settings** page. The start URL is specific to your organization.
**To find the Start URL**
1. Sign in to the AWS Management Console.
1. Switch to the Amazon Q Developer console.
To use the Amazon Q Developer console, you must have the permissions defined in [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users) .
1. Choose **Settings**.
The start URL is shown in **Start URL** near the top of the page. The start URL is specific to your organization.
# Managing the encryption method in Amazon Q Developer
**Note**
This section does not apply to personal accounts (Builder IDs).
By default, Amazon Q Developer uses an AWS managed key for encryption. For some features, you can set up a customer managed key to encrypt data. For a list of features that support encryption with customer managed keys, see [Data encryption](data-encryption.md#encryption-rest).
To set the key used for encryption, complete the following procedure.
1. Sign in to the AWS Management Console.
1. Switch to the Amazon Q Developer console.
To use the Amazon Q Developer console, you must have the permissions defined in [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users) .
1. Choose **Settings**.
1. Choose **Edit** in the Amazon Q Developer account details panel.
![\[The Amazon Q Developer console settings page\]](http://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/images/q-dev-console-settings-3.png)
1. On the **Edit details** page, expand the **Encryption key - optional** section.
1. To use a customer managed key for encryption, select **Customize encryption settings (advanced)**.
1. In the search bar that appears, search for the name of the key you want to use for encryption or enter the key ARN.
If you haven't created a key yet, choose **Create an AWS KMS key**, and then return to this page to add your key.
1. To disable encryption with your customer managed key and revert to an AWS managed key for encryption, deselect **Customize encryption settings (advanced)**.
# What is the Amazon Q Developer profile?
**Note**
This section does not apply to personal accounts (Builder IDs).
An *Amazon Q Developer profile*, also known as a *settings profile*, a collection of Amazon Q Developer settings associated with a set of IAM Identity Center workforce user Pro tier subscriptions. The profile is also associated with an Amazon Q Developer managed application which ties the user's identity in IAM Identity Center to their subscription in Amazon Q Developer.
The very first time you subscribe users, you will be prompted to create this profile. Creating the profile causes several pages to appear in the side navigation of the Amazon Q Developer console where you can configure Amazon Q Developer Pro features. All subscriptions that you add to your account (during the initial subscription process, and later) will be associated with this profile.
Other characteristics of the Amazon Q Developer profile are:
+ The profile is mandatory for use with IAM Identity Center workforce users. You cannot subscribe workforce users without it. It must be created in the AWS account where you want to subscribe users to Amazon Q Developer Pro.
+ The profile can be created once per supported AWS Region, per AWS account. For a list of AWS Regions supported by the Amazon Q Developer profile, see [Supported Regions for the Q Developer console and Q Developer profile](q-admin-setup-subscribe-regions.md#qdev-console-and-profile-regions).
# Creating the Amazon Q Developer profile
**Note**
This section does not apply to personal accounts (Builder IDs).
Creating the Amazon Q Developer profile unlocks settings in the Amazon Q Developer console and is a prerequisite for subscribing users to Amazon Q Developer Pro. For more information about the profile, see [What is the Amazon Q Developer profile?](subscribe-understanding-profile.md).
**To create the Amazon Q Developer profile**
+ Subscribe users according to the instructions in [Getting started with IAM Identity Center](getting-started-idc.md). During the subscription process, you will be asked to create the profile.
# Deleting the Amazon Q Developer profile
**Note**
This section does not apply to personal accounts (Builder IDs).
You might want to delete the Amazon Q Developer profile to quickly cancel all subscriptions and remove all Q Developer configurations from your AWS account. When you delete the Amazon Q Developer profile, the following occurs:
+ All subscriptions associated with the profile marked as **Canceled**, and users will no longer be able to access Amazon Q Developer features. The final monthly subscription fee is charged at the end of the current billing cycle for all users who had active subscriptions. You'll be charged for the full month; the fee won't be prorated. Subscriptions will continue to be visible in the Amazon Q Developer console until the end of the month, at which time they will be removed from view.
+ All settings and options in the Amazon Q Developer console that became available as a result of creating the profile will no longer be visible or take effect. For example, the Q Developer dashboard will no longer be visible, customizations will no longer be configurable or applied, and user activity reports will no longer be configurable or generated.
+ The managed application (called **QDevProfile-*region***) will be removed from the IAM Identity Center instance that is connected to Amazon Q Developer. (This IAM Identity Center instance might be a different account from the one where the profile is being deleted, depending on your [deployment option](deployment-options.md).)
**Note**
If you accidentally delete the profile:
You'll have to recreate it and then resubscribe users. You'll also have to reset any settings you configured previously through the Amazon Q Developer console. Your IAM Identity Center instance will remain, so there is no need to recreate user identities.
You won't be able to see historical data in the Amazon Q Developer dashboard after recreating the profile; you can only see data starting from the date of the new profile creation onward.
Use the following instructions to delete the Amazon Q Developer profile.
**Before you begin**
+ Remove any customizations you might have created to allow for the successful deletion of the profile.
**To delete the Amazon Q Developer profile**
1. Sign in to the AWS Management Console.
1. Switch to the Amazon Q Developer console.
To use the Amazon Q Developer console, you must have the permissions defined in [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
1. Choose **Settings**.
1. Near the top of the page, choose **Delete profile**.
# Enabling profile sharing in Amazon Q Developer
**Note**
This section does not apply to personal accounts (Builder IDs).
If you are a management account administrator within an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html), you can enable the *profile sharing* feature. When profile sharing is enabled, the [Amazon Q Developer profile](subscribe-understanding-profile.md) that has been created in a management account will be shared with member accounts. Sharing the profile has one benefit: it allows IAM Identity Center workforce users who are subscribed to Amazon Q Developer Pro in a *management* account to use their Amazon Q Developer Pro subscription [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md) while signed in to a *member* account. When profile sharing is disabled, these users can still use Amazon Q in the AWS Management Console, and on AWS apps and websites, while signed in to a member account, but they'll be subject to Free tier limits and features.
Enabling profile sharing has no effect on users' ability to use [Amazon Q in the integrated development environment (IDE)](q-in-IDE.md) or [on the command line](command-line.md).
Use the following instructions to enable profile sharing.
**Prerequisites**
Before you begin, make sure that:
+ You are an administrator of an AWS *management* account.
+ You have an IAM Identity Center instance set up in your management account and connected to Amazon Q. To check, sign in to your management account, go to the Amazon Q Developer console, choose **Settings**, and make sure that a **Start URL** appears.
+ You have subscribed users to Amazon Q Developer Pro in your management account.
+ You have the minimum permissions required to access the Amazon Q Developer console. For more information, see [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
**To enable profile sharing**
1. Sign in to the AWS Management Console using your AWS management account.
1. Switch to the Amazon Q Developer console.
1. Choose **Settings**.
1. Scroll to the **Member account settings** section and choose **Edit**.
1. Enable **Q Developer managed application and settings profile**.
1. Choose **Save**.
Users who are subscribed to Amazon Q Developer Pro in your management account will now be able to use their Amazon Q Developer Pro subscription in the AWS Management Console, and on AWS apps and websites while signed in to a member account.
# Troubleshooting Amazon Q Developer Pro subscriptions
If you are having trouble with Amazon Q Developer Pro subscriptions, review the following issues to understand how to resolve them.
**Topics**
+ [Unable to subscribe users](unable-to-subscribe-standalone.md)
+ [Users not receiving activation emails](users-not-receiving-emails.md)
+ [Users unable to use their subscription on AWS websites](unable-to-use-pro-on-websites.md)
+ [Users unable to use their subscription in the IDE](unable-to-use-pro-in-ide.md)
+ [Can't see subscribed users](users-not-appearing.md)
# Unable to subscribe users
**Problem: Unable to subscribe users to Amazon Q Developer Pro**
**Solutions:**
+ Verify that you have the minimum permissions required to subscribe users. For more information, see [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users). After you obtain the necessary permissions, reload the console page to access Amazon Q.
+ Check that you're in the Amazon Q Developer console (not the Amazon Q console).
+ Check that you're in a supported AWS Region for Amazon Q Developer. For more information, see [Supported Regions for the Q Developer console and Q Developer profile](q-admin-setup-subscribe-regions.md#qdev-console-and-profile-regions).
+ Ensure you're following the correct workflow for the type of account you have. For more information, see [Getting started with a personal account (Builder ID)](getting-started-builderid.md), [Subscribe users to Amazon Q Developer Pro in a standalone account](subscribe-standalone.md), [Subscribe users to Amazon Q Developer Pro in a management account](subscribe-management.md), or [Subscribe users to Amazon Q Developer Pro in a member account](subscribe-member.md).
# Users not receiving activation emails
**Problem: Users are not receiving activation emails**
**Solutions:**
+ Verify the email address is correct in AWS IAM Identity Center.
+ Have users check their spam or junk folders for emails titled **Activate Your Amazon Q Developer Pro Subscription**.
+ Allow up to 24 hours for activation emails to be delivered.
+ Verify the user was properly added to IAM Identity Center. For more information, see [Add users to your IAM Identity Center directory](https://docs.aws.amazon.com/singlesignon/latest/userguide/addusers.html) in the *AWS IAM Identity Center User Guide*.
# Users unable to use their subscription on AWS websites
**Problem: Users are unable to use their subscriptions on AWS websites**
When attempting to use Amazon Q [in the AWS Management Console, and on AWS apps and websites](q-on-aws.md), users see the following message in their browser:
`Your account has not been configured to use an Amazon Q subscription. You currently have access to the Free tier of Amazon Q. Contact your AWS administrator to configure your subscription.`
**Solutions:**
+ Verify that identity-enhanced console sessions are enabled (only available with organization instances of IAM Identity Center). For information about how to enable identity-enhanced console sessions, see [Enabling identity-enhanced console sessions](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-aware-sessions.html).
+ Check that the user has an active Amazon Q Developer Pro subscription. For more information, see [Amazon Q Developer subscription statuses](q-admin-setup-subscribe-status.md).
+ Verify that you're not using an account instance of IAM Identity Center. Account instances don't support console access. For more information, see [Account instance considerations](https://docs.aws.amazon.com/singlesignon/latest/userguide/account-instances-identity-center.html#about-account-instance) in the *AWS IAM Identity Center User Guide*.
Users with identities in an account instance of IAM Identity Center can still use Amazon Q in the console but will be limited to Free tier.
+ If the user recently switched from the Free tier to the Pro tier, have them sign out of the AWS Management Console or another AWS website and sign back in again.
+ If you subscribed the user as part of a group, allow up to 24 hours for their subscription to be activated. There might be a delay between the time the user is added to the group and the time their subscription becomes active.
+ Verify that the user's access to the Amazon Q Developer Pro managed application was not revoked or that the managed application was not deleted. Restore access to the managed application if needed.
+ If users don't have an active subscription, try getting them to refresh their page so that they can use the Free tier.
# Users unable to use their subscription in the IDE
**Problem: IAM Identity Center workforce users are unable to use their Pro subscriptions in the IDE**
**Solutions:**
+ Check that the user has an active Amazon Q Developer Pro subscription. For more information, see [Amazon Q Developer subscription statuses](q-admin-setup-subscribe-status.md).
+ If the user recently switched from the Free tier to the Pro tier, have them sign out of Amazon Q in the IDE and sign back in again.
+ If you subscribed the user as part of a group, allow up to 24 hours for their subscription to be activated. There might be a delay between the time the user is added to the group and the time their subscription becomes active.
+ Verify that the user's access to the Amazon Q Developer Pro managed application was not revoked or that the managed application was not deleted. Restore access to the managed application if needed.
+ Have users sign in with a Builder ID to use the Free tier while they wait for their subscription to become active. For more information, see [Installing the Amazon Q Developer extension or plugin in your IDE](q-in-IDE-setup.md).
# Can't see subscribed users
**Problem: Subscribed users are not appearing in the Amazon Q Developer console.**
You have subscribed one or more users to the Pro tier, but when you navigate to the Amazon Q Developer console's **Subscriptions** page, you can't see them.
**Solutions:**
+ Make sure you're signed in to the correct AWS account and AWS Region.
+ Try switching to the **Amazon Q** console. The Amazon Q console is able to display users who were subscribed as part of a group, and is also able to display subscriptions across multiple accounts in an organization managed by AWS Organizations.
+ If you switched to the **Amazon Q** console, and still can't see users, do the following:
+ Make sure you're in the correct AWS Region. You will need to be in the Region where your IAM Identity Center instance is deployed. This might be a different Region from your Amazon Q Developer console and profile.
+ If you're using AWS Organizations, try enabling trusted access so that you can see subscriptions in both management and member accounts. For more information, see [Viewing an aggregated list of Amazon Q Developer subscriptions](subscribe-visibility.md).
# Viewing an aggregated list of Amazon Q Developer subscriptions
**Note**
This section does not apply to personal accounts (Builder IDs).
If you are a management account administrator within an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html), you can configure Amazon Q to display Amazon Q Developer Pro subscriptions from both *management* and *member* accounts in a single, unified list on the **Subscriptions** page of the Amazon Q console (*not* the Amazon Q Developer console) while signed in to your management account. This organization-wide visibility eliminates the need to sign in to multiple accounts to track your subscriptions.
**Note**
Unified subscription information also appears on the **Dashboard** page of the Amazon Q Developer console when you enable organization-wide visibility.
If you are a member account administrator, you will only ever be able to view the subscriptions within the member accounts that you administer. This is true regardless of whether organization-wide visibility was enabled in the management account.
To enable organization-wide visibility of Amazon Q Developer subscriptions, you must enable trusted access to Amazon Q in your organization. *Trusted access* is an AWS Organizations feature that lets you designate Amazon Q as a *trusted service* that is allowed to query your organization's structure. This querying is required in order to show the status of subscriptions.
To learn more about trusted access, see [Enabling trusted access for AWS Account Management](https://docs.aws.amazon.com/accounts/latest/reference/using-orgs-trusted-access.html) in the *AWS Organizations User Guide*.
To learn more about member and management accounts, see [Terminology and concepts for AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_getting-started_concepts.html) in the *AWS Organizations User Guide* for explanations.
Use the following instructions to enable trusted access to Amazon Q in your organization.
**Prerequisites**
Before you begin, make sure that:
+ You are an administrator of an AWS *management* account.
+ You have an *organization instance* of IAM Identity Center set up in your management account and connected to Amazon Q Developer.
+ Your organization instance of IAM Identity Center contains users who are subscribed to Amazon Q Developer Pro in member accounts.
+ You have the minimum permissions required to perform actions in the Amazon Q or Amazon Q Developer console (you can use either console to enable trusted access). For more information, see [Allow administrators to use the Amazon Q console](id-based-policy-examples-admins.md#q-admin-setup-admin-users-sub) and [Allow administrators to use the Amazon Q Developer console](id-based-policy-examples-admins.md#q-admin-setup-admin-users).
**To enable trusted access (enable organization-wide visibility of subscriptions)**
1. Sign in to the AWS Management Console using your AWS management account.
1. Do one of the following depending on the console you want to use:
+ Switch to the Amazon Q console.
Choose **Subscriptions**.
At the bottom of the page, in the **Subscription view settings** section, choose **Edit**.
Choose **On**.
+ Switch to the Amazon Q Developer console.
Choose **Settings**.
In the **Subscription view settings** section, choose **Edit**.
Enable the toggle.
1. Choose **Save**.
Trusted access to Amazon Q is now enabled. Users and groups who are subscribed in member accounts now appear in the Amazon Q console (not the Amazon Q Developer console) when you're signed in as a management account administrator.
# Unsubscribing from Amazon Q Developer Pro
How you unsubscribe from the Pro tier depends on whether you're an end-user with a personal account (Builder ID) or an administrator of IAM Identity Center workforce users.
## Unsubscribing a personal account (Builder ID)
Read this section if you want to unsubscribe your personal account (Builder ID) from the Pro tier.
When you unsubscribe your Builder ID, your subscription is marked as **Canceled**, and you can no longer access Amazon Q Developer features. (You can still use the [Free tier](q-tiers.md) though, provided you have not exceeded your Free tier limits.) The final monthly subscription fee is charged at the end of the current billing cycle. You'll be charged for the full month; the fee won't be prorated.
**Warning**
Deleting your Builder ID does not unsubscribe you. To stop being billed, you must actively unsubscribe yourself using the instructions in this section. Similarly, deleting your Amazon Q Developer Profile or Kiro Profile does not cancel your Builder ID subscription.
You can unsubscribe starting from one of the following interfaces:
+ IDE
+ command line
+ AWS Management Console
------
#### [ IDE ]
**To unsubscribe your Builder ID starting from your IDE**
1. Authenticate to Amazon Q in your IDE using your personal account (Builder ID). For more information, see [Installing the Amazon Q Developer extension or plugin in your IDE](q-in-IDE-setup.md).
1. From the Amazon Q menu, choose **Manage Q Developer Pro Subscription**.
A browser window opens.
1. If prompted, sign in to the AWS Management Console using the AWS account that's linked to your personal account (Builder ID). You specified this AWS account when you upgraded your Builder ID to the Pro tier. For more information, see [Upgrading a personal account (Builder ID)](upgrade-to-pro.md#upgrade-builder-id).
The **Subscriptions** page in the Amazon Q Developer console appears.
1. In the **Builder ID users** section, choose **Unsubscribe**.
------
#### [ Command line ]
**To unsubscribe your Builder ID starting from the command line**
1. On a computer where Amazon Q for the command line is installed, open a terminal.
1. Make sure you're signed in with your personal account (Builder ID) by typing `q whoami` at the command line.
You should see a `Logged in with Builder ID` message.
1. Start a chat session by typing `q chat` at your terminal's prompt.
An interactive chat sessions opens.
1. Type **/subscribe --manage**.
The AWS Management Console launches in a browser window.
**Note**
If the AWS Management Console doesn't automatically launch, copy and paste the URL from the terminal into a browser window.
1. If prompted, sign in to the AWS Management Console using the AWS account that's linked to your personal account (Builder ID). You specified this AWS account when you upgraded your Builder ID to the Pro tier. For more information, see [Upgrading a personal account (Builder ID)](upgrade-to-pro.md#upgrade-builder-id).
The **Subscriptions** page in the Amazon Q Developer console appears.
1. In the **Builder ID users** section, choose **Unsubscribe**.
------
#### [ AWS Management Console ]
**To unsubscribe your Builder ID starting from the AWS Management Console**
1. Sign in to the AWS Management Console using the AWS account that's linked to your personal account (Builder ID). You specified this AWS account when you upgraded your Builder ID to the Pro tier. For more information, see [Upgrading a personal account (Builder ID)](upgrade-to-pro.md#upgrade-builder-id).
1. If you don't have a Kiro Profile, create one in the US East (N. Virginia) Region (IAD) by following the [Kiro onboarding quickstart](https://kiro.dev/docs/enterprise/getting-started/). If you have a Kiro Profile but not a Amazon Q Developer Profile, choose **Settings**, then under **Other applications**, choose **Enable**.
1. Switch to the Amazon Q Developer console in the US East (N. Virginia) Region (IAD).
1. Choose **Subscriptions**.
1. In the **Builder ID users** section, select the subscription and choose **Unsubscribe**.
------
## Unsubscribing IAM Identity Center workforce users
If you are the administrator of an AWS standalone account, an AWS management account, or an AWS member account, use the following procedure to unsubscribe IAM Identity Center workforce users from your account.
For more information about AWS management and member accounts, see [Managing AWS accounts in an organization with AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts.html).
Notes about unsubscribing users:
+ If you are an administrator of either a management or member account within an organization managed by [AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html), you can only unsubscribe users if your created their subscriptions.
+ If a user has been subscribed in both member and management accounts, both account administrators must unsubscribe the user from their respective accounts for the user to be fully unsubscribed.
+ If you are a management account administrator, you can view other accounts the user is subscribed in by choosing **View subscriptions from member accounts** on the **Settings** page of the Amazon Q Developer console. This allows you to coordinate with member account administrators for unsubscription. Alternatively, if you have the appropriate permissions, you can sign in as a member account administrator and unsubscribe the user directly. For more information about viewing member account subscriptions as a management account administrator, see [Viewing an aggregated list of Amazon Q Developer subscriptions](subscribe-visibility.md).
+ After unsubscribing users or groups, their subscriptions are marked as **Canceled**, and they can no longer access Amazon Q Developer features. (They can still use the [Free tier](q-tiers.md) though, provided they have not exceeded their Free tier limits.) The final monthly subscription fee is charged at the end of the current billing cycle for all users who had active subscriptions. You'll be charged for the full month; the fee won't be prorated.
**To unsubscribe a user or group you manage**
1. Sign in to the AWS Management Console using your AWS standalone, management, or member account.
1. Switch to the Amazon Q Developer console.
1. In the **Identity provider users and groups** section, choose the **Users** or **Groups** tab.
1. Choose the user or group you want to unsubscribe.
1. Choose **More actions**.
1. Choose **Unsubscribe**.
# Upgrading to Amazon Q Developer Pro
How you upgrade to the Pro tier from the Free tier depends on whether you're an end-user with a personal account (Builder ID) or whether you're an administrator of IAM Identity Center workforce users.
## Upgrading a personal account (Builder ID)
Read this section if you want to upgrade your personal account (Builder ID) from the Free tier to a Pro tier monthly subscription. For reasons why you might consider upgrading, see [Tiers of service](q-tiers.md), and [Limitations of Builder IDs](getting-started-builderid.md#builder-id-limitations).
You can upgrade starting from one of the following interfaces:
+ IDE
+ command line
**Before you begin**
+ Create an AWS account if you don't have one yet. This account will be linked to your Builder ID, and will be charged the monthly subscription fee. For more information about creating an account, see [Create an AWS account](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html) in the *AWS Account Management Reference Guide*.
**Note**
You cannot link multiple Builder IDs to a single AWS account. If you have multiple Builder IDs that you want to upgrade, create separate AWS accounts for each.
------
#### [ IDE ]
**To upgrade starting from the IDE**
1. Authenticate to Amazon Q in your IDE using your personal account (Builder ID). For more information, see [Installing the Amazon Q Developer extension or plugin in your IDE](q-in-IDE-setup.md).
1. In your IDE, do one of the following:
+ If you see a `Monthly request limit reached` message in the Amazon Q chat window, choose **Subscribe to Q Developer Pro**.
Or
+ From the Amazon Q menu, choose **Subscribe to Q Developer Pro**.
A browser window opens.
1. If prompted, sign in using your AWS account. You should have created this account previously, as described in **Before you begin**.
A **Review upgrade details for Q Developer Pro** page appears. The page shows your Builder ID, AWS account number, and subscription fee, among other information. For more information about the subscription fee, see [Subscription billing](tracking-across-org-cost-usage.md). The **Activation token** field shows a one-time token that links your AWS account with your Builder ID. This token is never used again.
1. Choose **Confirm upgrade**.
The **Subscriptions** page of the Amazon Q Developer console appears with an **Upgrade to Q Developer Pro successful** message at the top. You should see your user name listed in the **Builder ID users** section.
Your personal account (Builder ID) is now subscribed to the Pro tier.
1. (Optional) Return to the Amazon Q chat window in your IDE.
You should see a **Successfully subscribed to Amazon Q Developer Pro** message.
------
#### [ Command line ]
**To upgrade starting from the command line**
1. On a computer where Amazon Q for the command line is installed, open a terminal.
1. Make sure you're signed in with your personal account (Builder ID) by typing `q whoami` at the command line.
You should see a `Logged in with Builder ID` message.
1. Start a chat session by typing `q chat` at your terminal's prompt.
An interactive chat sessions opens.
1. Type **/subscribe**.
The AWS Management Console launches in a browser window.
**Note**
If the AWS Management Console doesn't automatically launch, copy and paste the URL from the terminal into a browser window.
1. If prompted, sign in using your AWS account. You should have created this account previously, as described in **Before you begin**.
A **Review upgrade details for Q Developer Pro** page appears. The page shows your Builder ID, AWS account number, and subscription fee, among other information. For more information about the subscription fee, see [Subscription billing](tracking-across-org-cost-usage.md). The **Activation token** field shows a one-time token that links your AWS account with your Builder ID. This token is never used again.
1. Choose **Confirm upgrade**.
The **Subscriptions** page of the Amazon Q Developer console appears with a **Upgrade to Q Developer Pro successful** message at the top. You should see your user name listed in the **Builder ID users** section.
Your personal account (Builder ID) is now subscribed to the Pro tier.
1. (Optional) Verify that you're subscribed by typing **/subscribe** at the Q CLI prompt. Amazon Q should indicate that you're already subscribed.
------
## Upgrading IAM Identity Center workforce users to the Pro tier
If you are the administrator of IAM Identity Center workforce users, you can upgrade these users to the Pro tier following the instructions in [Getting started with IAM Identity Center](getting-started-idc.md).
# Upgrade to Kiro
The Amazon Q Developer CLI has been rebranded to Kiro.
What does this rebrand mean for you?
+ **If you're a user with a personal account**: Optionally upgrade the Q CLI and Amazon Q extension in your IDE to Kiro to take advantage of all the updates that will only be available in Kiro going forward. On upgrade, your extension and Q CLI installation will be rebranded to Kiro, and you'll also get additional features.
+ **If you're an administrator of Amazon Q Developer Pro subscriptions**: Start using the **Kiro** console to manage your users' subscriptions. The Kiro console is a rebrand of the Amazon Q Developer console, with all the same functionality. Have your users upgrade their Amazon Q IDE extensions and CLI installations to Kiro to access the rebranded interface and receive additional features. After upgrading, all Amazon Q components will automatically update to their Kiro equivalents.
## Canceling Amazon Q Developer
After you upgrade to Kiro, the Amazon Q Developer console is no longer visible in the left navigation pane by default. To cancel your Amazon Q Developer subscription, you must first enable the Amazon Q Developer console, and then follow the unsubscribe instructions.
**Note**
The **Users & Groups** page under **Kiro** in the left navigation pane is only for managing Kiro subscriptions. To manage Amazon Q Developer subscriptions, you must enable the Amazon Q Developer console as described in the following procedure.
**To cancel Amazon Q Developer**
1. Open the Kiro console.
1. In the left navigation pane, choose **Settings**.
1. In the **Other applications** section, choose **Enable** to make Amazon Q Developer visible in the left navigation pane. An **Amazon Q Developer** section appears in the left navigation pane with links to the Dashboard, Subscriptions, Customizations, and Plugins pages.
1. In the left navigation pane, under **Amazon Q Developer**, choose **Subscriptions**, and then follow the instructions in [Unsubscribing from Amazon Q Developer Pro](q-admin-setup-unsubscribe.md) to cancel your subscription.
To learn about Kiro in the IDE and at the command line, and how to administer Kiro subscriptions in your enterprise, see the [Kiro Docs](https://kiro.dev/docs/).