All Products
Search

This Product

    Server Load Balancer:EnableLoadBalancerIpv6Internet

    Document Center

    Server Load Balancer:EnableLoadBalancerIpv6Internet

    Last Updated:Jun 18, 2024

    Changes the type of the IPv6 address that is used by a dual-stack Application Load Balancer (ALB) instance from private to public.

    Operation description

    Prerequisites

    An ALB instance is created and IPv4/IPv6 dual stack is enabled for the instance. You can call the CreateLoadBalancer operation and set AddressIpVersion to DualStack to create a dual-stack ALB instance.

    Note If you set AddressIpVersion to DualStack:

    • If you set AddressType to Internet, the ALB instance uses a public IPv4 IP address and a private IPv6 address.

    • If you set AddressType to Intranet, the ALB instance uses a private IPv4 IP address and a private IPv6 address.

    Description

    • After the EnableLoadBalancerIpv6Internet operation is called, the value of Ipv6AddressType is changed to Internet and the type of the IPv6 address of the ALB instance is changed from private to public. If you upgrade the instance or the instance scales elastic network interfaces (ENIs) along with workloads, public IPv6 addresses are automatically enabled for the instance and the new ENIs. You can call the GetLoadBalancerAttribute operation to query the value of Ipv6AddressType.

    • EnableLoadBalancerIpv6Internet 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 GetLoadBalancerAttribute operation to query the status of the task.

      • If the ALB instance is in the Configuring state, the network type of the IPv6 address that is used by the ALB instance is being changed.
      • If the ALB instance is in the Active state, the network type of the IPv6 address that is used by the ALB instance is changed.

    Debugging

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

    Authorization information

    The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

    • Operation: the value that you can use in the Action element to specify the operation on a resource.
    • Access level: the access level of each operation. The levels are read, write, and list.
    • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
      • The required resource types are displayed in bold characters.
      • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
    • Condition Key: the condition key that is defined by the cloud service.
    • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
    OperationAccess levelResource typeCondition keyAssociated operation
    alb:EnableLoadBalancerIpv6InternetWrite
    • LoadBalancer
      acs:alb:{#regionId}:{#accountId}:loadbalancer/{#LoadBalancerId}
    • alb:AddressType
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    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.
    		5A2CFF0E-5718-45B5-9D4D-70B3FF3898
    DryRunbooleanNo

    Specifies whether to perform only 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.
    		false
    LoadBalancerIdstringYes

    The ALB instance ID.

    		alb-o2cvudgo6rlqz7****

    Response parameters

    ParameterTypeDescriptionExample
    object

    Schema of Response

    RequestIdstring

    The request ID.

    		BB920797-D70E-567F-8098-55A861DD7912
    JobIdstring

    The asynchronous task ID.

    		4a6e3ad4-ef08-4ab1-b332-fa621cfe****

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "BB920797-D70E-567F-8098-55A861DD7912",
  "JobId": "4a6e3ad4-ef08-4ab1-b332-fa621cfe****"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400IncorrectStatus.LoadBalancerThe status of %s [%s] is incorrect.The status of %s [%s] is incorrect.
    400IncorrectBusinessStatus.LoadBalancerThe business status of %s [%s] is incorrect.-
    400OperationDenied.NonDualStackInstanceThe operation is not allowed because of %s.-
    400OperationDenied.Ipv6InternetInstanceThe operation is not allowed because of %s.-
    404ResourceNotFound.LoadBalancerThe specified resource %s is not found.The specified resource %s is not found.

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

    Change history

    Change timeSummary of changesOperation
    2024-01-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