All Products
Search

This Product

    Server Load Balancer:AssociateAdditionalCertificatesWithListener

    Document Center

    Server Load Balancer:AssociateAdditionalCertificatesWithListener

    Last Updated:Mar 13, 2024

    Associates additional certificates with a listener that uses SSL over TCP.

    Operation description

    AssociateAdditionalCertificatesWithListener is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListListenerCertificates operation to query the status of the task:

    • If the listener is in the Associating state, the additional certificates are being associated.
    • If the listener is in the Associated state, the additional certificates are associated.

    Debugging

    OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

    Authorization information

    There is currently no authorization information disclosed in the API.

    Request parameters

    ParameterTypeRequiredDescriptionExample
    AdditionalCertificateIdsarrayYes

    The additional certificates. You can associate up to 15 additional certificates with a listener in each request.

    stringYes

    The additional certificates. You can associate up to 15 additional certificates with a listener in each request.

    		12315790343_166f8204689_1714763408_70998****
    ListenerIdstringYes

    The listener ID. You must specify the ID of a listener that uses SSL over TCP.

    		lsr-bp1bpn0kn908w4nbw****
    DryRunbooleanNo

    Specifies whether to perform a dry run, without performing the actual request. Valid values:

    • true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and service limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the DryRunOperation error code is returned.
    • false(default): performs a dry run and performs the actual request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.
    		true
    ClientTokenstringNo

    The client token that is used to ensure the idempotence of the request.

    You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters.

    Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.
    		123e4567-e89b-12d3-a456-426655440000
    RegionIdstringNo

    The region ID of the Network Load Balancer (NLB) instance.

    You can call the DescribeRegions operation to query the most recent region list.

    		cn-hangzhou

    Response parameters

    ParameterTypeDescriptionExample
    object

    The operation to add additional certificates to a listener that uses SSL over TCP.

    RequestIdstring

    The request ID.

    		365F4154-92F6-4AE4-93F8-7FF34B540710
    JobIdstring

    The ID of the asynchronous task.

    		72dcd26b-f12d-4c27-b3af-18f6aed5****

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "365F4154-92F6-4AE4-93F8-7FF34B540710",
  "JobId": "72dcd26b-f12d-4c27-b3af-18f6aed5****"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400SystemBusySystem is busy, please try again later.-
    400OperationDenied.%sThe operation is not allowed because of %s.-
    400OperationFailed.%sThe operation failed because of %s.Failed to call the API operation due to %.
    400IncorrectStatus.%sThe status of %s [%s] is incorrect.-
    400ResourceAlreadyAssociated.%sThe specified resource of %s is already associated.-
    404ResourceNotFound.%sThe specified resource of %s is not found.-
    404ResourceNotFound.listenerThe specified resource %s is not found.-

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    2024-02-29The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
      delete Error Codes: 404
      Added Error Codes: 403
    2024-02-22The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 400 change
      delete Error Codes: 404
    2024-01-29The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 400 change
      delete Error Codes: 404
    2023-12-18The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 400 change
      delete Error Codes: 404
    2023-09-26The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 404 change
      delete Error Codes: 400
    2023-08-22The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 400 change
      Error Codes 404 change