cannot see AI agent under Amazon Q in Connect

If you're unable to see AI agents under Amazon Q in Connect console in the eu-west-2 region, there are a few things to check:

1. Ensure that Amazon Q in Connect has been properly enabled for your Amazon Connect instance. This is a prerequisite for accessing AI agent features.

2. Verify that you have the correct permissions. You need specific permissions to access and manage Amazon Q in Connect features, including AI agents. The "AmazonQFullAccess" policy should be applied to your user profile, but you might still need additional permissions specific to Amazon Q in Connect.

3. Navigate to the Amazon Connect admin website, and look for the "Amazon Q" section. Under this section, you should see "AI agents" as an option if everything is set up correctly.

4. If you're still encountering issues, you might need to check if there are any service control policies (SCPs) or other IAM policies restricting your access to these features.

5. Consider checking if you need to create AI prompts first before AI agents become visible, as AI agents typically work with AI prompts to customize the Amazon Q in Connect experience.

If after checking these items you still cannot see the AI agent section, you may need to contact AWS Support for further assistance, as there might be account-specific issues or regional configuration problems affecting your access.
Sources
Getting started with AWS connect AmazonQ | AWS re:Post
Personalize agent assistance with Amazon Q in Connect | AWS Contact Center
Create AI agents in Amazon Connect - Amazon Connect

If you're unable to see AI agents under Amazon Q in admin workspace, there are a few things to check:

• Ensure that Amazon Q in Connect has been properly enabled for your Amazon Connect instance. This is a prerequisite for accessing AI agent feature.

• Verify that the permissions for Amazon Q are checked in Security Profile attached to your user.

The most likely reasons you cannot find the AI agent in your Amazon Q in Connect console are a lack of proper IAM permissions or the need to enable Amazon Q for your instance first. To fix this, you should ensure your IAM user has the AmazonQ permissions, check that Amazon Q is enabled for your instance, and make sure you have created an AI prompt first, as the AI agent section may not appear until that is done.

https://docs.aws.amazon.com/connect/latest/adminguide/enable-q.html#:~:text=Configure%20SAML%20with%20IAM%20for,Set%20up%20your%20channels