ContextQMD
Back to Gitlabhq

GitLab Duo with Amazon Q

doc/user/duo_amazon_q/_index.md

19.2.07.7 KB
Original Source

{{< details >}}

  • Tier: Ultimate
  • Add-on: GitLab Duo with Amazon Q
  • Offering: GitLab Self-Managed

{{< /details >}}

{{< history >}}

  • Introduced as beta in GitLab 17.7 with a feature flag named amazon_q_integration. Disabled by default.
  • Feature flag amazon_q_integration removed in GitLab 17.8.
  • Generally available with additional GitLab Duo feature support in GitLab 17.11.

{{< /history >}}

[!note] GitLab Duo with Amazon Q cannot be combined with other GitLab Duo add-ons.

At re:Invent 2024, Amazon announced the GitLab Duo with Amazon Q integration. With this integration, you can automate tasks and increase productivity.

GitLab Duo with Amazon Q:

For a click-through demo, see the GitLab Duo with Amazon Q Product Tour.

<!-- Demo published on 2025-04-23 -->

To get a subscription for GitLab Duo with Amazon Q, contact your Account Executive.

Alternatively, to request a trial, fill out this form.

Set up GitLab Duo with Amazon Q

When you have a GitLab Duo with Amazon Q subscription and GitLab 17.11 or later, you can set up GitLab Duo with Amazon Q on your instance.

Use GitLab Duo with Amazon Q in an issue

To invoke GitLab Duo with Amazon Q for an issue, you will use quick actions.

Turn an idea into a merge request

Turn an idea in an issue into a merge request that contains the proposed implementation.

Amazon Q uses the issue title and description, along with project context, to create a merge request with code to address the issue.

From the issue description

  1. Create a new issue, or open an existing issue and in the upper-right corner, select Edit.
  2. In the description box, type /q dev.
  3. Select Save changes.

From a comment

  1. In the issue, in a comment, type /q dev.
  2. Select Comment.

Upgrade Java

Amazon Q can analyze Java 8 or 11 code and determine the necessary Java changes to update the code to Java 17.

View a walkthrough.

Prerequisites:

To upgrade Java:

  1. Create an issue.
  2. In the issue title and description, explain that you want to upgrade Java. You do not need to enter version details. Amazon Q can determine the version.
  3. Save the issue. Then, in a comment, type /q transform.
  4. Select Comment.

A CI/CD job starts. A comment is displayed with the details and a link to the job.

  • If the job is successful, a merge request with the code changes needed for the upgrade is created.
  • If the job fails, a comment provides details about potential fixes.

Use GitLab Duo with Amazon Q in a merge request

To invoke GitLab Duo with Amazon Q for a merge request, you will use quick actions.

Review a merge request

Amazon Q can analyze your merge request and suggest improvements to your code. It can find things like security issues, quality issues, inefficiencies, and other errors.

You can have Amazon Q review automatically when you open or reopen a merge request, or you can manually start a review.

To manually start:

  1. Open your merge request.
  2. On the Overview tab, in a comment, type /q review.
  3. Select Comment.

Amazon Q performs a review of the merge request changes and displays the results in comments.

Make code changes based on feedback

Amazon Q can make code changes based on reviewer feedback.

  1. Open a merge request that has reviewer feedback.
  2. On the Overview tab, go to the comment you want to address.
  3. Below the comment, in the Reply box, type /q dev.
  4. Select Add comment now.

Amazon Q proposes changes to the merge request based on the reviewer's comments and feedback.

Generate unit tests

Generate new unit tests for your code using Amazon Q.

From an issue

  1. Create an issue.
  2. Use one of the following options to request that tests be generated for your code:
    • In the issue description, describe your request and select Save changes.
    • In a comment, type /q dev and select Comment.

Amazon Q creates a merge request with the suggested tests.

From a merge request

  1. Open your merge request.
  2. On the Changes tab, leave an inline comment where you want to add tests. Include as much detail as possible in your feedback, such as file name, class name and line number.
  3. In the comment, type /q dev on a new line and select Add comment now.

Amazon Q updates the merge request with the suggested tests.

Authentication and authorization

{{< history >}}

{{< /history >}}

GitLab Duo with Amazon Q uses a composite identity to authenticate requests.

[!note] Support for a composite identity in other areas of the product is proposed in issue 511373.

The token that authenticates requests is a composite of two identities:

  • The primary author, which is the Amazon Q service account. This service account is instance-wide and has the Developer role on the project where the Amazon Q quick action was used. The service account is the owner of the token.
  • The secondary author, which is the human user who submitted the quick action. This user's id is included in the scopes of the token.

This composite identity ensures that any activities authored by Amazon Q are correctly attributed to the Amazon Q service account. At the same time, the composite identity ensures that there is no privilege escalation for the human user.

This dynamic scope is checked during the authorization of the API request. When authorization is requested, GitLab validates that both the service account and the user who originated the quick action have sufficient permissions.

mermaid
flowchart TD
    accTitle: Authentication flow for GitLab Duo
    accDescr: API requests are checked against user permissions first, then service account permissions, with access denied if either check fails.

    A[API Request] --> B{Human user has access?}
    B -->|No| D[Access denied]
    B -->|Yes| C{Service account has access?}
    C -->|No| D
    C -->|Yes| E[API request succeeds]