Configuring Cross-CIDR Access for a Replica Set
API Description
This API is used to configure cross-CIDR access for a replica set instance.
Constraints
Only replica set instances are supported.
URI
|
Name |
Mandatory |
Type |
IN |
Description |
|---|---|---|---|---|
|
project_id |
Yes |
string |
path |
Explanation: Project ID of a tenant in a region. To obtain the project ID, see Obtaining a Project ID. Constraints: N/A Value range: N/A Default value: N/A |
|
instance_id |
Yes |
string |
path |
Explanation: Instance ID, which can be obtained by calling the API described in Querying Instances and Details. If you do not have an instance, call the API described in Creating a DB Instance to create one. Constraints: N/A Value range: N/A Default value: N/A |
Request Parameters
|
Name |
Mandatory |
Type |
IN |
Description |
|---|---|---|---|---|
|
X-Auth-Token |
Yes |
string |
header |
Definition User token obtained from IAM. For details, see Authentication. Constraints N/A Range N/A Default Value N/A |
|
Name |
Type |
Mandatory |
Description |
|---|---|---|---|
|
client_network_ranges |
Array of strings |
Yes |
Definition CIDR block where the client is located Constraints
NOTE:
Range N/A Default Value N/A |
Example Requests
Configuring access across CIDR blocks for a replica set instance
{
"client_network_ranges":["192.168.0.0/16"]
}
Response Parameters
None
SDK
Click Document Database Service DDS SDK to download the SDK or view the SDK document. To learn how to install and authenticate an SDK, read the Usage section.
Status Code
For more information, see Status Code.
Error Code
For more information, see Error Code.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot