This document provides examples about how to grant a user permissions to view and use specific resources in the TencentDB console by using a CAM policy.
Full access policy for TencentDB
To grant a user permissions to create and manage TencentDB instances, you can implement the QcloudCDBFullAccess policy for the user.
Log in to the CAM console, select Policies on the left sidebar, and search QcloudCDBFullAccess in the upper right corner.
The policy syntax is as follows:
{
"statement":[
{
"action":[
"cdb:*"
],
"effect":"allow",
"resource":"*"
},
{
"action":[
"vpc:*"
],
"effect":"allow",
"resource":"*"
},
{
"action":[
"cvm:*"
],
"effect":"allow",
"resource":"qcs::cvm:::sg/*"
},
{
"action":[
"cos:*"
],
"effect":"allow",
"resource":"*"
},
{
"action":[
"monitor:*",
"cam:ListUsersForGroup",
"cam:ListGroups",
"cam:GetGroup"
],
"effect":"allow",
"resource":"*"
},
{
"action":[
"kms:CreateKey",
"kms:GenerateDataKey",
"kms:Decrypt",
"kms:ListKey"
],
"effect":"allow",
"resource":"*"
}
],
"version":"2.0"
}
The above policy achieves its goal by allowing the user to separately authorize the use of TencentDB, VPC, security group, COS, KMS, and all resources available in the monitor with the CAM policy.
Read-only permission policy for TencentDB
To grant a user permission to view TencentDB instances but not create, delete, or modify them, you can implement the policy named QcloudCDBInnerReadOnlyAccess for the user.
Note:
We recommend that you configure the read-only policy for TencentDB.
Log in to the CAM console, select Policies on the left sidebar, click Service Type in the policy list and select TencentDB for MySQL in the drop-down list, and then you can see this policy in the results.
The policy syntax is as follows:
{
"statement":[
{
"action":[
"cdb:Describe*"
],
"effect":"allow",
"resource":"*"
}
],
"version":"2.0"
}
Read-only permission policy for TencentDB-related resources
To grant a user permissions to view TencentDB instances and related resources (VPC, security groups, COS, and Cloud Monitor) but not create, delete, or modify them, you can implement the QcloudCDBReadOnlyAccess policy for the user.
Log in to the CAM console, select Policies on the left sidebar, click Service Type in the policy list and select TencentDB for MySQL in the drop-down list, and then you can see this policy in the results.
The policy syntax is as follows:
{
"statement":[
{
"action":[
"cdb:Describe*"
],
"effect":"allow",
"resource":"*"
},
{
"action":[
"monitor:Describe*",
"monitor:Get*",
"cam:ListUsersForGroup",
"cam:ListGroups",
"cam:GetGroup"
],
"effect":"allow",
"resource":"*"
}
],
"version":"2.0"
}
The above policy achieves its goal by allowing the user to separately authorize the use of the following operations with the CAM policy.
All operations in TencentDB that begin with "Describe".
All operations in VPC that begin with "Describe", "Inquiry", or "Get".
All operations in security groups that begin with "DescribeSecurityGroup".
All operations in COS that begin with "List", "Get", and "Head" as well as the "OptionsObject" operation.
All operations in the monitor.
Policy for granting a user permissions to use APIs not at the resource level
To grant a user permissions to use only APIs not at the resource level, you can implement the QcloudCDBProjectToUser policy for the user.
Log in to the CAM console, select Policies on the left sidebar, click Service Type in the policy list and select TencentDB for MySQL in the drop-down list, and then you can see this policy in the results.
The policy syntax is as follows:
{
"version":"2.0",
"statement":[
{
"action":[
"cdb:BalanceRoGroupLoad",
"cdb:CancelBatchOperation",
"cdb:CreateBatchJobFiles",
"cdb:CreateDBInstance",
"cdb:CreateDBInstanceHour",
"cdb:CreateMonitorTemplate",
"cdb:CreateParamTemplate",
"cdb:DeleteBatchJobFiles",
"cdb:DeleteMonitorTemplate",
"cdb:DeleteParamTemplate",
"cdb:DescribeBatchJobFileContent",
"cdb:DescribeBatchJobFiles",
"cdb:DescribeBatchJobInfo",
"cdb:DescribeProjectSecurityGroups",
"cdb:DescribeDefaultParams",
"cdb:DescribeMonitorTemplate",
"cdb:DescribeParamTemplateInfo",
"cdb:DescribeParamTemplates",
"cdb:DescribeRequestResult",
"cdb:DescribeRoGroupInfo",
"cdb:DescribeRoMinScale",
"cdb:DescribeTasks",
"cdb:DescribeUploadedFiles",
"cdb:ModifyMonitorTemplate",
"cdb:ModifyParamTemplate",
"cdb:ModifyRoGroupInfo",
"cdb:ModifyRoGroupVipVport",
"cdb:StopDBImportJob",
"cdb:UploadSqlFiles"
],
"effect":"allow",
"resource":"*"
}
]
}
Policy for granting a user permissions to manipulate a specific TencentDB instance
To grant a user the permission to manipulate a specific TencentDB instance, associate the following policy with the user. For example, the policy below allows the user to manipulate the TencentDB instance "dcdb-xxx" in Guangzhou region.
Policy for granting a user permissions to manipulate TencentDB instances in batches
To grant a user permissions to manipulate TencentDB instances in batches, associate the following policy with the user. For example, the policy below allows the user to manipulate the TencentDB instances "cdb-xxx" and "cdb-yyy" in Guangzhou region and "cdb-zzz" in Beijing region.
Policy for granting a user permissions to manipulate TencentDB instances in a specific region
To grant a user permissions to manipulate TencentDB instances in a specific region, associate the following policy with the user. This policy authorizes the user to operate TencentDB instances in Guangzhou region.
{
"version":"2.0",
"statement":[
{
"action":"cdb:*",
"resource":"qcs::cdb:ap-guangzhou::*",
"effect":"allow"
}
]
}
Custom policy
If preset policies cannot meet your requirements, you can create custom policies as shown below. If permissions are granted by resources, for a TencentDB API operation that does not support authorization at the resource level, you can still authorize a user to perform it, but you must specify * as the resource element in the policy statement.
The syntax of custom policies is as follows:
{
"version":"2.0",
"statement":[
{
"action":[
"Action"
],
"resource":"Resource",
"effect":"Effect"
}
]
}
Replace "Action" with the operation to be allowed or denied.
Replace "Resource" with the resources that you want to authorize the user to manipulate.
Yes
No
Was this page helpful?