Updated on 2026-09-02 GMT+08:00

Uploading a Certificate

Function

This API is used to upload a certificate file to a Logstash cluster.

Calling Method

For details, see Calling APIs.

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/certs/upload

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Definition Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. Constraints N/A Range Project ID of an account. The value contains 32 characters, consisting of lowercase letters and digits. Default Value N/A
cluster_id	Yes	String	Definition ID of the target cluster. For details about how to obtain the cluster ID, see Obtaining the Cluster ID. Constraints N/A Range The value is a UUID containing 36 characters. Default Value N/A

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
bucket_name	Yes	String	Definition OBS bucket where the certificate file is stored. Constraints The storage class must be Standard. The region must be the same as the cluster region. Range 3 to 63 characters. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. Default Value N/A
certs_object	Yes	String	Definition Certificate file object name. Constraints The certificate file size cannot exceed 1 MB. Range The name must start with a letter, be 4 to 32 characters in length, and end with one of the following extensions: .cer, .crt, .rsa, .jks, .pem, .p10, .pfx, .p12, .csr, .der, or .keystore. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. Default Value N/A

Response Parameters

Status code: 200

Request succeeded.

None

Example Requests

Upload a certificate.

POST https://{Endpoint}/v1.0/{project_id}/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/certs/upload

{
  "bucket_name" : "test-bucket",
  "certs_object" : "test/cert.cer"
}

Example Responses

None

Status Codes

Status Code	Description
200	Request succeeded.
400	Invalid request. Modify the request instead of retrying.
409	The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.
412	The server does not meet one of the requirements that the requester puts on the request.

Error Codes

See Error Codes.

Parent topic: Logstash