Enabling Kibana Public Access
Function
This API is used to enable public network access to Kibana.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/publickibana/open
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        project_id  | 
      
        Yes  | 
      
        String  | 
      
        Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.  | 
     
| 
        cluster_id  | 
      
        Yes  | 
      
        String  | 
      
        ID of the cluster whose Kibana public access you want to enable.  | 
     
Request Parameters
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        eipSize  | 
      
        Yes  | 
      
        Integer  | 
      
        Bandwidth. Unit: Mbit/s  | 
     
| 
        elbWhiteList  | 
      
        Yes  | 
      
        ELB whitelist.  | 
     
Response Parameters
None
Example Requests
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/publickibana/open
{
  "eipSize" : 5,
  "elbWhiteList" : {
    "enableWhiteList" : true,
    "whiteList" : "192.168.0.xx"
  },
  "isAutoPay" : 1
}
 Example Responses
None
Status Codes
| 
        Status Code  | 
      
        Description  | 
     
|---|---|
| 
        200  | 
      
        Request succeeded.  | 
     
| 
        400  | 
      
        Invalid request. Modify the request before retry.  | 
     
| 
        409  | 
      
        The request could not be completed due to a conflict with the current state of the resource. The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.  | 
     
| 
        412  | 
      
        The server did not meet one of the preconditions contained in the request.  | 
     
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.