Before you begin
Before you start creating your Amazon Q Business sample application, note the following information.
Creating an application
The following are important things to consider before you begin creating your Amazon Q Business application:
-
You must connect an Amazon Q Business application environment to an IAM Identity Center instance to manage end user access to your application. You can do this in the following two ways:
-
You can create and configure an IAM Identity Center instance and add users and groups to it. Then, when you create an Amazon Q Business application, you can assign the users and groups you’ve created in IAM Identity Center to your Amazon Q Business application.
-
If you don’t have an IAM Identity Center instance configured, or want to create a sample Amazon Q Business application environment to test a use case, you can create an IAM Identity Center instance from the Amazon Q Business console. An IAM Identity Center instance created from the Amazon Q Business console during the application environment creation process has limited functionality. You can only add users to an IAM Identity Center instance created from the Amazon Q Business and not groups.
-
-
To minimize latency, we recommend using an IAM Identity Center instance created in the same region as your Amazon Q Business application. However, you can also use an IAM Identity Center instance created in an AWS region not yet supported by Amazon Q Business. For more information, see Creating a cross-region IAM Identity Center instance.
Important
When you create a cross-region IAM Identity Center and Amazon Q Business integration, any Amazon Q Business indices associated with your application are billed in the Amazon Q Business region they're created in. User subscriptions for an Amazon Q Business application using a cross-region IAM Identity Center integration are billed in the region the IAM Identity Center instance is created in. For more information on pricing, see Amazon Q Business Pricing
. -
Amazon Q Business supports cross-region IAM Identity Center and Amazon Q Business integrations only for organization level instances. For more information on IAM Identity Center instances and their use cases, see see Understanding types of IAM Identity Center instances.
-
During the application environment creation process, Amazon Q Business detects and customizes your application environment creation experience based on your level of integration with IAM Identity Center. Specifically, whether:
-
You haven’t yet created an IAM Identity Center instance.
-
You have integrated with IAM Identity Center and created an account level instance.
-
You have integrated with IAM Identity Center and created an organization level instance.
-
You have integrated with IAM Identity Center and have created both an account level and organization level instance.
-
Your IAM Identity Center instance is in an AWS region not yet supported by Amazon Q Business.
Your path through creating an application environment will depend on your specific IAM Identity Center setup. For more information on different IAM Identity Center instances, see Configure an IAM Identity Center instance.
-
-
After creating an application environment and adding at least one subscribed user to it, you can test it by using the Customize web experience mode.
-
Your IAM Identity Center instance must be created in the same region as your Amazon Q Business application.
-
When your application environment is successfully created, Amazon Q Business generates a web experience login URL. Any user you've added to your sample application environment and enabled in IAM Identity Center can log in and chat with your Amazon Q Business application.
Adding users and groups
The following are important things to consider before you begin adding users and groups to your Amazon Q Business application:
-
You must add, assign, and subscribe at least one user to your Amazon Q Business application environment for it to work as intended.
-
You can add users and groups to your Amazon Q Business application in the following two ways:
-
You can create and configure a user or group in IAM Identity Center. Then, you can assign the users and groups you created in IAM Identity Center to your Amazon Q Business application environment during the application environment creation process.
-
You can create an IAM Identity Center instance from the Amazon Q Business console during the application environment creation process and add and assign a user to it. You can’t create groups from the Amazon Q Business console. You can only assign existing groups in IAM Identity Center to your Amazon Q Business application.
-
-
When you add a new user to IAM Identity Center from the Amazon Q Business console, you need to make sure that the user is enabled in your IAM Identity Center instance and their email ID is verified before they can log in to your Amazon Q Business web experience to chat.
-
When you add a new user, the user will receive a notification to their email asking them to accept your invitation to IAM Identity Center. You might also have to go to the IAM Identity Center console and send them an email verification request. Your user will have to verify their email and set their password before they can successfully log in to the web experience URL for your Amazon Q Business application. For more information, see Manage identities in IAM Identity Center.
-
If you add a user to a group in IAM Identity Center and have given that group access to your application, it can take up to 24 hours for the change to take effect and for the user to be able to access your Amazon Q Business application.
User subscriptions
The following are important things to consider before you begin adding subscriptions to users and groups in your Amazon Q Business application:
-
Subscription activation is tied to a user's group membership. When a user is added to a group that has a subscription, they become entitled to access that application.
-
When you create a cross-region IAM Identity Center and Amazon Q Business integration, any Amazon Q Business indices associated with your application are billed in the Amazon Q Business region they're created in. User subscriptions for an Amazon Q Business application using a cross-region IAM Identity Center integration are billed in the region the IAM Identity Center instance is created in. For more information on pricing, see Amazon Q Business Pricing
. -
After you add users or groups to an application, you must choose the Amazon Q Business subscription tier for each user or group. Users or groups must be given a subscription tier before they can access and use your Amazon Q Business application. For information on what's included in the tiers of user subscriptions, see User subscription tiers.
-
If a user is later removed from that group, their subscription will be revoked at the end of the current billing cycle (typically the end of the month). They will no longer be able to access the application environment after that point.
-
User subscriptions are prorated when created or upgraded based on the number of days left in the calendar month. Any cancellations or downgrades are not prorated and apply starting in the next calendar month. The charges for user subscription starts only after first use by the user.
-
If a user has individual subscriptions to multiple applications across different accounts, removing their group membership will only impact the subscription tied to that specific group. Their other individual subscriptions will remain active.
-
AWS will deduplicate subscriptions across all Amazon Q Business applications and Amazon QuickSight accounts and charge each user only once for their highest subscription level. Note that deduplication will apply only if the Amazon Q Business applications and Amazon QuickSight accounts share the same IAM Identity Center.
-
When you remove a user or group from the Amazon Q Business application, they still exist in IAM Identity Center. You can still search for and select the user or group to add to an application environment in future.
-
You must confirm and save your user subscription settings, otherwise you are charged based on your unsaved user subscriptions.
-
Administrators should monitor group membership changes and make appropriate adjustments to subscriptions to avoid over-charging users who no longer require access.