All Products
Search
Document Center

ApsaraDB for ClickHouse:CheckClickhouseToRDS

Last Updated:Mar 05, 2025

Checks the connectivity between an ApsaraDB for ClickHouse cluster and an ApsaraDB RDS for MySQL instance.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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:
    • For mandatory resource types, indicate with a prefix of * .
    • 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.
OperationAccess levelResource typeCondition keyAssociated operation
clickhouse:CheckClickhouseToRDSget
*DBCluster
acs:clickhouse:{#regionId}:{#accountId}:dbcluster/{#DBClusterId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DbClusterIdstringYes

The ID of the ApsaraDB for ClickHouse cluster.

cc-2zeyy362b5sbm****
ClickhousePortlongNo

The port number of the ApsaraDB for ClickHouse cluster.

8123
CkUserNamestringYes

The account that is used to log on to the database in the ApsaraDB for ClickHouse cluster.

user1
CkPasswordstringYes

The password of the account that is used to log on to the database in the ApsaraDB for ClickHouse cluster.

123456Aa
RdsIdstringYes

The ID of the ApsaraDB RDS for MySQL instance.

rm-bp13v4bnwlu8j****
RdsPortlongNo

The port number of the ApsaraDB RDS for MySQL instance.

3306
RdsVpcIdstringYes

The ID of the VPC in which the ApsaraDB RDS for MySQL instance is deployed.

vpc-wz9mm0qka0winfl47****
RdsUserNamestringYes

The account that is used to log on to the database in the ApsaraDB RDS for MySQL instance.

user2
RdsPasswordstringYes

The password of the account that is used to log on to the database in the ApsaraDB RDS for MySQL instance.

123456Rr
RdsVpcUrlstringYes

The internal endpoint of the ApsaraDB RDS for MySQL instance.

rm-bp16t9h3999xb0a7****.mysql.rds.aliyuncs.com

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

A82758F8-E793-5610-BE11-0E46664305C2
Statusboolean

Indicates whether the ApsaraDB for ClickHouse cluster can be connected to the ApsaraDB RDS for MySQL instance.

  • true: The ApsaraDB for ClickHouse cluster can be connected to the ApsaraDB RDS for MySQL instance.
  • false: The ApsaraDB for ClickHouse cluster cannot be connected to the ApsaraDB RDS for MySQL instance.
false
ErrorCodestring
  • When the value true is returned for the Status parameter, the system does not return the ErrorCode parameter.
  • When the value false is returned for the Status parameter, the system returns for the ErrorCode parameter the reason why the ApsaraDB for ClickHouse cluster cannot be connected to the ApsaraDB RDS for MySQL instance.
NotSameVpc

Examples

Sample success responses

JSONformat

{
  "RequestId": "A82758F8-E793-5610-BE11-0E46664305C2",
  "Status": false,
  "ErrorCode": "NotSameVpc"
}

Error codes

HTTP status codeError codeError messageDescription
404InvalidDBCluster.NotFoundThe DBClusterId provided does not exist in our records.The DBClusterId provided does not exist in our records.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history