You can call the GetDbProxyInstanceSsl operation to query the SSL encryption settings of the dedicated proxy endpoint of an ApsaraDB RDS instance.
Operation Description
ApsaraDB RDS provides the dedicated proxy feature. You can configure SSL encryption for the dedicated proxy endpoint of an instance. This allows you to ensure the data security of the instance. For more information about the dedicated proxy feature, see Dedicated proxy.
Before you call this operation, make sure that the following requirements are met:
The dedicated proxy feature must be enabled for the instance.
The minor engine version that the dedicated proxies of the instance run must be 1.12.8 or later.
The minor engine version of the instance must be 20200831 or later, and the instance must run the following MySQL versions and RDS editions:
- MySQL 8.0 on RDS High-availability Edition with local SSDs
- MySQL 5.7 on RDS High-availability Edition with local SSDs
- MySQL 5.6 on RDS High-availability Edition with local SSDs
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
rds:GetDbProxyInstanceSsl | WRITE |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | No | The region ID of the instance. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
DbInstanceId | string | Yes | The ID of the instance. You can call the DescribeDBInstances operation to query the ID of the instance. | rm-t4n3axxxxx |
DBProxyEngineType | string | No | An internal parameter. You do not need to specify this parameter. | normal |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "D330E60C-8AAA-4D63-8F64-5B78F4692F98",
"DbProxyCertListItems": {
"DbProxyCertListItems": [
{
"DbInstanceName": "rm-t4n3axxxxx",
"EndpointName": "buxxxxxxx",
"EndpointType": "RWSplit",
"SslExpiredTime": "2021-12-16T08:43:20Z",
"CertCommonName": "test1234.rwlb.rds.aliyuncs.com"
}
]
}
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | InvalidVpcInstanceId | The specified VPC instance ID is invalid. | - |
400 | InvalidDBInstanceName | Specified parameter DBInstanceName is not valid. | The value of the DBInstanceName parameter is invalid. Check that the value of this parameter is not null or an empty string. |
403 | IncorrectDBInstanceType | The current database instance type does not support the operation. | - |
404 | InvalidDBInstance.NotFound | The specified instance does not exist or is not supported. | The RDS instance cannot be found. Check the ID or name of the RDS instance. |
404 | Endpoint.NotFound | The specified endpoint is not found. | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2022-06-23 | API Description Update,The error codes of the API operation change. | |||||||||||||
| ||||||||||||||
2022-06-08 | The error codes of the API operation change.,The input parameters of the API operation change. | |||||||||||||
|