Updated on 2024-10-17 GMT+08:00

Uploading a Certificate

Function

This API is used to upload a certificate.

Debugging

You can debug this API through automatic authentication in API Explorer.

URI

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

Table 1 Path Parameters

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 target cluster

Request Parameters

Table 2 Request body parameters

Parameter

Mandatory

Type

Description

bucket_name

Yes

String

OBS bucket where a certificate is stored. The bucket type must be Standard or Infrequent Access. Archive is not supported.

certs_object

Yes

String

Certificate. The certificate size cannot exceed 1 MB. The certificate name contains 4 to 32 characters, must start with a letter, and end with .cer, .crt, .rsa, .jks, .pem, .p10, .pfx, .p12, .csr, .der, or .keystore. The value can contain letters, digits, hyphens (-), underscores (_), and dots (.). Other special characters are not allowed.

Response Parameters

None

Example Requests

Upload a certificate.

POST /v1.0/6204a5bd270343b5885144cf9c8c158d/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.