Applies for a direct connection endpoint for an ApsaraDB Tair (Redis® OSS-Compatible) database cluster instance.
Operation description
Clients can use the direct connection endpoint to bypass the proxy and connect to the cluster instance in the same way as they connect to a native Redis cluster. This reduces link overhead and further improves the response speed of the ApsaraDB Tair (Redis® OSS-Compatible) database service.
The instance for which you invoke this operation must meet the following conditions:
The instance uses the cluster architecture.
The deployment pattern is classic.
The network type of the instance is VPC. If the instance is connected to the classic network, you can invoke the SwitchNetwork operation to switch the network type to VPC.
The Secure Sockets Layer (SSL) encryption feature is disabled for the instance. If the Secure Sockets Layer (SSL) encryption feature is enabled, you can invoke the ModifyInstanceSSL operation for shutdown.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
kvstore:AllocateDirectConnection |
create |
*DBInstance
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| InstanceId |
string |
Yes |
The instance ID. Only cluster instances deployed in classic mode are supported. For instances deployed in classic mode, the value of the ComputingType parameter is Machine. You can call the DescribeInstances operation to query the ComputingType parameter. |
r-bp1zxszhcgatnx**** |
| ConnectionString |
string |
No |
The prefix of the direct connection endpoint. The prefix must be 8 to 40 characters in length and can contain lowercase letters and digits. It must start with a lowercase letter. Default value: the instance ID followed by |
redisdirect123 |
| Port |
string |
No |
The port number. Valid values: 1024 to 65535. Default value: 6379. |
6379 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| RequestId |
string |
The request ID. |
5D622714-AEDD-4609-9167-F5DDD3D1**** |
Examples
Success response
JSON format
{
"RequestId": "5D622714-AEDD-4609-9167-F5DDD3D1****"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | NetTypeExists | Specified net type already existed | |
| 400 | InvalidConnType | Specified DB instance conn type is not valid. | |
| 400 | TaskHasExist | The task already exists. | |
| 400 | ConnectionStringAlreadyExists | Specified connection string already exists in the Aliyun RDS. | |
| 400 | InvalidConnectionString.Format | Specified connection string is not valid. | The connection string is invalid. Use a different one. |
| 400 | DirectConnectionAlreadyExists | Specified instance direct connection already exists. | |
| 400 | InvalidVPCParamGroup | Specified vpc param group is not valid. | |
| 400 | InvalidConnectionString | ConnectionString is invalid, valid regex: ^\w+$ | The prefix of the endpoint is invalid. The prefix must start with a lowercase letter and can contain lowercase letters and digits. The prefix can be 8 to 40 characters in length. |
| 403 | UnsupportedEngineVersion | Current engine version does not support operations. | |
| 403 | IncorrectMinorVersion | Current engine minor version does not support operations. | |
| 403 | InstanceStatus.NotSupport | Instance status does not support this operation. | |
| 404 | InvalidDbInstanceId.NotFound | Specified instance does not exist. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.