GitLabDuoWithAmazonQPermissionsPolicy
Summary
This managed policy grants permission to connect with Amazon Q and utilize the features in the GitLab Duo with Amazon Q integration.
Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.
Identity
- ARN
arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicy- Default version
- v3
- Created
- Last edited
- Services
- q
Control-plane actions (12)
By access level: 1 List, 2 Read, 9 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Q | 12 of 54 | 1 List, 2 Read, 9 Write; 3 restricted, 0 conditional | q:CreateAuthGrant, q:CreateOAuthAppConnection, q:CreatePlugin, q:DeleteOAuthAppConnection, q:DeletePlugin, q:GenerateCodeRecommendations, q:GetPlugin, q:ListPlugins, q:SendEvent, q:SendMessage, q:UpdateAuthGrant, q:VerifyOAuthAppConnection |
Q: 12 actions
- q:CreateAuthGrant (Write)
- q:CreateOAuthAppConnection (Write)
- q:CreatePlugin (Write)
- q:DeleteOAuthAppConnection (Write)
- q:DeletePlugin (Write)
- q:GenerateCodeRecommendations (Read)
- q:GetPlugin (Read)
- q:ListPlugins (List)
- q:SendEvent (Write)
- q:SendMessage (Write)
- q:UpdateAuthGrant (Write)
- q:VerifyOAuthAppConnection (Write)
Data-plane actions (0)
By access level: none.
This policy grants no actions in this plane.
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: mixed.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants 9 write, tagging or permissions-management actions, short of full control of any service.
Guidance
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Related policies
Same service
- AIOpsOperatorAccess
- AmazonQDeveloperAccess
- AmazonQFullAccess
- AmazonSageMakerCanvasSMDataScienceAssistantAccess
- AWSManagementConsoleBasicUserAccess
- AWSMarketplaceSellerProductsFullAccess
- AWSPartnerCentralChannelManagement
- AWSPartnerCentralMarketingManagement
Same domain
Frequently asked questions
Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "GitLabDuoUsagePermissions",
"Effect": "Allow",
"Action": [
"q:SendEvent",
"q:CreateAuthGrant",
"q:UpdateAuthGrant",
"q:GenerateCodeRecommendations",
"q:SendMessage",
"q:ListPlugins",
"q:VerifyOAuthAppConnection"
],
"Resource": "*"
},
{
"Sid": "GitLabDuoManagementPermissions",
"Effect": "Allow",
"Action": [
"q:CreateOAuthAppConnection",
"q:DeleteOAuthAppConnection"
],
"Resource": "*"
},
{
"Sid": "GitLabDuoPluginPermissions",
"Effect": "Allow",
"Action": [
"q:CreatePlugin",
"q:DeletePlugin",
"q:GetPlugin"
],
"Resource": "arn:aws:qdeveloper:*:*:plugin/GitLabDuoWithAmazonQ/*"
}
]
}
Version history
Current version v3, edited by AWS on 2026-02-12. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicy
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicy
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicyCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicyTerraform
resource "aws_iam_role_policy_attachment" "gitlabduowithamazonqpermissionspolicy" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/GitLabDuoWithAmazonQPermissionsPolicy"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("GitLabDuoWithAmazonQPermissionsPolicy"),
);Sources
Pending editorial review. No editorial sources are listed yet.