Troubleshooting for GitLab Duo with Amazon Q
Note
GitLab Duo with Amazon Q is in preview release and is subject to change.
The following information can help you troubleshoot common issues you might come across for GitLab Duo with Amazon Q.
Why did authentication stop working after I changed the instance URL?
Authentication breaks when you change the instance URL. When you change an instance URL, you need to offboard and then reonboard to Amazon Q with your GitLab instance that has the new instance URL. For more information, see Getting started with GitLab Duo with Amazon Q.
How do I make sure if my IAM role is able to access my GitLab instance?
After providing your IAM role ARN when configuring GitLab Duo with Amazon Q and save the changes, you can confirm that the application is being created in the Amazon CloudWatch console log. For more information, see What is Amazon CloudWatch?
After the application is created, you can see in the GitLab configuration page that the settings have been saved. In the navigation pane, choose Applications to confirm that the Amazon Q OAuth application is created. You can then add an Amazon Q user that was dynamically created.
Why is a code transformation job paused?
You might see jobs queued up and waiting to be processed when jobs appear to be paused. That is because one code transformation jobs occurs per instance.
