• Home
• com.aliyun
• alibabacloud-ecs20140526
• 5.0.29
• source code
• AsyncClient.java

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

com.aliyun.sdk.service.ecs20140526.AsyncClient Maven / Gradle / Ivy

// This file is auto-generated, don't edit it. Thanks.
package com.aliyun.sdk.service.ecs20140526;

import com.aliyun.core.utils.SdkAutoCloseable;
import com.aliyun.sdk.service.ecs20140526.models.*;
import darabonba.core.*;
import darabonba.core.async.*;
import darabonba.core.sync.*;

import java.util.concurrent.CompletableFuture;

public interface AsyncClient extends SdkAutoCloseable {

    static DefaultAsyncClientBuilder builder() {
        return new DefaultAsyncClientBuilder();
    }

    static AsyncClient create() {
        return builder().build();
    }

    /**
     * @param request the request parameters of AcceptInquiredSystemEvent  AcceptInquiredSystemEventRequest
     * @return AcceptInquiredSystemEventResponse
     */
    CompletableFuture acceptInquiredSystemEvent(AcceptInquiredSystemEventRequest request);

    /**
     * @deprecated OpenAPI ActivateRouterInterface is deprecated  * @param request  the request parameters of ActivateRouterInterface  ActivateRouterInterfaceRequest
     * @return ActivateRouterInterfaceResponse
     */
    @Deprecated
    CompletableFuture activateRouterInterface(ActivateRouterInterfaceRequest request);

    /**
     * @deprecated OpenAPI AddBandwidthPackageIps is deprecated  * @param request  the request parameters of AddBandwidthPackageIps  AddBandwidthPackageIpsRequest
     * @return AddBandwidthPackageIpsResponse
     */
    @Deprecated
    CompletableFuture addBandwidthPackageIps(AddBandwidthPackageIpsRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
Up to 20 tags can be added to each ECS resource.
     * 
Tag.N.Key must match Tag.N.Value based on the value of N.
     * 
If you add a tag that has the same key (Tag.N.Key) as an existing tag on the specified resource, the new tag value (Tag.N.Value) overwrites the original tag value.
     * 
     * 
     * @param request the request parameters of AddTags  AddTagsRequest
     * @return AddTagsResponse
     */
    CompletableFuture addTags(AddTagsRequest request);

    /**
     * description :
     * 
Before you create a dedicated host, you can call the DescribeAvailableResource operation to query the resources available in a specific region or zone.
     * We recommend that you understand the billing methods of resources before you create a dedicated host. You are charged for resources used by the created dedicated host. For more information, see Billing overview.
     * 

     * 
You can create up to 100 pay-as-you-go or subscription dedicated hosts at a time.
     * 
After a dedicated host is created, you can use the returned dedicated host ID as the value of a request parameter to call the DescribeDedicatedHosts operation to query the state of the dedicated host.
     * 
After you submit a request to create a dedicated host, an error is returned if a specific parameter is invalid or if the requested resources are insufficient. For more information about error causes, see the "Error codes" section of this topic.
     * 
After a dedicated host is created, you can call the ModifyInstanceDeployment operation to migrate ECS instances from a shared host to the dedicated host. You can also migrate ECS instances from another dedicated host to the created dedicated host.
     * 
     * 
     * @param request the request parameters of AllocateDedicatedHosts  AllocateDedicatedHostsRequest
     * @return AllocateDedicatedHostsResponse
     */
    CompletableFuture allocateDedicatedHosts(AllocateDedicatedHostsRequest request);

    /**
     * @deprecated OpenAPI AllocateEipAddress is deprecated, please use Vpc::2016-04-28::AllocateEipAddress instead.  * @description > This operation has been upgraded. We recommend that you do not use it. For information about the new version of this operation, see [AllocateEipAddress](https://help.aliyun.com/document_detail/120192.html).
     * 
     * @param request the request parameters of AllocateEipAddress  AllocateEipAddressRequest
     * @return AllocateEipAddressResponse
     */
    @Deprecated
    CompletableFuture allocateEipAddress(AllocateEipAddressRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The instance to which you want to assign a static public IP address must be in the Running (Running) or Stopped (Stopped) state.
     * 
If OperationLocks in the response of the DescribeInstances operation contains "LockReason" : "security" for an instance, the instance is locked for security reasons and cannot be assigned a static public IP address.
     * 
You can assign only one static public IP address to an ECS instance. If the instance already has a static public IP address, the static public IP address is returned for the IpAddress response parameter.
     * 
After you assign a static public IP address to an ECS instance, you must restart the instance (RebootInstance) or start the instance (StartInstance) for the public IP address to take effect.
     * If an ECS instance resides in a virtual private cloud (VPC), you can assign a static public IP address to the instance or associate an elastic IP address (EIP) with the instance. For more information, see AssociateEipAddress.
     * 
     * 
     * @param request the request parameters of AllocatePublicIpAddress  AllocatePublicIpAddressRequest
     * @return AllocatePublicIpAddressResponse
     */
    CompletableFuture allocatePublicIpAddress(AllocatePublicIpAddressRequest request);

    /**
     * description :
     * 
  Each disk can have only one automatic snapshot policy.
     * 

     * 
Each automatic snapshot policy can be applied to multiple disks.
     * 
     * 
     * @param request the request parameters of ApplyAutoSnapshotPolicy  ApplyAutoSnapshotPolicyRequest
     * @return ApplyAutoSnapshotPolicyResponse
     */
    CompletableFuture applyAutoSnapshotPolicy(ApplyAutoSnapshotPolicyRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can specify IPv6 addresses in the CIDR block of the vSwitch to which the ENI is connected. You can also specify the number of IPv6 addresses that the system assigns to the ENI. Take note of the following items:
     * 

     * 
IPv6 must be enabled on the vSwitch to which the ENI is connected. For more information, see Enable IPv6 for a vSwitch.
     * 
The ENI must be in the Available (Available) or InUse (InUse) state.
     * 
If you want to assign IPv6 addresses to a primary ENI, make sure that the Elastic Compute Service (ECS) instance to which the ENI is attached is in the Running (Running) or Stopped (Stopped) state.
     * 
The maximum number of IPv6 addresses that can be assigned to an ENI varies based on the instance type of the instance to which the ENI is attached.

     * 
If the ENI is in the Available (Available) state, up to 10 IPv6 addresses can be assigned to the ENI.
     * 
If the ENI is attached to an ECS instance, the maximum number of IPv6 addresses that can be assigned to the ENI varies based on the instance type. For more information, see Overview of instance families.
     * 
     * 
     * 
After the operation is called, you can obtain the IPv6 addresses that are assigned to the ENI from the response.
     * 
     * 
     * @param request the request parameters of AssignIpv6Addresses  AssignIpv6AddressesRequest
     * @return AssignIpv6AddressesResponse
     */
    CompletableFuture assignIpv6Addresses(AssignIpv6AddressesRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The ENI to which you want to assign secondary private IP addresses must be in the Available (Available) or InUse (InUse) state.
     * 
When you assign private IP addresses to a primary ENI, the Elastic Compute Service (ECS) instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
     * 
When an ENI is in the Available state, you can assign up to 49 secondary private IP addresses to the ENI. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI varies based on the instance type. For more information, see Overview of instance families.
     * 
After the operation is called, you can obtain the assigned secondary private IP addresses from the response.
     * 
     * 
     * @param request the request parameters of AssignPrivateIpAddresses  AssignPrivateIpAddressesRequest
     * @return AssignPrivateIpAddressesResponse
     */
    CompletableFuture assignPrivateIpAddresses(AssignPrivateIpAddressesRequest request);

    /**
     * @deprecated OpenAPI AssociateEipAddress is deprecated, please use Vpc::2016-04-28::AssociateEipAddress instead.  * @param request  the request parameters of AssociateEipAddress  AssociateEipAddressRequest
     * @return AssociateEipAddressResponse
     */
    @Deprecated
    CompletableFuture associateEipAddress(AssociateEipAddressRequest request);

    /**
     * @deprecated OpenAPI AssociateHaVip is deprecated  * @param request  the request parameters of AssociateHaVip  AssociateHaVipRequest
     * @return AssociateHaVipResponse
     */
    @Deprecated
    CompletableFuture associateHaVip(AssociateHaVipRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
The instance that you want to connect to a VPC must be in the Running or Stopped state.
     * 
The ClassicLink feature must be enabled for the destination VPC. For more information, see Create a ClassicLink connection.
     * 
The instance and the VPC must reside in the same region.
     * 
     * 
     * @param request the request parameters of AttachClassicLinkVpc  AttachClassicLinkVpcRequest
     * @return AttachClassicLinkVpcResponse
     */
    CompletableFuture attachClassicLinkVpc(AttachClassicLinkVpcRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The ECS instance and the disk must reside in the same zone.
     * 
The disk must be in the Unattached (Available) state.
     * 
When you attach the disk as a data disk to an ECS instance, take note of the following items:

     * 
The ECS instance must be in the Running (Running) or Stopped (Stopped) state.
     * 
If the disk was separately purchased, the billing method of the disk must be pay-as-you-go.
     * 
If the disk is a system disk that was detached from an ECS instance, no limits apply to the billing method of the disk.
     * 
If the disk is an elastic ephemeral disk that was detached from an ECS instance, the disk can be attached only to the instance.
     * 
     * 
     * 
When you attach the disk as the system disk to an ECS instance, take note of the following items:

     * 
The ECS instance must be the original instance from which the system disk was detached.
     * 
The ECS instance must be in the Stopped (Stopped) state.
     * 
You must configure logon credentials for the ECS instance.
     * 
The disk cannot be an elastic ephemeral disk.
     * 
For more information about how to attach a system disk, see Detach or attach a system disk.
     * 
     * 
     * 
If the response contains {"OperationLocks": {"LockReason" : "security"}} when you query information about an ECS instance, the instance is locked for security reasons. No operations are allowed on the instance.
     * 
     * 
     * @param request the request parameters of AttachDisk  AttachDiskRequest
     * @return AttachDiskResponse
     */
    CompletableFuture attachDisk(AttachDiskRequest request);

    /**
     * description :
     * 
You can call the DescribeInstanceRamRole operation to query the instance RAM roles that are attached to ECS instances.
     * 

     * 
 If an ECS instance already has an instance RAM role, an error is returned when you attach another instance RAM role to the instance.
     * 
     * 
     * @param request the request parameters of AttachInstanceRamRole  AttachInstanceRamRoleRequest
     * @return AttachInstanceRamRoleResponse
     */
    CompletableFuture attachInstanceRamRole(AttachInstanceRamRoleRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
SSH key pairs are not supported on Windows instances.
     * 
If an SSH key pair is bound to an instance, authentication by using the username and password is disabled for the instance.
     * 
If you bind an SSH key pair to an instance in the running state, you must call the RebootInstance operation to restart the instance for the key pair to take effect.
     * 
If you bind an SSH key pair to an instance in the stopped state, you must call the StartInstance operation to start the instance for the key pair to take effect.
     * 
If an instance is already bound to an SSH key pair, the new SSH key pair will replace the original one.
     * 
     * 
     * @param request the request parameters of AttachKeyPair  AttachKeyPairRequest
     * @return AttachKeyPairResponse
     */
    CompletableFuture attachKeyPair(AttachKeyPairRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The ENI must be in the Available state. You can attach an ENI to only one instance that resides in the same zone and VPC as the ENI.
     * 
The instance must be in the Running or Stopped state. When you attach ENIs to instances of specific instance types, make sure that the instances are in the Stopped state. For more information, see the "Instance types of the ECS instances that must be in the Stopped (Stopped) state" section in the Bind an ENI topic.

     * 
If the last start time of the instance (including the start time of the instance if it is a new instance, the last restart time of the instance, and the last reactivation time of the instance) is before April 1st, 2018 and the instance is in the Running state, you must call the RebootInstance operation to restart the instance. If you do not call the RebootInstance operation to restart the instance, you cannot attach the ENI to the instance.
     * 
     * 
     * 
You can attach multiple ENIs to one instance. For more information, see ENI overview.
     * 
The vSwitch to which the ENI is connected must be in the same zone and VPC as the vSwitch to which the instance is connected.
     * 
This operation is an asynchronous operation. After you call this operation to attach an ENI, you can view the status or events of the ENI to check whether the ENI is attached. The following figure shows the transitions between the statuses of the ENI.
     * 
     * 
     * 

     * 
If the ENI is in the Attaching state, the ENI attachment request is sent and the ENI is being attached to the specified instance. 
     * 
If the ENI is in the InUse state, the ENI is attached to the specified instance.
     * 
If the ENI is in the Available state, the ENI failed to be attached.
     * For examples on how to call this operation, see Attach an ENI.
     * 
     * 
     * @param request the request parameters of AttachNetworkInterface  AttachNetworkInterfaceRequest
     * @return AttachNetworkInterfaceResponse
     */
    CompletableFuture attachNetworkInterface(AttachNetworkInterfaceRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The total number of outbound and inbound rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in Limits.
     * 
The valid values of Priority range from 1 to 100. A smaller value indicates a higher priority.
     * 
When multiple security group rules have the same priority, drop rules take precedence.
     * 
The source can be a CIDR block that is specified by SourceCidrIp, Ipv6SourceCidrIp, or SourcePrefixListId. The source can also be Elastic Compute Service (ECS) instances in a security group that is specified by SourceGroupId.
     * 
You cannot reference security groups as sources or destinations in the rules of advanced security groups.
     * 
You can reference up to 20 security groups as sources or destinations in the rules of each basic security group.
     * 
If the specified security group rule already exists in the security group, the call is successful but no security group rule is created.
     * 
Parameters and their Permissions.N-prefixed counterparts cannot be specified at the same time. We recommend that you use the Permissions.N-prefixed parameters.
     * 
You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.

     * 
Parameters used to specify an inbound security group rule that controls access from a specific CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourceCidrIp. For a security group of the Virtual Private Cloud (VPC) type, you must set NicType to intranet. For a security group of the classic network type, you can set NicType to either internet or intranet. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourceCidrIp=10.0.0.0/8
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=Accept
     * &
     * 
Parameters used to determine an inbound security group rule that controls access from a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceGroupOwnerAccount, and SourceGroupId. In this case, you must set NicType to intranet. For mutual access between security groups in the classic network, you can allow or deny another security group within the same region access to your security group. The security group that is allowed access to your security group can belong to your own Alibaba Cloud account or another Alibaba Cloud account specified by SourceGroupOwnerAccount. For mutual access between security groups in VPCs, you can allow or deny another security group within the same VPC access to your security group. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourceGroupId=sg-1651FBB**
     * &Permissions.1.SourceGroupOwnerAccount=[email protected]
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=Drop
     * &
     * 
Parameters used to determine an inbound security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourcePrefixListId. In this case, prefix lists support only security groups in VPCs. NicType must be set to intranet. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
     * &Permissions.1.SourceGroupOwnerAccount=[email protected]
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=Drop
     * &
     * 
     * 
     * 
For information about examples on security group rule settings, see Security groups for different use cases and Security group quintuple rules.
     * 
     * 
     * @param request the request parameters of AuthorizeSecurityGroup  AuthorizeSecurityGroupRequest
     * @return AuthorizeSecurityGroupResponse
     */
    CompletableFuture authorizeSecurityGroup(AuthorizeSecurityGroupRequest request);

    /**
     * description :
     * 
Limits
     * 

     * 
Quantity limit: The total number of outbound security group rules in each security group cannot exceed 200. For more information, see the Security group limits section of the "Limits" topic.
     * 
Rule types: For outbound security group rules, you can set Policy to accept or drop to specify whether to allow or deny access.
     * 
Rule priorities: For outbound security group rules, the valid values of Priority range from 1 to 100. A smaller value indicates a higher priority. When multiple security group rules have the same priority, drop rules take precedence.
     * 
     * 
Considerations
     * 

     * 
If the security group rule that you call the AuthorizeSecurityGroupEgress operation to create exists in the security group, the call is successful but no security group rule is created.
     * 
Parameters and their Permissions.N-prefixed counterparts cannot be specified in the same request. We recommend that you use the Permissions.N-prefixed parameters.
     * 
     * 
Parameters that define a security group rule
     * 
Define a security group rule by configuring the following parameters together:
     * 

     * 
One of the following parameters: DestCidrIp, Ipv6DestCidrIp, DestPrefixListId, and DestGroupId. DestCidrIp specifies the destination IPv4 CIDR block. Ipv6DestCidrIp specifies the destination IPv6 CIDR block. DestPrefixListId specifies the ID of the destination prefix list. DestGroupId specifies the destination security group.
     * 
PortRange: specifies the range of destination port numbers.
     * 
IpProtocol: specifies the protocol.
     * 
Policy: specifies the action.

     * 
 Advanced security groups do not support security group rules that reference security groups as authorization objects. Each basic security group can contain up to 20 security group rules that reference security groups as authorization objects.
     * 
     * 
     * 
     * 
Sample requests
     * 
Sample requests to create outbound security group rules that control access to different destinations in a security group in the China (Hangzhou) region:
     * 

     * 
Sample request to create an outbound security group rule that controls access to a specific CIDR block:
     * "RegionId":"cn-hangzhou",  //The region ID of the source security group.
     * "SecurityGroupId":"sg-bp17vs63txqxbds9***", //The ID of the source security group.
     * "Permissions":[
     *      {
     *        "DestCidrIp": "10.0.0.0/8", //The destination IPv4 CIDR block.
     *        "PortRange": "-1/-1", //The range of destination port numbers.
     *        "IpProtocol": "ICMP", //The protocol.
     *        "Policy": "Accept" //The action.
     *      }
     * ]
     * 
Sample request to create an outbound security group rule that controls access to a security group and an outbound security group rule that controls access to a prefix list:
     * "RegionId":"cn-hangzhou",
     * "SecurityGroupId":"sg-bp17vs63txqxbds9***",
     * "Permissions":[
     *      {
     *        "DestGroupId": "sg-bp67acfmxazb4pi***", //The ID of the destination security group.
     *        "PortRange": "22/22",
     *        "IpProtocol": "TCP",
     *        "Policy": "Drop"
     *      },{
     *        "DestPrefixListId": "pl-x1j1k5ykzqlixdcy****", //The ID of the destination prefix list.
     *        "PortRange": "22/22",
     *        "IpProtocol": "TCP",
     *        "Policy": "Drop"
     *      }
     * ]
     * 
     * 
     * @param request the request parameters of AuthorizeSecurityGroupEgress  AuthorizeSecurityGroupEgressRequest
     * @return AuthorizeSecurityGroupEgressResponse
     */
    CompletableFuture authorizeSecurityGroupEgress(AuthorizeSecurityGroupEgressRequest request);

    /**
     * @param request the request parameters of CancelAutoSnapshotPolicy  CancelAutoSnapshotPolicyRequest
     * @return CancelAutoSnapshotPolicyResponse
     */
    CompletableFuture cancelAutoSnapshotPolicy(CancelAutoSnapshotPolicyRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
After you cancel an image copy task, the image copy created in the destination region is deleted, and the copied image remains unchanged.
     * 
If the image copy task is complete, the CancelCopyImage operation fails, and an error is returned.
     * 
     * 
     * @param request the request parameters of CancelCopyImage  CancelCopyImageRequest
     * @return CancelCopyImageResponse
     */
    CompletableFuture cancelCopyImage(CancelCopyImageRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that the image build task to be canceled is in the BUILDING, DISTRIBUTING, or RELEASING state.
     * 
     * @param request the request parameters of CancelImagePipelineExecution  CancelImagePipelineExecutionRequest
     * @return CancelImagePipelineExecutionResponse
     */
    CompletableFuture cancelImagePipelineExecution(CancelImagePipelineExecutionRequest request);

    /**
     * @deprecated OpenAPI CancelPhysicalConnection is deprecated  * @param request  the request parameters of CancelPhysicalConnection  CancelPhysicalConnectionRequest
     * @return CancelPhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture cancelPhysicalConnection(CancelPhysicalConnectionRequest request);

    /**
     * @param request the request parameters of CancelSimulatedSystemEvents  CancelSimulatedSystemEventsRequest
     * @return CancelSimulatedSystemEventsResponse
     */
    CompletableFuture cancelSimulatedSystemEvents(CancelSimulatedSystemEventsRequest request);

    /**
     * @param request the request parameters of CancelTask  CancelTaskRequest
     * @return CancelTaskResponse
     */
    CompletableFuture cancelTask(CancelTaskRequest request);

    /**
     * @deprecated OpenAPI ConnectRouterInterface is deprecated  * @param request  the request parameters of ConnectRouterInterface  ConnectRouterInterfaceRequest
     * @return ConnectRouterInterfaceResponse
     */
    @Deprecated
    CompletableFuture connectRouterInterface(ConnectRouterInterfaceRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After a public IP address is converted into an EIP, the EIP is billed separately. Make sure that you fully understand the billing methods of EIPs. For more information, see Billing overview.
     * When you call this operation, make sure that the ECS instance meets the following requirements:
     * 

     * 
The instance is in the Stopped (Stopped) or Running (Running) state.
     * 
The instance has no EIPs associated.
     * 
The instance has no configuration change tasks that have not taken effect.
     * 
The public bandwidth of the instance is not 0 Mbit/s.
     * 
If the instance is a subscription instance, the billing method for network usage of the instance must be pay-by-traffic. The public IP address of a subscription instance that uses the pay-by-bandwidth billing method for network usage cannot be converted into an EIP. This requirement does not apply to pay-as-you-go instances. For more information, see Change the billing method for network usage.
     * 
If the instance is a subscription instance that resides in a VPC, the instance does not expire within 24 hours.
     * 
     * 
     * @param request the request parameters of ConvertNatPublicIpToEip  ConvertNatPublicIpToEipRequest
     * @return ConvertNatPublicIpToEipResponse
     */
    CompletableFuture convertNatPublicIpToEip(ConvertNatPublicIpToEipRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After you copy a custom image to the destination region, you can use the image copy (new image) to create ECS instances by calling the RunInstances operation or replace the system disks of instances by calling the ReplaceSystemDisk operation in the destination region.
     * Take note of the following items:
     * 

     * 
Only custom images that are in the Available state can be copied.
     * 
Custom images that belong to your Alibaba Cloud account can be copied across regions. Images that are shared with you by others can be copied only within the regions where the images reside.
     * 
When an image is being copied, the new image cannot be deleted by calling the DeleteImage operation. However, you can cancel the ongoing image copy task by calling the CancelCopyImage operation.
     * 
A region supports only up to five concurrent image copy tasks. Excess image copy tasks are queued for execution.
     * 
You can configure ResourceGroupId to specify the resource group to which to assign the new image. If you do not configure ResourceGroupId, the new image is assigned to the default resource group.
     * 
     * 
     * @param request the request parameters of CopyImage  CopyImageRequest
     * @return CopyImageResponse
     */
    CompletableFuture copyImage(CopyImageRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
New snapshots (snapshot copies) cannot be used to roll back the disks for which source snapshots (copied snapshots) were created.
     * 
Local snapshots cannot be copied.
     * 
     * 
     * @param request the request parameters of CopySnapshot  CopySnapshotRequest
     * @return CopySnapshotResponse
     */
    CompletableFuture copySnapshot(CopySnapshotRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After you use an activation code to register a server that is not provided by Alibaba Cloud as an Alibaba Cloud managed instance, you can use a variety of online services provided by Alibaba Cloud, such as Cloud Assistant, CloudOps Orchestration Service (OOS), and Apsara Devops on the managed instance.
     * If a server is not provided by Alibaba Cloud, you can register the server as an Alibaba Cloud managed instance only if the server has Internet connectivity and runs one of the following operating systems:
     * 

     * 
Alibaba Cloud Linux 2 and Alibaba Cloud Linux 3 and later
     * 
CentOS 6, CentOS 7, and CentOS 8 and later
     * 
Debian 8, Debian 9, and Debian 10 and later
     * 
Ubuntu 12, Ubuntu 14, Ubuntu 16, and Ubuntu 18 and later
     * 
CoreOS
     * 
OpenSUSE
     * 
Red Hat 5, Red Hat 6, and Red Hat 7 and later
     * 
SUSE Linux Enterprise Server 11, SUSE Linux Enterprise Server 12, and SUSE Linux Enterprise Server 15 and later
     * 
Windows Server 2012, Windows Server 2016, and Windows Server 2019 and later
     * You can have up to 5,000 activation codes per Alibaba Cloud region. When the number of activation codes exceeds 1,000, the usage of the activation codes must be greater than 50% before you can create additional activation codes.

     * 
 To obtain the usage of activation codes, go to the ECS Cloud Assistant page, click the Manage Instances tab, and then click Register Instance.
     * 
     * 
     * 
     * 
     * @param request the request parameters of CreateActivation  CreateActivationRequest
     * @return CreateActivationResponse
     */
    CompletableFuture createActivation(CreateActivationRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
Auto Provisioning is a service that allows quick deployment of an instance cluster that consists of preemptible instances and pay-as-you-go instances. Auto Provisioning supports push-button deployment of instance clusters across different billing methods, instance families, and zones. For more information, see Use auto provisioning group-related API operations to create multiple ECS instances at the same time.
     * 
Auto Provisioning uses auto provisioning groups to schedule and maintain computing resources. You can use auto provisioning groups to obtain a steady supply of computing resources. This helps reduce the impact on compute capacity when preemptible instances are reclaimed.
     * 
Auto Provisioning is provided free of charge. However, you are charged for instance resources that are created in auto provisioning groups. For more information, see Overview of preemptible instances and Pay-as-you-go.
     * 
When you specify both a launch template (LaunchTemplateId) and extended configurations (LaunchConfiguration.* parameters), LaunchTemplateId takes precedence.
     * 
     * 
     * @param request the request parameters of CreateAutoProvisioningGroup  CreateAutoProvisioningGroupRequest
     * @return CreateAutoProvisioningGroupResponse
     */
    CompletableFuture createAutoProvisioningGroup(CreateAutoProvisioningGroupRequest request);

    /**
     * description :
     * 
Usage notes
     * 
When you call this operation to create an automatic snapshot policy, you can specify the days of the week on which to create automatic snapshots, the retention period of the automatic snapshots, and whether to enable cross-region replication for the snapshots in the policy to meet your diverse data backup requirements. After the automatic snapshot policy is created, call the ApplyAutoSnapshotPolicy operation to apply the policy to disks. If you want to modify the automatic snapshot policy, call the ModifyAutoSnapshotPolicyEx operation.
     * Take note of the following items:
     * 

     * 
You can create up to 100 automatic snapshot policies per region for a single Alibaba Cloud account.
     * 
If an automatic snapshot is being created when the time scheduled for creating another automatic snapshot is due, the new snapshot task is skipped. This may occur when a disk contains a large volume of data. For example, you have scheduled snapshots to be created at 09:00:00, 10:00:00, 11:00:00, and 12:00:00 for a disk. The system starts to create a snapshot for the disk at 09:00:00. The process takes 80 minutes to complete because the disk contains a large volume of data and ends at 10:20:00. In this case, the system does not create a snapshot at 10:00, but creates a snapshot at 11:00.
     * 
For information about how to copy a snapshot from one region to another region, see the "Background information" section in Copy a snapshot.
     * 
     * 
     * @param request the request parameters of CreateAutoSnapshotPolicy  CreateAutoSnapshotPolicyRequest
     * @return CreateAutoSnapshotPolicyResponse
     */
    CompletableFuture createAutoSnapshotPolicy(CreateAutoSnapshotPolicyRequest request);

    /**
     * description :
     * 
When you create a capacity reservation, you can specify attributes such as a zone and an instance type. The system uses a private pool to reserve resources that match the specified attributes. For more information, see Overview of Immediate Capacity Reservation.
     * 

     * 
Currently, only immediate capacity reservations are supported. Immediate capacity reservations take effect immediately after you purchase them. After you purchase an immediate capacity reservation, you are charged for the specified instance type based on the pay-as-you-go billing method regardless of whether you use the capacity reservation to create pay-as-you-go instances. Billing stops when you manually release the capacity reservation or when the capacity reservation expires and is automatically released.

     * 
You can call the CreateInstance or RunInstances operation to specify private pool attributes when you create instances. To modify the attributes of a private pool, you can call the ModifyInstanceAttachmentAttributes operation. If an instance matches a private pool associated with a capacity reservation, you are charged based on the configurations of the instance such as the instance type, disks, and public bandwidth.
     * 
Before you use a private pool associated with a capacity reservation to create pay-as-you-go instances, you are charged only for the specified instance type.
     * 
     * 
     * 
You can apply savings plans or regional reserved instances to offset hourly billing of unused immediate capacity reservations, and hourly fees of the instances that match the immediate capacity reservations. However, you cannot use zonal reserved instances to offset the hourly fees. We recommend that you purchase reserved instances or savings plans before you purchase immediate capacity reservations. This way, you can access resources free of charge within the coverage of the reserved instances or savings plans.

     * 
You can call the CreateCapacityReservation operation to create only immediate capacity reservations. You can create immediate or scheduled capacity reservations in the Elastic Compute Service (ECS) console. For more information, see Overview.
     * 
     * 
     * 
     * 
     * @param request the request parameters of CreateCapacityReservation  CreateCapacityReservationRequest
     * @return CreateCapacityReservationResponse
     */
    CompletableFuture createCapacityReservation(CreateCapacityReservationRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
You can create commands of the following types:

     * 
Batch commands (RunBatScript), applicable to Windows instances
     * 
PowerShell commands (RunPowerShellScript), applicable to Windows instances
     * 
Shell commands (RunShellScript), applicable to Linux instances
     * 
     * 
     * 
You can specify the Timeout parameter to set the maximum timeout period for executions of a command on Elastic Compute Service (ECS) instances. If an execution times out, Cloud Assistant Agent forcefully terminates the command process by canceling the process ID (PID) of the command.

     * 
For a one-time task, when the execution times out, the state of the command (InvokeRecordStatus) becomes Failed.
     * 
For a scheduled task, take note of the following items:

     * 
The timeout period takes effect on each execution.
     * 
When an execution times out, the state (InvokeRecordStatus) of the command becomes Failed.
     * 
The timeout of one execution does not affect the subsequent executions.
     * 
     * 
     * 
     * 
     * 
You can retain up to 500 to 50,000 Cloud Assistant commands in each region. You can also apply for a quota increase. For information about how to query and increase quotas, see Manage quotas.
     * 
You can use WorkingDir to specify the execution directory of a Cloud Assistant command. For Linux instances, the default execution directory of Cloud Assistant commands is the home directory of the root user, which is /root. For Windows instances, the default execution directory of Cloud Assistant commands is the directory where the Cloud Assistant Agent process resides, such as C:\\Windows\\System32.
     * 
You can enable the custom parameter feature for a Cloud Assistant command by setting EnableParameter to true. When you set CommandContent, you can define custom parameters in the {{parameter}} format. Then, when the InvokeCommand operation is called, the key-value pairs of custom parameters are passed in. For example, if a command is echo {{name}}, the Parameters parameter can be used to pass in the <name, Jack> key-value pair when the InvokeCommand operation is called. The name key of the custom parameter is automatically replaced by the paired Jack value to generate a new command. As a result, the echo Jack command is run.
     * 
     * 
     * @param request the request parameters of CreateCommand  CreateCommandRequest
     * @return CreateCommandResponse
     */
    CompletableFuture createCommand(CreateCommandRequest request);

    /**
     * @param request the request parameters of CreateDedicatedHostCluster  CreateDedicatedHostClusterRequest
     * @return CreateDedicatedHostClusterResponse
     */
    CompletableFuture createDedicatedHostCluster(CreateDedicatedHostClusterRequest request);

    /**
     * @deprecated OpenAPI CreateDemand is deprecated, please use Ecs::2014-05-26::CreateCapacityReservation instead.  * @description You can call this operation to file a demand for an ECS instance type. Alibaba Cloud provides the requested resources based on your demand.
     * You can file demands only for I/O optimized instance types and instances of the virtual private cloud (VPC) type.
     * > This operation is in internal preview and has not been officially released. We recommend that you do not call this operation.
     * 
     * @param request the request parameters of CreateDemand  CreateDemandRequest
     * @return CreateDemandResponse
     */
    @Deprecated
    CompletableFuture createDemand(CreateDemandRequest request);

    /**
     * @param request the request parameters of CreateDeploymentSet  CreateDeploymentSetRequest
     * @return CreateDeploymentSetResponse
     */
    CompletableFuture createDeploymentSet(CreateDeploymentSetRequest request);

    /**
     * @param request the request parameters of CreateDiagnosticMetricSet  CreateDiagnosticMetricSetRequest
     * @return CreateDiagnosticMetricSetResponse
     */
    CompletableFuture createDiagnosticMetricSet(CreateDiagnosticMetricSetRequest request);

    /**
     * @param request the request parameters of CreateDiagnosticReport  CreateDiagnosticReportRequest
     * @return CreateDiagnosticReportResponse
     */
    CompletableFuture createDiagnosticReport(CreateDiagnosticReportRequest request);

    /**
     * description :
     * 
  You can enable the multi-attach (MultiAttach) feature when you create a disk. Before you enable the multi-attach feature, we recommend that you familiarize yourself with the feature and the limits on the feature. For more information, see NVMe protocol and Use the multi-attach feature to attach a cloud disk to multiple ECS instances.
     * 

     * 
You can create disks of the following disk categories: basic disks, ultra disks, standard SSDs, Enterprise SSDs (ESSDs), ESSD Entry disks, Regional ESSDs, ESSD AutoPL disks, standard elastic ephemeral disks, and premium elastic ephemeral disks.
     * 
Before you can create a disk, you must complete real-name verification. Complete real-name verification on the Real-name Verification page in the Alibaba Cloud Management Console.
     * 
When you create disks, you may be charged for the resources used. We recommend that you familiarize yourself with the billing methods of Elastic Compute Service (ECS) resources before you create a disk. For more information, see Billing overview.
     * 
When you call this operation to create a disk, specific parameters are automatically specified.

     * 
DeleteAutoSnapshot is automatically set to true when a disk is created. This indicates that the automatic snapshots of the disk are deleted when the disk is released. You can call the DescribeDisks operation to query the DeleteAutoSnapshot value for the disk and call the ModifyDiskAttribute operation to change the DeleteAutoSnapshot value for the disk.
     * 
If you do not specify a performance level when you create an ESSD, the performance level of the ESSD is automatically set to PL1. To change the performance level of the ESSD, you can call the ModifyDiskSpec operation.
     * 
Portable is automatically set to true when a disk is created, which indicates that the disk is a pay-as-you-go disk.
     * 
     * 
     * 
     * 
     * @param request the request parameters of CreateDisk  CreateDiskRequest
     * @return CreateDiskResponse
     */
    CompletableFuture createDisk(CreateDiskRequest request);

    /**
     * description :
     * 
Elasticity Assurance provides a new way to purchase and use resources with flexibility and assurance. It offers assured resource reservations for pay-as-you-go Elastic Compute Service (ECS) instances. For more information, see Overview of Elasticity Assurance.
     * 

     * 
Elasticity assurances are not refundable after purchase.
     * 
Elasticity assurances are applicable to only pay-as-you-go ECS instances.
     * 
Elasticity assurances support only the unlimited mode. Therefore, you can set AssuranceTimes only to Unlimited. Elasticity assurances in unlimited mode can be applied an unlimited number of times within their effective period and take effect immediately after they are purchased.
     * 
     * 
     * @param request the request parameters of CreateElasticityAssurance  CreateElasticityAssuranceRequest
     * @return CreateElasticityAssuranceResponse
     */
    CompletableFuture createElasticityAssurance(CreateElasticityAssuranceRequest request);

    /**
     * @deprecated OpenAPI CreateForwardEntry is deprecated  * @param request  the request parameters of CreateForwardEntry  CreateForwardEntryRequest
     * @return CreateForwardEntryResponse
     */
    @Deprecated
    CompletableFuture createForwardEntry(CreateForwardEntryRequest request);

    /**
     * @deprecated OpenAPI CreateHaVip is deprecated  * @param request  the request parameters of CreateHaVip  CreateHaVipRequest
     * @return CreateHaVipResponse
     */
    @Deprecated
    CompletableFuture createHaVip(CreateHaVipRequest request);

    /**
     * @param request the request parameters of CreateHpcCluster  CreateHpcClusterRequest
     * @return CreateHpcClusterResponse
     */
    CompletableFuture createHpcCluster(CreateHpcClusterRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
You can use the created custom image only if the image is in the Available (Available) state.
     * 
If the response contains {"OperationLocks": {"LockReason" : "security"}} when you query the information of an instance, the instance is locked for security reasons. No operations are allowed on the instance.
     * 
To optimize the image, we recommend that you specify DetectionStrategy when you create the image. For more information, see Overview of image check.
     * You can call the CreateImage operation to create a custom image by using one of the following methods. The following request parameters are sorted by priority: InstanceId > DiskDeviceMapping > SnapshotId. If your request contains two or more of these parameters, the custom image is created based on the parameter that has a higher priority.
     * 
Method 1: Create a custom image from an instance. You need to only specify the ID of the instance by using InstanceId. The instance must be in the Running (Running) or Stopped (Stopped) state. After you call the CreateImage operation, a snapshot is created for each disk of the instance. When you create a custom image from a running instance, cache data may not be written to disks. In this case, the data of the custom image may be slightly different from the data of the instance. We recommend that you stop instances by calling the StopInstances operation before you create custom images from the instances.
     * 
Method 2: Create a custom image from the system disk snapshot of an instance. You need to only specify the ID of the system disk snapshot by using SnapshotId. The specified system disk snapshot must be created after July 15, 2013.
     * 
Method 3: Create a custom image from multiple disk snapshots. You must specify data mappings between the snapshots and the disks to be created by using the parameters that start with DiskDeviceMapping.
     * When you use Method 3 to create a custom image, take note of the following items:
     * 
You can specify only one snapshot to use to create the system disk in the custom image. The device name of the system disk must be /dev/xvda.
     * 
You can specify up to 16 snapshots to use to create data disks in the custom image. The device names of the data disks are unique and range from /dev/xvdb to /dev/xvdz in alphabetical order.
     * 
You can leave SnapshotId empty. In this case, an empty data disk with the specified size is created.
     * 
The specified disk snapshot must be created after July 15, 2013.
     * 
     * 
     * @param request the request parameters of CreateImage  CreateImageRequest
     * @return CreateImageResponse
     */
    CompletableFuture createImage(CreateImageRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
You can create only custom image components.
     * 
Only Linux operating systems are supported. Set SystemType to Linux.
     * 
Only image build components are supported. Set ComponentType to Build.
     * 
You can use Dockerfile to edit the content of image components and pass the edited content into the Content parameter. The content size can be up to 16 KB. FROM commands cannot be used in image components. An image component supports up to 127 commands. For information about the supported commands, see Commands supported by Image Builder.
     * You can use image components to create image templates in the Elastic Compute Service (ECS) console, but cannot call API operations to create image templates from image components. For more information, see What is Image Builder.
     * 
     * 
     * @param request the request parameters of CreateImageComponent  CreateImageComponentRequest
     * @return CreateImageComponentResponse
     */
    CompletableFuture createImageComponent(CreateImageComponentRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can use image templates to customize image content and create images across regions and accounts. Take note of the following items:
     * 

     * 
You can create only custom image templates.
     * 
You can configure only public, custom, or shared Linux images or image families as the source images when you create image templates.
     * 
When you create an image from an image template, an intermediate Elastic Compute Service (ECS) instance that uses the pay-as-you-go billing method is created. You are charged for the instance. For more information, see Pay-as-you-go.
     * When you use the BuildContent parameter to specify the content of the image template, take note of the following items:
     * 
If the BuildContent value contains FROM commands, the FROM commands override the values of BaseImageType that specifies the type of the source image and BaseImage that specifies the source image.
     * 
If the BuildContent value does not contain FROM commands, the system creates a FROM command that consists of the BaseImageType and BaseImage values in the format of <BaseImageType>:<BaseImage> and adds the command to the first line of the template content.
     * 
You can use Dockerfile to edit the content of the image template and then pass the edited content into the BuildContent parameter. The content cannot be greater than 16 KB in size and can contain up to 127 commands. For information about commands supported by image templates, see Commands supported by Image Builder.
     * You can use image components to create image templates in the ECS console, but cannot call API operations to use image components to create image templates. For more information, see What is Image Builder.
     * 
     * 
     * @param request the request parameters of CreateImagePipeline  CreateImagePipelineRequest
     * @return CreateImagePipelineResponse
     */
    CompletableFuture createImagePipeline(CreateImagePipelineRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
 This operation is no longer iterated or updated. We recommend that you call the RunInstances operation instead.
     * Before you call this operation, familiarize yourself with the billing and pricing of ECS resources.
     * This operation is an asynchronous operation. After a request to create an ECS instance is sent, an ECS instance ID is immediately returned but the instance may be still being created. You can call the DescribeInstanceStatus operation to query the status of the instance. If the status of the instance is Stopped in the DescribeInstanceStatus response, the instance is created. In this case, you can call the StartInstance operation to start the instance.
     * 
     * 

     * 
Prerequisites

     * 
Make sure that you are familiar with the ECS billing methods because you may be charged for the resources that are used by the instance. For more information, see Billing overview.
     * 
Make sure that the number of ECS instances you create or the number of vCPUs on ECS instances of all instance types you create does not exceed the corresponding quota. Go to the Quota Center to view the quotas.
     * 
Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, create a VPC in the region. For more information, see Create a VPC.
     * 
     * 
     * 
Considerations:

     * 
If you create a subscription instance (PrePaid), available coupons in your account are used by default.
     * 
If you want to create instances with 512 MiB of memory, you cannot use Windows Server images except for Windows Server Semi-Annual Channel images. If you want to create instances with 4 GiB or more of memory, you cannot use 32-bit OS image.
     * 
If you call the CreateInstance operation to create an instance, no public IP address is automatically assigned to the instance. You can call the AllocatePublicIpAddress operation to assign a public IP address to the instance.
     * **
     * Note Starting November 27, 2020, when you create ECS instances or change ECS instance configurations, the maximum bandwidth value that you can specify is subject to the throttling policy of your account. To increase the maximum bandwidth value, submit a ticket. The throttling policy imposes the following constraints: In a single region, the total maximum bandwidth value of all instances that use the pay-by-traffic billing method for network usage cannot exceed 5 Gbit/s and the total bandwidth value of all instances that use the pay-by-bandwidth billing method for network usage cannot exceed 50 Gbit/s.
     * 
     * 
     * 
Suggestions:

     * 
Instance type selection: See Instance families or call the DescribeInstanceTypes operation to query the performance data of instance types, or see Best practices for instance type selection to learn about how to select instance types.
     * 
Query of available resources: Call the DescribeAvailableResource operation to query resources available in a specific region or zone.
     * 
User data: If the instance type supports user data, you can use the UserData parameter to pass in user data. User data is encoded in Base64. We recommend that you do not pass in confidential information (such as passwords or private keys) in plaintext as user data. This is because the system does not encrypt UserData values when API requests are transmitted. If you must pass in confidential information, we recommend that you encrypt and encode the information in Base64 before you pass in the information. Then decode and decrypt the information in the same way within the instance.
     * 
     * 
     * 
     * 
     * @param request the request parameters of CreateInstance  CreateInstanceRequest
     * @return CreateInstanceResponse
     */
    CompletableFuture createInstance(CreateInstanceRequest request);

    /**
     * description :
     * 
In addition to calling the CreateKeyPair operation to create a key pair, you can use a third-party tool to create a key pair and then call the ImportKeyPair operation to upload the key pair to an Alibaba Cloud region.
     * Up to 500 key pairs can be created in each region. For more information, see the "SSH key pair limits" section in Limits.
     * 
     * @param request the request parameters of CreateKeyPair  CreateKeyPairRequest
     * @return CreateKeyPairResponse
     */
    CompletableFuture createKeyPair(CreateKeyPairRequest request);

    /**
     * description :
     * 
After you create a launch template by calling the CreateLaunchTemplate operation, a default version that has a version number of 1 is automatically generated for the launch template. You can call the CreateLaunchTemplateVersion operation to create additional versions for the launch template. Version numbers start from 1 and increment by 1. If you specify a launch template but do not specify a launch template version number when you call the RunInstances operation to create instances, the default version of the launch template is used.
     * Launch templates contain preset configurations that are used to create instances, such as the region ID, image ID, instance type, security group ID, and public bandwidth settings. If a specific parameter is not included in a launch template, you need to manually specify the parameter when you use the launch template to create instances.
     * Take note of the following items:
     * 

     * 
You can retain up to 30 launch templates in each region in your Alibaba Cloud account. Each launch template can have up to 30 versions.
     * 
Most parameters in launch templates are optional. When you create a launch template, ECS does not verify the existence or validity of specified parameter values. The parameter values are verified only when you use the launch template to create instances.
     * 
If you configured a specific parameter in a launch template, you cannot filter out the parameter when you call the RunInstances operation to create instances from the launch template. For example, if you set HostName to LocalHost in a launch template but do not specify HostName when you call the RunInstances operation to create instances from the launch template, the hostname of the created instances is LocalHost. If you want to overwrite LocalHost, which is the value of HostName in the launch template, you can set HostName to MyHost or a different value when you call the RunInstances operation.
     * 
     * 
     * @param request the request parameters of CreateLaunchTemplate  CreateLaunchTemplateRequest
     * @return CreateLaunchTemplateResponse
     */
    CompletableFuture createLaunchTemplate(CreateLaunchTemplateRequest request);

    /**
     * description :
     * 
Usage notes
     * 
If you want to modify the parameters of a launch template version, you can create another version with different parameter settings for the launch template. You can create up to 30 versions for each launch template.
     * 
     * @param request the request parameters of CreateLaunchTemplateVersion  CreateLaunchTemplateVersionRequest
     * @return CreateLaunchTemplateVersionResponse
     */
    CompletableFuture createLaunchTemplateVersion(CreateLaunchTemplateVersionRequest request);

    /**
     * @deprecated OpenAPI CreateNatGateway is deprecated  * @param request  the request parameters of CreateNatGateway  CreateNatGatewayRequest
     * @return CreateNatGatewayResponse
     */
    @Deprecated
    CompletableFuture createNatGateway(CreateNatGatewayRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
This operation is a synchronous operation. After an ENI is created, the ENI immediately enters the Available (Available) state and can be attached to an Elastic Compute Service (ECS) instance.
     * 
If NetworkInterfaceId is empty in the response, no ENI is created. Recall the operation to create an ENI.
     * 
An ENI can be attached only to a single ECS instance that resides in a virtual private cloud (VPC).
     * 
When an ENI is detached from an ECS instance and attached to another ECS instance, the attributes of the ENI remain unchanged and network traffic is redirected to the new instance.
     * 
When you call this operation to create an ENI, you can assign up to 49 secondary private IP addresses to the ENI.
     * 
If you want to assign IPv6 addresses when you create an ENI, make sure that IPv6 is enabled for the vSwitch with which you want to associate the ENI. For more information, see What is an IPv6 gateway?
     * 
A limit is imposed on the number of ENIs that can be created per Alibaba Cloud region per account. You can view the quota limit in the ECS console. For more information, see Manage ECS quotas.
     * 
     * 
Sample requests
     * 
Create an ENI
     *     RegionId:  cn-hangzhou,   // Specify the China (Hangzhou) region.SecurityGroupId:  sg-bp10jztp6b0sdsyl****,   // Specify the ID of the security group in which to create the ENI.VSwitchId:  vsw-bp19wo63nleroq22g****,   // Specify the ID of the vSwitch to which to connect the ENI.
     * Create an ENI and specify an IP address as the primary private IP address of the ENI
     *     RegionId:  cn-hangzhou,   // Specify the China (Hangzhou) region.SecurityGroupId:  sg-bp10jztp6b0sdsyl****,   // Specify the ID of the security group in which to create the ENI.VSwitchId:  vsw-bp19wo63nleroq22g****,   // Specify the ID of the vSwitch to which to connect the ENI.PrimaryIpAddress:  192.168.0.*,   // Specify an IP address as the primary private IP address of the ENI.
     * 
     * @param request the request parameters of CreateNetworkInterface  CreateNetworkInterfaceRequest
     * @return CreateNetworkInterfaceResponse
     */
    CompletableFuture createNetworkInterface(CreateNetworkInterfaceRequest request);

    /**
     * description :
     * 
Before you call this operation, submit a ticket to apply for using this operation.
     * 
     * @param request the request parameters of CreateNetworkInterfacePermission  CreateNetworkInterfacePermissionRequest
     * @return CreateNetworkInterfacePermissionResponse
     */
    CompletableFuture createNetworkInterfacePermission(CreateNetworkInterfacePermissionRequest request);

    /**
     * @deprecated OpenAPI CreatePhysicalConnection is deprecated  * @param request  the request parameters of CreatePhysicalConnection  CreatePhysicalConnectionRequest
     * @return CreatePhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture createPhysicalConnection(CreatePhysicalConnectionRequest request);

    /**
     * description :
     * 
  A prefix list is a collection of network prefixes (CIDR blocks) and can be referenced to configure network rules for other resources. For more information, see Overview.
     * 

     * 
When you create a prefix list, take note of the following items:

     * 
You must specify an IP address family (IPv4 or IPv6) for the prefix list, and cannot change the IP address family after the prefix list is created. You cannot combine IPv4 and IPv6 CIDR blocks in a single prefix list.
     * 
You must specify the maximum number of entries that the prefix list can contain. You cannot modify the maximum number of entries after the prefix list is created.
     * 
You can specify entries for the prefix list. Each entry consists of a CIDR block and the description for the CIDR block. The total number of entries cannot exceed the maximum number of entries that you specified.
     * 
     * 
     * 
For more information about the limits on prefix lists and other resources, see Limits.
     * 
You can create Resource Access Management (RAM) users and grant them minimum permissions. This eliminates the need to share the AccessKey pair of your Alibaba Cloud account with other users and reduces security risks for your enterprises. For information about how to grant permissions on prefix lists to RAM users, see Grant a RAM user permissions on prefix lists
     * 
     * 
     * @param request the request parameters of CreatePrefixList  CreatePrefixListRequest
     * @return CreatePrefixListResponse
     */
    CompletableFuture createPrefixList(CreatePrefixListRequest request);

    /**
     * @deprecated OpenAPI CreateRouteEntry is deprecated  * @param request  the request parameters of CreateRouteEntry  CreateRouteEntryRequest
     * @return CreateRouteEntryResponse
     */
    @Deprecated
    CompletableFuture createRouteEntry(CreateRouteEntryRequest request);

    /**
     * @deprecated OpenAPI CreateRouterInterface is deprecated  * @param request  the request parameters of CreateRouterInterface  CreateRouterInterfaceRequest
     * @return CreateRouterInterfaceResponse
     */
    @Deprecated
    CompletableFuture createRouterInterface(CreateRouterInterfaceRequest request);

    /**
     * @param request the request parameters of CreateSavingsPlan  CreateSavingsPlanRequest
     * @return CreateSavingsPlanResponse
     */
    CompletableFuture createSavingsPlan(CreateSavingsPlanRequest request);

    /**
     * description :
     * 
  By default, the internal access control policy (InnerAccessPolicy) of the basic security group that you create by calling this operation is internal interconnectivity (Accept). You can call the ModifySecurityGroupPolicy operation to change the value of InnerAccessPolicy for the basic security group.
     * 

     * 
By default, the internal access control policy (InnerAccessPolicy) of the advanced security group that you create by calling this operation is internal isolation (Drop). The InnerAccessPolicy value of the advanced security group cannot be changed.
     * 
You can create a limited number of security groups per region. You can create at least 100 security groups per region. For more information, see the Security group limits section in the "Limits" topic.
     * 
To create a security group of the Virtual Private Cloud (VPC) type, you must specify VpcId.
     * 
     * 
     * @param request the request parameters of CreateSecurityGroup  CreateSecurityGroupRequest
     * @return CreateSecurityGroupResponse
     */
    CompletableFuture createSecurityGroup(CreateSecurityGroupRequest request);

    /**
     * description :
     * 
You can use the ECS console, call ECS API operations, or use CloudMonitor to view the scheduled simulated system events.
     * The following descriptions provide the lifecycle of a simulated system event:
     * 

     * 
Scheduled: The state of the simulated system event is automatically changed to Scheduled after it is scheduled.
     * 
Executed: The state of the simulated system event is automatically changed to Executed at the time specified by the NotBefore parameter if no manual intervention is involved.
     * 
Canceled: The state of the simulated system event is changed to Canceled if you cancel the event by calling the CancelSimulatedSystemEvents operation.
     * 
Avoided: The state of the simulated system event generated from maintenance-triggered instance restart can be changed to Avoided if you restart the instance before the scheduled time of the simulated system event. The maintenance-triggered instance restart is indicated by the SystemMaintenance.Reboot value. For more information, see RebootInstance.
     * 
     * 
     * @param request the request parameters of CreateSimulatedSystemEvents  CreateSimulatedSystemEventsRequest
     * @return CreateSimulatedSystemEventsResponse
     */
    CompletableFuture createSimulatedSystemEvents(CreateSimulatedSystemEventsRequest request);

    /**
     * description :
     * 
The local snapshot feature is replaced by the instant access feature. Take note of the following items:
     * 

     * 
If you have used the local snapshot feature before December 14, 2020, you can use Category.
     * 
If you have not used the local snapshot feature before December 14, 2020, new snapshots of your Enterprise SSD (ESSD) series disks are instantly available after creation without the need for additional configurations, regardless of whether the snapshots are manually or automatically created. ESSD-series disks include ESSDs, ESSD AutoPL disks, ESSD Entry disks, and Regional ESSDs. InstantAccess, InstantAccessRetentionDays, and DisableInstantAccess that are related to the instant access feature no longer take effect in API operations. Available is added to the DescribeSnapshots and DescribeSnapshotGroups operations to indicate whether snapshots are available.
     * Prerequisites:
     * 
Elastic Compute Service (ECS) Snapshot is activated. For more information, see Activate ECS Snapshot.
     * 
The disk for which you want to create a snapshot is in the In_use or Available state. Take note of the following items:

     * 
If the disk is in the In_use state, make sure that the ECS instance to which the disk is attached is in the Running or Stopped state.
     * 
If the disk is in the Available state, make sure that the disk was attached to an ECS instance. Snapshots cannot be created for disks that have never been attached to an ECS instance.
     * 
When you use a disk to create a dynamic extended volume or a RAID array, we recommend that you create a snapshot-consistent group and enable the application-consistent snapshot feature to back up data. When a business system involves multiple disks, you can create a snapshot-consistent group to ensure a consistent write order and the crash consistency of business system data. For more information, see Create a snapshot-consistent group and Create application-consistent snapshots.
     * When you create a snapshot, take note of the following items:
     * 
     * 
     * 
We recommend that you create snapshots during off-peak hours because snapshot creation degrades disk I/O performance by up to 10% and slows down data reads and writes.
     * 
If a snapshot is being created, you cannot use this snapshot to create a custom image by calling the CreateImage operation.
     * 
If operations are performed on the disk and incremental data is generated when a snapshot is being created, the incremental data is not included in the snapshot.
     * 
When a snapshot is being created for a disk that is attached to an ECS instance, do not perform operations that change the status of the instance, such as stopping or restarting the instance. Otherwise, the snapshot may fail to be created.
     * 
You cannot resize a disk for which a snapshot is being created. Wait until the snapshot is created before you resize the disk.
     * 
You can create snapshots for a disk that is in the Expired (Expired) state. If the release time scheduled for a disk arrives while a snapshot is being created for the disk, the snapshot is in the Creating (Creating) state and is deleted when the disk is released.
     * 
After you create snapshots, you are charged snapshot storage fees per region based on the total size of the snapshots that are stored in the region. For more information, see Snapshots.
     * 
In the following scenarios, you cannot create snapshots for a disk:

     * 
The number of manual snapshots of the disk has reached 256.
     * 
A snapshot is being created for the disk.
     * 
If the response contains {"OperationLocks": {"LockReason" : "security"}} when you query information about an ECS instance, the instance is locked for security reasons and no operations are allowed on the instance.
     * 
     * 
     * 
     * 
     * @param request the request parameters of CreateSnapshot  CreateSnapshotRequest
     * @return CreateSnapshotResponse
     */
    CompletableFuture createSnapshot(CreateSnapshotRequest request);

    /**
     * description :
     * 
You can specify InstanceId to create a snapshot-consistent group for disks on a specific ECS instance. You can also specify DiskId.N to create a snapshot-consistent group for multiple disks on multiple ECS instances within the same zone.
     * 

     * 
 You cannot specify both DiskId.N and ExcludeDiskId.N in the same request. If you specify InstanceId, you can use DiskId.N to specify only disks on the specified ECS instance and cannot use DiskId.N to specify disks across ECS instances.
     * Take note of the following items:
     * 
     * 

     * 
The disks for which you want to create a snapshot must be in the In Use (In_use) or Unattached (Available) state.

     * 
If a disk is in the In Use (In_use) state, make sure that the ECS instance to which the disk is attached is in the Running (Running) or Stopped (Stopped) state.
     * 
If a disk is in the Unattached (Available) state, make sure that the disk has been attached to ECS instances. Snapshots cannot be created for disks that have never been attached to an ECS instance.
     * 
     * 
     * 
Snapshot-consistent groups can be used to create snapshots only for Enterprise SSDs (ESSDs), ESSD AutoPL disks, and ESSD Entry disks.
     * 
A snapshot-consistent group can contain snapshots of up to 16 disks, including system disks and data disks, and cannot exceed 32 TiB in size.
     * 
Snapshots that you created are stored indefinitely until you delete the snapshots. We recommend that you delete unnecessary snapshots on a regular basis to prevent excess snapshot storage fees.
     * 
Snapshot-consistent groups cannot be created for disks for which multi-attach feature is enabled. If disks for which the multi-attach feature is enabled are attached to an ECS instance, you must specify the ExcludeDiskId.N parameter to exclude the disks.
     * For more information about the snapshot-consistent group feature, see Create a snapshot-consistent group.
     * 
     * 
     * @param request the request parameters of CreateSnapshotGroup  CreateSnapshotGroupRequest
     * @return CreateSnapshotGroupResponse
     */
    CompletableFuture createSnapshotGroup(CreateSnapshotGroupRequest request);

    /**
     * description :
     * 
A storage set can distribute disks or Shared Block Storage devices to different locations. You can specify the number of partitions in a storage set. A larger number of partitions indicate more discrete distribution of disks or Shared Block Storage devices.
     * When you call this operation, take note of the following items:
     * 

     * 
The number of storage sets that you can create in a region is limited. You can call the DescribeAccountAttributes operation to query the limit.
     * 
The number of partitions in a zone is limited. You can call the DescribeAccountAttributes operation to query the limit.
     * 
     * 
     * @param request the request parameters of CreateStorageSet  CreateStorageSetRequest
     * @return CreateStorageSetResponse
     */
    CompletableFuture createStorageSet(CreateStorageSetRequest request);

    /**
     * @deprecated OpenAPI CreateVSwitch is deprecated  * @param request  the request parameters of CreateVSwitch  CreateVSwitchRequest
     * @return CreateVSwitchResponse
     */
    @Deprecated
    CompletableFuture createVSwitch(CreateVSwitchRequest request);

    /**
     * @deprecated OpenAPI CreateVirtualBorderRouter is deprecated  * @param request  the request parameters of CreateVirtualBorderRouter  CreateVirtualBorderRouterRequest
     * @return CreateVirtualBorderRouterResponse
     */
    @Deprecated
    CompletableFuture createVirtualBorderRouter(CreateVirtualBorderRouterRequest request);

    /**
     * @deprecated OpenAPI CreateVpc is deprecated, please use Vpc::2016-04-28::CreateVpc instead.  * @param request  the request parameters of CreateVpc  CreateVpcRequest
     * @return CreateVpcResponse
     */
    @Deprecated
    CompletableFuture createVpc(CreateVpcRequest request);

    /**
     * @deprecated OpenAPI DeactivateRouterInterface is deprecated  * @param request  the request parameters of DeactivateRouterInterface  DeactivateRouterInterfaceRequest
     * @return DeactivateRouterInterfaceResponse
     */
    @Deprecated
    CompletableFuture deactivateRouterInterface(DeactivateRouterInterfaceRequest request);

    /**
     * description :
     * 
$.parameters[4].schema.description
     * 
     * @param request the request parameters of DeleteActivation  DeleteActivationRequest
     * @return DeleteActivationResponse
     */
    CompletableFuture deleteActivation(DeleteActivationRequest request);

    /**
     * @param request the request parameters of DeleteAutoProvisioningGroup  DeleteAutoProvisioningGroupRequest
     * @return DeleteAutoProvisioningGroupResponse
     */
    CompletableFuture deleteAutoProvisioningGroup(DeleteAutoProvisioningGroupRequest request);

    /**
     * @param request the request parameters of DeleteAutoSnapshotPolicy  DeleteAutoSnapshotPolicyRequest
     * @return DeleteAutoSnapshotPolicyResponse
     */
    CompletableFuture deleteAutoSnapshotPolicy(DeleteAutoSnapshotPolicyRequest request);

    /**
     * @deprecated OpenAPI DeleteBandwidthPackage is deprecated  * @param request  the request parameters of DeleteBandwidthPackage  DeleteBandwidthPackageRequest
     * @return DeleteBandwidthPackageResponse
     */
    @Deprecated
    CompletableFuture deleteBandwidthPackage(DeleteBandwidthPackageRequest request);

    /**
     * @param request the request parameters of DeleteCommand  DeleteCommandRequest
     * @return DeleteCommandResponse
     */
    CompletableFuture deleteCommand(DeleteCommandRequest request);

    /**
     * @param request the request parameters of DeleteDedicatedHostCluster  DeleteDedicatedHostClusterRequest
     * @return DeleteDedicatedHostClusterResponse
     */
    CompletableFuture deleteDedicatedHostCluster(DeleteDedicatedHostClusterRequest request);

    /**
     * @deprecated OpenAPI DeleteDemand is deprecated, please use Ecs::2014-05-26::ReleaseCapacityReservation instead.  * @description >  This operation is in internal preview and has not been officially released. We recommend that you avoid using this operation.
     * 
     * @param request the request parameters of DeleteDemand  DeleteDemandRequest
     * @return DeleteDemandResponse
     */
    @Deprecated
    CompletableFuture deleteDemand(DeleteDemandRequest request);

    /**
     * description :
     * 
Before you delete a deployment set, make sure that no instances exist in the deployment set. If instances exist in the deployment set, move the instances to a different deployment set or release the instances before you delete the deployment set. For more information, see Change the deployment set of an instance and Release an ECS instance.
     * 
     * @param request the request parameters of DeleteDeploymentSet  DeleteDeploymentSetRequest
     * @return DeleteDeploymentSetResponse
     */
    CompletableFuture deleteDeploymentSet(DeleteDeploymentSetRequest request);

    /**
     * @param request the request parameters of DeleteDiagnosticMetricSets  DeleteDiagnosticMetricSetsRequest
     * @return DeleteDiagnosticMetricSetsResponse
     */
    CompletableFuture deleteDiagnosticMetricSets(DeleteDiagnosticMetricSetsRequest request);

    /**
     * description :
     * 
You can call this operation to delete the diagnostic reports that are no longer needed.
     * 
     * @param request the request parameters of DeleteDiagnosticReports  DeleteDiagnosticReportsRequest
     * @return DeleteDiagnosticReportsResponse
     */
    CompletableFuture deleteDiagnosticReports(DeleteDiagnosticReportsRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
Manual snapshots of the disk are retained.
     * 
You can call the ModifyDiskAttribute operation to configure whether to retain automatic snapshots of the disk or release the snapshots along with the disk. We recommend that you delete the snapshots that are no longer needed to maintain a sufficient quota for new automatic snapshots.
     * 
The disk must be in the Unattached (Available) state.
     * 
If the specified DiskId parameter does not exist, the request is ignored.
     * 
     * 
     * @param request the request parameters of DeleteDisk  DeleteDiskRequest
     * @return DeleteDiskResponse
     */
    CompletableFuture deleteDisk(DeleteDiskRequest request);

    /**
     * @deprecated OpenAPI DeleteForwardEntry is deprecated  * @param request  the request parameters of DeleteForwardEntry  DeleteForwardEntryRequest
     * @return DeleteForwardEntryResponse
     */
    @Deprecated
    CompletableFuture deleteForwardEntry(DeleteForwardEntryRequest request);

    /**
     * @deprecated OpenAPI DeleteHaVip is deprecated  * @param request  the request parameters of DeleteHaVip  DeleteHaVipRequest
     * @return DeleteHaVipResponse
     */
    @Deprecated
    CompletableFuture deleteHaVip(DeleteHaVipRequest request);

    /**
     * @param request the request parameters of DeleteHpcCluster  DeleteHpcClusterRequest
     * @return DeleteHpcClusterResponse
     */
    CompletableFuture deleteHpcCluster(DeleteHpcClusterRequest request);

    /**
     * description :
     * 
For information about scenarios in which you cannot delete a custom image and the considerations related to custom image deletion, see Delete a custom image.
     * 
     * @param request the request parameters of DeleteImage  DeleteImageRequest
     * @return DeleteImageResponse
     */
    CompletableFuture deleteImage(DeleteImageRequest request);

    /**
     * description :
     * 
Only custom image components can be deleted.
     * 
     * @param request the request parameters of DeleteImageComponent  DeleteImageComponentRequest
     * @return DeleteImageComponentResponse
     */
    CompletableFuture deleteImageComponent(DeleteImageComponentRequest request);

    /**
     * description :
     * 
If an image build task based on an image template is in the BUILDING, DISTRIBUTING, RELEASING, or CANCELLING state, you cannot delete the image template. You can delete the image template only when the image build task is in the SUCCESS, FAILED, or CANCELLED state. You can call the DescribeImagePipelineExecutions operation to query the details of an image build task.
     * 
     * @param request the request parameters of DeleteImagePipeline  DeleteImagePipelineRequest
     * @return DeleteImagePipelineResponse
     */
    CompletableFuture deleteImagePipeline(DeleteImagePipelineRequest request);

    /**
     * description :
     * 

     * 
Warning After an instance is released, all physical resources used by the instance are recycled. Relevant data is erased and cannot be restored.
     * 
Precautions
     * When you release an instance, manual snapshots of the cloud disks are retained. The settings configured during the creation of the instance determine whether the cloud disks attached to the instance and automatic snapshots are released. Before you release the instance, you can call the DescribeDisks operation to query the parameter settings for the cloud disks attached to the instance and the automatic snapshots.

     * 
The cloud disks for which DeleteWithInstance is set to false are retained as pay-as-you-go disks after the instance is released. The cloud disks for which DeleteWithInstance is set to true are released along with the instance.
     * 
If DeleteAutoSnapshot is set to false for a cloud disk attached to the instance, the automatic snapshots of the cloud disk are retained when the instance is released. If DeleteAutoSnapshot is set to true for the cloud disk, the cloud disk is released along with the instance.

     * 
 When you release an instance that is locked for security reasons, the cloud disks attached to the instance are released even if DeleteWithInstance is set to false.
     * 
     * 
     * 
     * 
     * 
     * 
     * @param request the request parameters of DeleteInstance  DeleteInstanceRequest
     * @return DeleteInstanceResponse
     */
    CompletableFuture deleteInstance(DeleteInstanceRequest request);

    /**
     * description :
     * 

     * 
Warning After an ECS instance is released, all physical resources used by the instance are reclaimed. Relevant data is erased and cannot be restored.
     * After an ECS instance is released, the manual snapshots of the disks attached to the instance are retained. Whether the disks and the automatic snapshots of the disks are released is determined by the options that you configured when you created the instance and disks. Before you release an ECS instance, you can call the DescribeDisks operation to query the parameters of the disks attached to the instance and the automatic snapshots.
     * 
If DeleteWithInstance is set to false, the disks are changed to pay-as-you-go disks and retained. If DeleteWithInstance is set to true, the disks are released along with the instance.
     * 
If DeleteAutoSnapshot is set to false, the automatic snapshots are retained. If DeleteAutoSnapshot is set to true, the automatic snapshots are released along with the instance.

     * 
 If an ECS instance is locked for security reasons, the disks attached to the instance are released along with the instance even if DeleteWithInstance is set to false for the disks.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DeleteInstances  DeleteInstancesRequest
     * @return DeleteInstancesResponse
     */
    CompletableFuture deleteInstances(DeleteInstancesRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
After an SSH key pair is deleted, you cannot query the SSH key pair by calling the DescribeKeyPairs operation.
     * 
If an SSH key pair is bound to one or more Elastic Compute Service (ECS) instances, the SSH key pair cannot be deleted.
     * 
     * 
     * @param request the request parameters of DeleteKeyPairs  DeleteKeyPairsRequest
     * @return DeleteKeyPairsResponse
     */
    CompletableFuture deleteKeyPairs(DeleteKeyPairsRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
After you delete a launch template, Elastic Compute Service (ECS) instances created based on the launch template are not affected.
     * 
After you delete a launch template, all versions of the launch template are deleted and cannot be restored. If you want to delete only a specific version of the launch template, call the DeleteLaunchTemplateVersion operation.
     * 
     * 
     * @param request the request parameters of DeleteLaunchTemplate  DeleteLaunchTemplateRequest
     * @return DeleteLaunchTemplateResponse
     */
    CompletableFuture deleteLaunchTemplate(DeleteLaunchTemplateRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
You cannot delete the default version of a launch template by calling this operation. To delete the default version of a launch template, you must delete the launch template.
     * 
If the version of a launch template that you want to delete is the default version, call the ModifyLaunchTemplateDefaultVersion operation or go to the Launch Templates page in the Elastic Compute Service (ECS) console to change the default version to a different version, and then delete the original default version.
     * 
After you delete a version of a launch template, the ECS instances that were created based on the version are not affected.
     * 
     * 
     * @param request the request parameters of DeleteLaunchTemplateVersion  DeleteLaunchTemplateVersionRequest
     * @return DeleteLaunchTemplateVersionResponse
     */
    CompletableFuture deleteLaunchTemplateVersion(DeleteLaunchTemplateVersionRequest request);

    /**
     * @deprecated OpenAPI DeleteNatGateway is deprecated  * @param request  the request parameters of DeleteNatGateway  DeleteNatGatewayRequest
     * @return DeleteNatGatewayResponse
     */
    @Deprecated
    CompletableFuture deleteNatGateway(DeleteNatGatewayRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The ENI to be deleted must be in the Available state.
     * 
If the ENI to be deleted is attached to an Elastic Compute Service (ECS) instance, you must detach the ENI from the instance before you can delete the ENI. To detach the ENI, you can call the DetachNetworkInterface operation.
     * 
After an ENI is deleted, the following situations occur:

     * 
All private IP addresses (including primary and secondary private IP addresses) of the ENI are automatically released.
     * 
The ENI is automatically removed from all security groups.
     * 
     * 
     * 
The DeleteNetworkInterface operation is an asynchronous operation. After this operation is called to delete an ENI, you can check the status or events of the ENI to determine whether the ENI is deleted. The following figure shows the transitions between the states of the ENI.
     * 

     * 
If the ENI is in the Deleting state, the ENI deletion request is sent and the ENI is being deleted.
     * 
If the ENI is not found, the ENI is deleted.
     * 
If the ENI is stuck in the Deleting state, the ENI fails to be deleted. You can re-initiate the request to delete the ENI.
     * For information about examples on how to call the DeleteNetworkInterface operation, see Delete an ENI.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DeleteNetworkInterface  DeleteNetworkInterfaceRequest
     * @return DeleteNetworkInterfaceResponse
     */
    CompletableFuture deleteNetworkInterface(DeleteNetworkInterfaceRequest request);

    /**
     * @deprecated OpenAPI DeleteNetworkInterfacePermission is deprecated, please use Ecs::2014-05-26::DeleteNetworkInterface instead.  * @param request  the request parameters of DeleteNetworkInterfacePermission  DeleteNetworkInterfacePermissionRequest
     * @return DeleteNetworkInterfacePermissionResponse
     */
    @Deprecated
    CompletableFuture deleteNetworkInterfacePermission(DeleteNetworkInterfacePermissionRequest request);

    /**
     * @deprecated OpenAPI DeletePhysicalConnection is deprecated  * @param request  the request parameters of DeletePhysicalConnection  DeletePhysicalConnectionRequest
     * @return DeletePhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture deletePhysicalConnection(DeletePhysicalConnectionRequest request);

    /**
     * description :
     * 
If a prefix list is associated with resources, you cannot delete the prefix list. You must disassociate the prefix list from the resources before you delete the prefix list. You can call the DescribePrefixListAssociations operation to query resources that are associated with a specific prefix list.
     * 
     * @param request the request parameters of DeletePrefixList  DeletePrefixListRequest
     * @return DeletePrefixListResponse
     */
    CompletableFuture deletePrefixList(DeletePrefixListRequest request);

    /**
     * @deprecated OpenAPI DeleteRouteEntry is deprecated  * @param request  the request parameters of DeleteRouteEntry  DeleteRouteEntryRequest
     * @return DeleteRouteEntryResponse
     */
    @Deprecated
    CompletableFuture deleteRouteEntry(DeleteRouteEntryRequest request);

    /**
     * @deprecated OpenAPI DeleteRouterInterface is deprecated  * @param request  the request parameters of DeleteRouterInterface  DeleteRouterInterfaceRequest
     * @return DeleteRouterInterfaceResponse
     */
    @Deprecated
    CompletableFuture deleteRouterInterface(DeleteRouterInterfaceRequest request);

    /**
     * description :
     * 
  Make sure that no Elastic Compute Service (ECS) instances exist in the security group. You can query instances by calling the DescribeInstances operation.
     * 

     * 
Make sure that no elastic network interfaces (ENIs) exist in the security group. You can query ENIs by calling the DescribeNetworkInterfaces operation.
     * 
Make sure that the security group that you want to delete is not referenced by rules of other security groups. You can query the associations by calling the DescribeSecurityGroupReferences operation.
     * 
If the InvalidOperation.DeletionProtection error code is returned when you call the DeleteSecurityGroup operation to delete a security group, the deletion protection feature is enabled for the security group. When you create a Container Service for Kubernetes (ACK) cluster, the deletion protection feature is enabled for an associated security group to prevent accidental deletion. You cannot manually disable the deletion protection feature for the security group. The deletion protection feature can be automatically disabled only after the ACK cluster is deleted. For more information, see the Disable deletion protection for a security group section of the "Configure and manage security groups for an ACK cluster" topic.
     * 
     * 
     * @param request the request parameters of DeleteSecurityGroup  DeleteSecurityGroupRequest
     * @return DeleteSecurityGroupResponse
     */
    CompletableFuture deleteSecurityGroup(DeleteSecurityGroupRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
If the snapshot does not exist, the request is ignored.
     * 
If the snapshot has been used to create custom images, the snapshot cannot be deleted. You need to call the DeleteImage operation to delete the custom images before you can delete the snapshot.
     * 
If the snapshot has been used to create disks and Force is not specified or is set to false, the snapshot cannot be deleted directly. If you want to delete the snapshot, set Force to true to forcibly delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is forcibly deleted.
     * 
     * 
     * @param request the request parameters of DeleteSnapshot  DeleteSnapshotRequest
     * @return DeleteSnapshotResponse
     */
    CompletableFuture deleteSnapshot(DeleteSnapshotRequest request);

    /**
     * description :
     * 
Usage notes
     * 
If a disk snapshot that is contained in a snapshot-consistent group has been used to create a custom image, the disk snapshot is retained after the snapshot-consistent group is deleted. Before you can delete the disk snapshot, you must call the DeleteImage operation to delete the custom image. Then, you can call the DeleteSnapshot operation to delete the disk snapshot.
     * 
     * @param request the request parameters of DeleteSnapshotGroup  DeleteSnapshotGroupRequest
     * @return DeleteSnapshotGroupResponse
     */
    CompletableFuture deleteSnapshotGroup(DeleteSnapshotGroupRequest request);

    /**
     * @param request the request parameters of DeleteStorageSet  DeleteStorageSetRequest
     * @return DeleteStorageSetResponse
     */
    CompletableFuture deleteStorageSet(DeleteStorageSetRequest request);

    /**
     * @deprecated OpenAPI DeleteVSwitch is deprecated  * @param request  the request parameters of DeleteVSwitch  DeleteVSwitchRequest
     * @return DeleteVSwitchResponse
     */
    @Deprecated
    CompletableFuture deleteVSwitch(DeleteVSwitchRequest request);

    /**
     * @deprecated OpenAPI DeleteVirtualBorderRouter is deprecated  * @param request  the request parameters of DeleteVirtualBorderRouter  DeleteVirtualBorderRouterRequest
     * @return DeleteVirtualBorderRouterResponse
     */
    @Deprecated
    CompletableFuture deleteVirtualBorderRouter(DeleteVirtualBorderRouterRequest request);

    /**
     * @deprecated OpenAPI DeleteVpc is deprecated, please use Vpc::2016-04-28::DeleteVpc instead.  * @param request  the request parameters of DeleteVpc  DeleteVpcRequest
     * @return DeleteVpcResponse
     */
    @Deprecated
    CompletableFuture deleteVpc(DeleteVpcRequest request);

    /**
     * @param request the request parameters of DeregisterManagedInstance  DeregisterManagedInstanceRequest
     * @return DeregisterManagedInstanceResponse
     */
    CompletableFuture deregisterManagedInstance(DeregisterManagedInstanceRequest request);

    /**
     * @deprecated OpenAPI DescribeAccessPoints is deprecated  * @param request  the request parameters of DescribeAccessPoints  DescribeAccessPointsRequest
     * @return DescribeAccessPointsResponse
     */
    @Deprecated
    CompletableFuture describeAccessPoints(DescribeAccessPointsRequest request);

    /**
     * description :
     * 
After you create an Alibaba Cloud account, you can create a specific number of ECS instances in different regions within the account. For more information, see Limits.
     * You can apply for a quota increase in the Quota Center console.
     * 
     * @param request the request parameters of DescribeAccountAttributes  DescribeAccountAttributesRequest
     * @return DescribeAccountAttributesResponse
     */
    CompletableFuture describeAccountAttributes(DescribeAccountAttributesRequest request);

    /**
     * description :
     * 
You can use one of the following methods to check the responses:
     * 

     * 
Method 1: When you call the DescribeActivations operation to retrieve the first page of results during a paged query, use MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which you can use in the next request to retrieve a new page of results. When you call the DescribeActivations operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and use MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page, and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * @param request the request parameters of DescribeActivations  DescribeActivationsRequest
     * @return DescribeActivationsResponse
     */
    CompletableFuture describeActivations(DescribeActivationsRequest request);

    /**
     * @param request the request parameters of DescribeAutoProvisioningGroupHistory  DescribeAutoProvisioningGroupHistoryRequest
     * @return DescribeAutoProvisioningGroupHistoryResponse
     */
    CompletableFuture describeAutoProvisioningGroupHistory(DescribeAutoProvisioningGroupHistoryRequest request);

    /**
     * @param request the request parameters of DescribeAutoProvisioningGroupInstances  DescribeAutoProvisioningGroupInstancesRequest
     * @return DescribeAutoProvisioningGroupInstancesResponse
     */
    CompletableFuture describeAutoProvisioningGroupInstances(DescribeAutoProvisioningGroupInstancesRequest request);

    /**
     * @param request the request parameters of DescribeAutoProvisioningGroups  DescribeAutoProvisioningGroupsRequest
     * @return DescribeAutoProvisioningGroupsResponse
     */
    CompletableFuture describeAutoProvisioningGroups(DescribeAutoProvisioningGroupsRequest request);

    /**
     * @param request the request parameters of DescribeAutoSnapshotPolicyEx  DescribeAutoSnapshotPolicyExRequest
     * @return DescribeAutoSnapshotPolicyExResponse
     */
    CompletableFuture describeAutoSnapshotPolicyEx(DescribeAutoSnapshotPolicyExRequest request);

    /**
     * description :
     * 
Usage notes
     * 
The value of DestinationResource determines whether you need to specify additional parameters. When you select a value in the following chain for DestinationResource, the more to the right the selected value is ordered, the more parameters you must specify.
     * 

     * 
Sequence: Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk
     * 
Examples:

     * 
If you set DestinationResource to DataDisk, take note of the following items:

     * 
If you set ResourceType to disk to query the categories of data disks that are not attached to ECS instances, you do not need to specify InstanceType.
     * 
If you set ResourceType to instance to query the categories of data disks that are purchased together with ECS instances, you must specify InstanceType and SystemDiskCategory due to instance type-specific limits on system disks and data disks.
     * 
     * 
     * 
If you set DestinationResource to SystemDisk and ResourceType to instance, you must specify InstanceType due to instance type-specific limits on system disks.
     * 
If you set DestinationResource to InstanceType, we recommend that you specify IoOptimized and InstanceType.
     * 
If you want to query the available ecs.g5.large resources in all zones of the China (Hangzhou) region, set RegionId to cn-hangzhou, DestinationResource to InstanceType, IoOptimized to optimized, and InstanceType to ecs.g5.large.
     * 
If you want to query the zones where ecs.g5.large resources are available in the China (Hangzhou) region, set RegionId to cn-hangzhou, DestinationResource to Zone, IoOptimized to optimized, and InstanceType to ecs.g5.large.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeAvailableResource  DescribeAvailableResourceRequest
     * @return DescribeAvailableResourceResponse
     */
    CompletableFuture describeAvailableResource(DescribeAvailableResourceRequest request);

    /**
     * @param request the request parameters of DescribeBandwidthLimitation  DescribeBandwidthLimitationRequest
     * @return DescribeBandwidthLimitationResponse
     */
    CompletableFuture describeBandwidthLimitation(DescribeBandwidthLimitationRequest request);

    /**
     * @deprecated OpenAPI DescribeBandwidthPackages is deprecated  * @param request  the request parameters of DescribeBandwidthPackages  DescribeBandwidthPackagesRequest
     * @return DescribeBandwidthPackagesResponse
     */
    @Deprecated
    CompletableFuture describeBandwidthPackages(DescribeBandwidthPackagesRequest request);

    /**
     * @param request the request parameters of DescribeCapacityReservationInstances  DescribeCapacityReservationInstancesRequest
     * @return DescribeCapacityReservationInstancesResponse
     */
    CompletableFuture describeCapacityReservationInstances(DescribeCapacityReservationInstancesRequest request);

    /**
     * @param request the request parameters of DescribeCapacityReservations  DescribeCapacityReservationsRequest
     * @return DescribeCapacityReservationsResponse
     */
    CompletableFuture describeCapacityReservations(DescribeCapacityReservationsRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
This operation applies only to instances that reside in the classic network.
     * 
You can query a maximum of 100 instances that reside in the classic network at a time.
     * 
At least one of the VpcId and InstanceId parameters must be configured.
     * 
     * 
     * @param request the request parameters of DescribeClassicLinkInstances  DescribeClassicLinkInstancesRequest
     * @return DescribeClassicLinkInstancesResponse
     */
    CompletableFuture describeClassicLinkInstances(DescribeClassicLinkInstancesRequest request);

    /**
     * @param request the request parameters of DescribeCloudAssistantSettings  DescribeCloudAssistantSettingsRequest
     * @return DescribeCloudAssistantSettingsResponse
     */
    CompletableFuture describeCloudAssistantSettings(DescribeCloudAssistantSettingsRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
Before you run commands on or send files to instances, especially new instances, we recommend that you query the status of Cloud Assistant on the instances by calling this operation and checking the return value of CloudAssistantStatus. Run commands on or send files to the instances only when the return value is true.
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: During a paged query, when you call the DescribeCloudAssistantStatus operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you call the DescribeCloudAssistantStatus operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeCloudAssistantStatus  DescribeCloudAssistantStatusRequest
     * @return DescribeCloudAssistantStatusResponse
     */
    CompletableFuture describeCloudAssistantStatus(DescribeCloudAssistantStatusRequest request);

    /**
     * @deprecated OpenAPI DescribeClusters is deprecated  * @param request  the request parameters of DescribeClusters  DescribeClustersRequest
     * @return DescribeClustersResponse
     */
    @Deprecated
    CompletableFuture describeClusters(DescribeClustersRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
If you specify only Action and RegionId, all available commands (CommandId) that you created in the specified region are queried by default.
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: During a paged query, when you call the DescribeCommands operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you call the DescribeCommands operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeCommands  DescribeCommandsRequest
     * @return DescribeCommandsResponse
     */
    CompletableFuture describeCommands(DescribeCommandsRequest request);

    /**
     * @param request the request parameters of DescribeDedicatedHostAutoRenew  DescribeDedicatedHostAutoRenewRequest
     * @return DescribeDedicatedHostAutoRenewResponse
     */
    CompletableFuture describeDedicatedHostAutoRenew(DescribeDedicatedHostAutoRenewRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can specify multiple request parameters to filter query results. Specified request parameters have logical AND relations. Only the specified parameters are included in the filter conditions. However, if DedicatedHostClusterIds is set to an empty JSON array ([]), this parameter is regarded as a valid filter condition and an empty result is returned.
     * 
     * @param request the request parameters of DescribeDedicatedHostClusters  DescribeDedicatedHostClustersRequest
     * @return DescribeDedicatedHostClustersResponse
     */
    CompletableFuture describeDedicatedHostClusters(DescribeDedicatedHostClustersRequest request);

    /**
     * @param request the request parameters of DescribeDedicatedHostTypes  DescribeDedicatedHostTypesRequest
     * @return DescribeDedicatedHostTypesResponse
     */
    CompletableFuture describeDedicatedHostTypes(DescribeDedicatedHostTypesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can use one of the following methods to query the information about dedicated hosts:
     * 

     * 
Specify DedicatedHostIds to query the details of specified dedicated hosts.
     * 
Specify DedicatedHostClusterId to query the details of dedicated hosts in a dedicated host cluster.
     * 
     * 
     * @param request the request parameters of DescribeDedicatedHosts  DescribeDedicatedHostsRequest
     * @return DescribeDedicatedHostsResponse
     */
    CompletableFuture describeDedicatedHosts(DescribeDedicatedHostsRequest request);

    /**
     * @deprecated OpenAPI DescribeDemands is deprecated, please use Ecs::2014-05-26::DescribeCapacityReservations instead.  * @description You can call this operation to query the details of resources that you filed with Alibaba Cloud, including the types, delivery status, and consumption details of the resources.
     * By default, the demands for I/O optimized instances of the Virtual Private Cloud (VPC) type are queried.
     * For information about how to create (CreateDemand), modify (ModifyDemand), and delete (DeleteDemand) demands for ECS resources, contact your account manager.
     * 
     * @param request the request parameters of DescribeDemands  DescribeDemandsRequest
     * @return DescribeDemandsResponse
     */
    @Deprecated
    CompletableFuture describeDemands(DescribeDemandsRequest request);

    /**
     * description :
     * 
Usage notes
     * 
For information about instance families, see Overview of instance families.
     * 
     * @param request the request parameters of DescribeDeploymentSetSupportedInstanceTypeFamily  DescribeDeploymentSetSupportedInstanceTypeFamilyRequest
     * @return DescribeDeploymentSetSupportedInstanceTypeFamilyResponse
     */
    CompletableFuture describeDeploymentSetSupportedInstanceTypeFamily(DescribeDeploymentSetSupportedInstanceTypeFamilyRequest request);

    /**
     * @param request the request parameters of DescribeDeploymentSets  DescribeDeploymentSetsRequest
     * @return DescribeDeploymentSetsResponse
     */
    CompletableFuture describeDeploymentSets(DescribeDeploymentSetsRequest request);

    /**
     * @param request the request parameters of DescribeDiagnosticMetricSets  DescribeDiagnosticMetricSetsRequest
     * @return DescribeDiagnosticMetricSetsResponse
     */
    CompletableFuture describeDiagnosticMetricSets(DescribeDiagnosticMetricSetsRequest request);

    /**
     * @param request the request parameters of DescribeDiagnosticMetrics  DescribeDiagnosticMetricsRequest
     * @return DescribeDiagnosticMetricsResponse
     */
    CompletableFuture describeDiagnosticMetrics(DescribeDiagnosticMetricsRequest request);

    /**
     * @param request the request parameters of DescribeDiagnosticReportAttributes  DescribeDiagnosticReportAttributesRequest
     * @return DescribeDiagnosticReportAttributesResponse
     */
    CompletableFuture describeDiagnosticReportAttributes(DescribeDiagnosticReportAttributesRequest request);

    /**
     * @param request the request parameters of DescribeDiagnosticReports  DescribeDiagnosticReportsRequest
     * @return DescribeDiagnosticReportsResponse
     */
    CompletableFuture describeDiagnosticReports(DescribeDiagnosticReportsRequest request);

    /**
     * @param request the request parameters of DescribeDiskDefaultKMSKeyId  DescribeDiskDefaultKMSKeyIdRequest
     * @return DescribeDiskDefaultKMSKeyIdResponse
     */
    CompletableFuture describeDiskDefaultKMSKeyId(DescribeDiskDefaultKMSKeyIdRequest request);

    /**
     * @param request the request parameters of DescribeDiskEncryptionByDefaultStatus  DescribeDiskEncryptionByDefaultStatusRequest
     * @return DescribeDiskEncryptionByDefaultStatusResponse
     */
    CompletableFuture describeDiskEncryptionByDefaultStatus(DescribeDiskEncryptionByDefaultStatusRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can query the following monitoring data of a disk: the read IOPS, write IOPS, read bandwidth (byte/s), write bandwidth (byte/s), read latency (microseconds), and write latency (microseconds).
     * Take note of the following items:
     * 

     * 
Monitoring data of only disks that are in the In Use (In_use) state can be queried. For more information, see Disk states.
     * **
     * Note Some information may be missing from the monitoring data of a disk because the disk is not in the In Use (In_use) state and the system cannot obtain the relevant information.
     * 
Up to 400 monitoring data entries can be returned at a time. Make sure that the TotalCount value does not exceed 400. The value is calculated by using the following formula: TotalCount = (EndTime - StartTime)/Period. If the TotalCount value is greater than 400, the InvalidParameter.TooManyDataQueried error is returned.
     * 
You can query the monitoring data in the last 30 days. If the value of StartTime is more than 30 days earlier than the current time, an error is returned.
     * 
     * 
     * @param request the request parameters of DescribeDiskMonitorData  DescribeDiskMonitorDataRequest
     * @return DescribeDiskMonitorDataResponse
     */
    CompletableFuture describeDiskMonitorData(DescribeDiskMonitorDataRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
You can specify multiple request parameters such as RegionId, ZoneId, DiskIds, and InstanceId as filters. The specified parameters are evaluated by using the "AND" operator. If you specify more than one filter, the records that match all filters are returned.
     * 
The value of DiskIds is a JSON array. If you do not specify DiskIds, the parameter is not used as a filter condition. If you set DiskIds to an empty JSON array, the parameter is regarded as a valid filter, and an empty result is returned.
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: Use NextToken to specify the pagination token. Set the value to the NextToken value that is obtained from the previous query. Then, use MaxResults to specify the maximum number of entries to return on each page.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page, and then use PageNumber to specify the number of the page to return.
     * You can use only one of the preceding methods. If a large number of entries are to be returned, we recommend that you use Method 1. If NextToken is specified, PageSize and PageNumber do not take effect and TotalCount in the response is invalid.
     * 
     * 
     * 
You can attach a disk for which the multi-attach feature is enabled to multiple instances. You can query the attachment information of the disk based on the Attachment values in the response.
     * When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see Parameter format overview.
     * 
     * 
     * @param request the request parameters of DescribeDisks  DescribeDisksRequest
     * @return DescribeDisksResponse
     */
    CompletableFuture describeDisks(DescribeDisksRequest request);

    /**
     * description :
     * 
  The full status information about an EBS device includes the lifecycle status specified by the Status parameter, health status specified by the HealthStatus parameter, and event type specified by the EventType parameter of the EBS device. You can filter the results based on these parameters.
     * 

     * 
The release time, scheduled execution time, and actual execution time of each EBS device event are identical. If you specify a period of time by using the EventTime.Start and EventTime.End parameters, all events that occurred within this period are queried. You can query events that occurred within the last seven days.
     * 
     * 
     * @param request the request parameters of DescribeDisksFullStatus  DescribeDisksFullStatusRequest
     * @return DescribeDisksFullStatusResponse
     */
    CompletableFuture describeDisksFullStatus(DescribeDisksFullStatusRequest request);

    /**
     * @deprecated OpenAPI DescribeEipAddresses is deprecated, please use Vpc::2016-04-28::DescribeEipAddresses instead.  * @param request  the request parameters of DescribeEipAddresses  DescribeEipAddressesRequest
     * @return DescribeEipAddressesResponse
     */
    @Deprecated
    CompletableFuture describeEipAddresses(DescribeEipAddressesRequest request);

    /**
     * @deprecated OpenAPI DescribeEipMonitorData is deprecated  * @param request  the request parameters of DescribeEipMonitorData  DescribeEipMonitorDataRequest
     * @return DescribeEipMonitorDataResponse
     */
    @Deprecated
    CompletableFuture describeEipMonitorData(DescribeEipMonitorDataRequest request);

    /**
     * description :
     * 
When an elasticity assurance expires, data about the association between the instances and the private pool generated by the elasticity assurance becomes invalid. When you call this operation to query the expired elasticity assurance, no value is returned.
     * 
     * @param request the request parameters of DescribeElasticityAssuranceInstances  DescribeElasticityAssuranceInstancesRequest
     * @return DescribeElasticityAssuranceInstancesResponse
     */
    CompletableFuture describeElasticityAssuranceInstances(DescribeElasticityAssuranceInstancesRequest request);

    /**
     * @param request the request parameters of DescribeElasticityAssurances  DescribeElasticityAssurancesRequest
     * @return DescribeElasticityAssurancesResponse
     */
    CompletableFuture describeElasticityAssurances(DescribeElasticityAssurancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
The monitoring data of a secondary ENI includes the amount of traffic sent and received over the internal network, the number of packets sent and received by the secondary ENI, and the number of sent and received packets that are dropped by the secondary ENI. Specific information may be missing from the returned monitoring data. This may be because the system cannot obtain the relevant information. For example, if the instance to which the secondary ENI is attached is in the Stopped state or if the secondary ENI is not attached to an instance and is in the Available state, the monitoring data of the secondary ENI cannot be obtained. Take note of the following items:
     * 

     * 
Up to 400 monitoring data entries can be returned at a time. Make sure that the TotalCount value does not exceed 400. The value is calculated by using the following formula: TotalCount = (EndTime - StartTime)/Period. If the TotalCount value is greater than 400, the InvalidParameter.TooManyDataQueried error is returned.
     * 
You can query the monitoring data in the last 30 days. If the value of StartTime is more than 30 days earlier than the current time, an error is returned.
     * 
     * 
     * @param request the request parameters of DescribeEniMonitorData  DescribeEniMonitorDataRequest
     * @return DescribeEniMonitorDataResponse
     */
    CompletableFuture describeEniMonitorData(DescribeEniMonitorDataRequest request);

    /**
     * @deprecated OpenAPI DescribeForwardTableEntries is deprecated  * @param request  the request parameters of DescribeForwardTableEntries  DescribeForwardTableEntriesRequest
     * @return DescribeForwardTableEntriesResponse
     */
    @Deprecated
    CompletableFuture describeForwardTableEntries(DescribeForwardTableEntriesRequest request);

    /**
     * @deprecated OpenAPI DescribeHaVips is deprecated  * @param request  the request parameters of DescribeHaVips  DescribeHaVipsRequest
     * @return DescribeHaVipsResponse
     */
    @Deprecated
    CompletableFuture describeHaVips(DescribeHaVipsRequest request);

    /**
     * @param request the request parameters of DescribeHpcClusters  DescribeHpcClustersRequest
     * @return DescribeHpcClustersResponse
     */
    CompletableFuture describeHpcClusters(DescribeHpcClustersRequest request);

    /**
     * description :
     * 
You can use NextToken to configure the query token. Set the value to the NextToken value that is returned in the previous call to the DescribeImageComponents operation. Then, use MaxResults to specify the maximum number of entries to return on each page.
     * 
     * @param request the request parameters of DescribeImageComponents  DescribeImageComponentsRequest
     * @return DescribeImageComponentsResponse
     */
    CompletableFuture describeImageComponents(DescribeImageComponentsRequest request);

    /**
     * description :
     * 
Description
     * 

     * 
This API operation only returns the available custom images that are newly created in the specified image family. Public images, Alibaba Cloud Marketplace images, community images, or shared images are not queried.
     * 
If no available custom images exist in the specified image family, the response is empty.
     * 
     * 
     * @param request the request parameters of DescribeImageFromFamily  DescribeImageFromFamilyRequest
     * @return DescribeImageFromFamilyResponse
     */
    CompletableFuture describeImageFromFamily(DescribeImageFromFamilyRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The image template that is specified by the ImagePipelineId parameter cannot be a deleted image template. When an image template is deleted, the corresponding image creation task is deleted.
     * 
You must specify ImagePipelineId or ExecutionId.
     * 
You can configure the query token by using the NextToken parameter. Set NextToken to the value of NextToken that was returned the previous call to the DescribeImagePipelineExecutions operation. Then, use the MaxResults parameter to specify the maximum number of entries to return on each page.
     * 
     * 
     * @param request the request parameters of DescribeImagePipelineExecutions  DescribeImagePipelineExecutionsRequest
     * @return DescribeImagePipelineExecutionsResponse
     */
    CompletableFuture describeImagePipelineExecutions(DescribeImagePipelineExecutionsRequest request);

    /**
     * description :
     * 
You can use NextToken to configure the query token. Set the value to the NextToken value that is returned in the previous call to the DescribeImagePipelines operation. Then, use MaxResults to specify the maximum number of entries to return on each page.
     * 
     * @param request the request parameters of DescribeImagePipelines  DescribeImagePipelinesRequest
     * @return DescribeImagePipelinesResponse
     */
    CompletableFuture describeImagePipelines(DescribeImagePipelinesRequest request);

    /**
     * @param request the request parameters of DescribeImageSharePermission  DescribeImageSharePermissionRequest
     * @return DescribeImageSharePermissionResponse
     */
    CompletableFuture describeImageSharePermission(DescribeImageSharePermissionRequest request);

    /**
     * @param request the request parameters of DescribeImageSupportInstanceTypes  DescribeImageSupportInstanceTypesRequest
     * @return DescribeImageSupportInstanceTypesResponse
     */
    CompletableFuture describeImageSupportInstanceTypes(DescribeImageSupportInstanceTypesRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
You can query your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images from other Alibaba Cloud accounts.
     * 
This is a paginated query. The response contains the total number of available images and the images on the returned page. By default,10 entries are displayed on each page.
     * 
When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see Parameter formats.
     * 
If you set ImageOwnerAlias to system or others when you call the DescribeImages operation to query public images that are provided by Alibaba Cloud or shared images, Resource Access Management (RAM) policies are ignored in the request. For more information, see RAM authorization.
     * 
     * 
     * @param request the request parameters of DescribeImages  DescribeImagesRequest
     * @return DescribeImagesResponse
     */
    CompletableFuture describeImages(DescribeImagesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After an elasticity assurance or a capacity reservation is created, a private pool is generated and associated with information about the instances that are created by using the private pool. You can specify a private pool when you create an instance. This way, the instance matches the elasticity assurance or capacity reservation that is associated with the private pool.
     * When a private pool expires, data related to the association between instances and the private pool becomes invalid. If you call this operation to query information about the private pool, empty values are returned.
     * 
     * @param request the request parameters of DescribeInstanceAttachmentAttributes  DescribeInstanceAttachmentAttributesRequest
     * @return DescribeInstanceAttachmentAttributesResponse
     */
    CompletableFuture describeInstanceAttachmentAttributes(DescribeInstanceAttachmentAttributesRequest request);

    /**
     * @param request the request parameters of DescribeInstanceAttribute  DescribeInstanceAttributeRequest
     * @return DescribeInstanceAttributeResponse
     */
    CompletableFuture describeInstanceAttribute(DescribeInstanceAttributeRequest request);

    /**
     * description :
     * 
  Before you configure auto-renewal or manual renewal for subscription instances, you can query the auto-renewal status of the instances.
     * 

     * 
This operation is applicable to only subscription instances. An error is returned if you call this operation on pay-as-you-go instances.
     * 
     * 
     * @param request the request parameters of DescribeInstanceAutoRenewAttribute  DescribeInstanceAutoRenewAttributeRequest
     * @return DescribeInstanceAutoRenewAttributeResponse
     */
    CompletableFuture describeInstanceAutoRenewAttribute(DescribeInstanceAutoRenewAttributeRequest request);

    /**
     * description :
     * 
  You can query system events that were completed within the last 30 days. No limits apply to the time range for querying uncompleted system events.
     * 

     * 
You can also specify InstanceEventCycleStatus to query the system events that are in the Scheduled, Executing, or Inquiring state.
     * 
     * 
     * @param request the request parameters of DescribeInstanceHistoryEvents  DescribeInstanceHistoryEventsRequest
     * @return DescribeInstanceHistoryEventsResponse
     */
    CompletableFuture describeInstanceHistoryEvents(DescribeInstanceHistoryEventsRequest request);

    /**
     * description :
     * 
This operation is used to query the specified maintenance policy of an instance, which contains the following maintenance attributes:
     * 

     * 
Maintenance window: the time period that you specify for maintenance.
     * 
Maintenance action: the action that you specify in response to instance shutdown.
     * 
     * 
     * @param request the request parameters of DescribeInstanceMaintenanceAttributes  DescribeInstanceMaintenanceAttributesRequest
     * @return DescribeInstanceMaintenanceAttributesResponse
     */
    CompletableFuture describeInstanceMaintenanceAttributes(DescribeInstanceMaintenanceAttributesRequest request);

    /**
     * description :
     * 
  Pricing information can be queried for unexpired subscription ECS instances only when you upgrade their configurations. The pricing information cannot be queried when the instance configurations are downgraded.
     * 

     * 
Pricing information cannot be queried for pay-as-you-go ECS instances when you change their configurations. Prices of existing pay-as-you-go ECS instances whose configurations are changed are the same as those of new pay-as-you-go instances. You can call the DescribePrice operation to query the latest prices of ECS instances.
     * 
Before you upgrade the configurations of an instance, we recommend that you call the DescribeResourcesModification operation to query the instance types available for configuration upgrades in a specified zone.
     * 
     * 
     * @param request the request parameters of DescribeInstanceModificationPrice  DescribeInstanceModificationPriceRequest
     * @return DescribeInstanceModificationPriceResponse
     */
    CompletableFuture describeInstanceModificationPrice(DescribeInstanceModificationPriceRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
Up to 400 monitoring data entries can be returned at a time. Make sure that the TotalCount value does not exceed 400. The value is calculated by using the following formula: TotalCount = (EndTime - StartTime)/Period. If the TotalCount value is greater than 400, the InvalidParameter.TooManyDataQueried error is returned.
     * 
You can query the monitoring data in the last 30 days. If the value of StartTime is more than 30 days earlier than the current time, an error is returned.
     * 
In some scenarios, such as when the instance is in the Stopped state, the system cannot obtain the relevant information and specific information may be missing from the returned monitoring data.
     * 
You cannot call this operation to obtain the CPU basic monitoring information of an ECS bare metal instance. To obtain the CPU monitoring information of an ECS bare metal instance, install the CloudMonitor agent on the instance. For more information, see InstallCloudMonitor.
     * 
     * 
     * @param request the request parameters of DescribeInstanceMonitorData  DescribeInstanceMonitorDataRequest
     * @return DescribeInstanceMonitorDataResponse
     */
    CompletableFuture describeInstanceMonitorData(DescribeInstanceMonitorDataRequest request);

    /**
     * description :
     * 
Usage notes
     * 
When you call the API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see Parameter formats.
     * 
     * @param request the request parameters of DescribeInstanceRamRole  DescribeInstanceRamRoleRequest
     * @return DescribeInstanceRamRoleResponse
     */
    CompletableFuture describeInstanceRamRole(DescribeInstanceRamRoleRequest request);

    /**
     * description :
     * 
For information about the lifecycle states of an ECS instance, see Instance lifecycle.
     * 
Sample requests
     * 

     * 
Query the ECS instances and the status of the instances in a specific region. Sample request:
     * "RegionID": "cn-hangzhou"
     * 
Query the ECS instances and the status of the instances in a zone of a specific region. Sample request:
     * 
  "RegionID": "cn-hangzhou",
     *   "ZoneID": "cn-hangzhou-a"
     * 
     * 
     * 
Query the status of an ECS instance based on the instance ID in a specific region. Sample request:
     * "RegionID": "cn-hangzhou",
     * "InstancesID": ["i-bp1f7c1zqp999zvp****", "i-bp1dqjv36biueg61****"]
     * 
     * 
     * @param request the request parameters of DescribeInstanceStatus  DescribeInstanceStatusRequest
     * @return DescribeInstanceStatusResponse
     */
    CompletableFuture describeInstanceStatus(DescribeInstanceStatusRequest request);

    /**
     * @param request the request parameters of DescribeInstanceTopology  DescribeInstanceTopologyRequest
     * @return DescribeInstanceTopologyResponse
     */
    CompletableFuture describeInstanceTopology(DescribeInstanceTopologyRequest request);

    /**
     * @param request the request parameters of DescribeInstanceTypeFamilies  DescribeInstanceTypeFamiliesRequest
     * @return DescribeInstanceTypeFamiliesResponse
     */
    CompletableFuture describeInstanceTypeFamilies(DescribeInstanceTypeFamiliesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
MaxResults specifies the maximum number of entries per page. The maximum value of this parameter is changed from 1600 to 100. As of November 15, 2023, only 100 can be used as the maximum value of MaxResults. If you called the DescribeInstanceTypes operation in 2022, you can use 1600 as the maximum value before November 15, 2023. If you do not specify NextToken when you call the DescribeInstanceTypes operation, only the first page of results that contains up to 100 entries is returned. If you want to retrieve more results, specify NextToken to perform paged queries, or specify filter conditions to filter results.
     * 
We recommend that you specify MaxResults and NextToken to perform paged queries. The first time you call the DescribeInstanceTypes operation, set MaxResults to limit the maximum number of entries that can be returned in a single call. If the number of entries to return exceeds the specified MaxResults value, the response includes a NextToken value. You can set NextToken to the return value and specify MaxResults in your next request to DescribeInstanceTypes to retrieve the next page of results.
     * 
The DescribeInstanceTypes operation is used to query only the specifications and performance information of instance types. To query instance types that are available in a specific region, call the DescribeAvailableResource operation.
     * 
To use special instance types such as instance types that are unavailable for purchase, submit a ticket.
     * 
     * 
     * @param request the request parameters of DescribeInstanceTypes  DescribeInstanceTypesRequest
     * @return DescribeInstanceTypesResponse
     */
    CompletableFuture describeInstanceTypes(DescribeInstanceTypesRequest request);

    /**
     * description :
     * 
  You cannot directly use the VNC logon address (VncUrl) in the response to log on to an ECS instance. To log on to the ECS instance, you can use the web management terminal URL that contains the VNC logon address.
     * 

     * 
 To construct a web management terminal URL, add the vncUrl=\\*\\*\\*\\*, instanceId=****, and isWindows=true/false parameters at the end of https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?. Separate each parameter with an ampersand (&). Parameter description:
     * 
     * 

     * 
vncUrl: the VNC logon address.
     * 
instanceId: the instance ID.
     * 
isWindows: specifies whether the operating system of your ECS instance is Windows. A value of true specifies that the operating system is Windows. A value of false specifies that the operating system is not Windows.
     * 
You can connect to an ECS instance without using a VNC logon password. Therefore, you do not need to specify the password parameter.
     * 
The keepalive time of a connection to a VNC management terminal is 300 seconds. If you do not interact with the VNC management terminal within 300 seconds, the VNC management terminal is automatically disconnected.
     * 
If the connection is interrupted, you must call the DescribeInstanceVncUrl operation to obtain a new VNC logon address (VncUrl) and use the new logon address to construct a new web management terminal URL that you can use to reconnect to the VNC management terminal. You can reconnect to a VNC management terminal up to 30 times per minute.
     * Sample web management terminal URL:
     * https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?vncUrl=ws%3A%2F%****&instanceId=i-wz9hhwq5a6tm****&isWindows=true
     * 
     * 
     * @param request the request parameters of DescribeInstanceVncUrl  DescribeInstanceVncUrlRequest
     * @return DescribeInstanceVncUrlResponse
     */
    CompletableFuture describeInstanceVncUrl(DescribeInstanceVncUrlRequest request);

    /**
     * description :
     * 
Limits
     * 

     * 
When you call the API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see Parameter format overview.
     * 
If you use a Resource Access Management (RAM) user or RAM role that does not have the permissions to call this operation, an empty list is returned.
     * 
     * 
Suggestions
     * 

     * 
Specify DryRun in the request to perform a dry run. In the dry run, the system checks the validity and authorization status of the parameters.
     * 
During a paged query, when you call the DescribeInstances operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInstances operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
     * 
     * @param request the request parameters of DescribeInstances  DescribeInstancesRequest
     * @return DescribeInstancesResponse
     */
    CompletableFuture describeInstances(DescribeInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
The response includes the instance status and the instance system events that are in the Scheduled state.
     * You can specify a period of time to query events that occurred within the period of time.
     * 
     * @param request the request parameters of DescribeInstancesFullStatus  DescribeInstancesFullStatusRequest
     * @return DescribeInstancesFullStatusResponse
     */
    CompletableFuture describeInstancesFullStatus(DescribeInstancesFullStatusRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
     * 
You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
     * 
You can subscribe to Cloud Assistant task status events to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: During a paged query, when you call the DescribeInvocationResults operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you call the DescribeInvocationResults operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries per page, and then use PageNumber to specify the page number. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * 
Comparison between the DescribeInvocations and DescribeInvocationResults operations:

     * 
Scenario in which the RunCommand or InvokeCommand operation is called to run a Cloud Assistant command on multiple instances:

     * 
The DescribeInvocations operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
     * 
The DescribeInvocationResults operation queries only the execution status of the command on each instance.
     * 
     * 
     * 
Scenario in which the RunCommand or InvokeCommand operation is called to run a Cloud Assistant command on a single instance:

     * 
The DescribeInvocations operation is equivalent to the DescribeInvocationResults operation.
     * 
     * 
     * 
If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (RepeatMode is set to Period or EveryReboot), you can call only the DescribeInvocationResults operation and must set IncludeHistory to true. The DescribeInvocations operation queries only the most recent execution status of the command.
     * 
If you want to view the command content and parameters, you can call only the DescribeInvocations operation and check the CommandContent value in the response.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeInvocationResults  DescribeInvocationResultsRequest
     * @return DescribeInvocationResultsResponse
     */
    CompletableFuture describeInvocationResults(DescribeInvocationResultsRequest request);

    /**
     * description :
     * 
  After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
     * 

     * 
You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
     * 
You can subscribe to Cloud Assistant task status events to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
     * 
During a paged query, when you call the DescribeInvocations operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInvocations operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Differences between the DescribeInvocations and DescribeInvocationResults operations:

     * 
Scenario in which the RunCommand or InvokeCommand operation is called to run a Cloud Assistant command on multiple instances:

     * 
The DescribeInvocations operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
     * 
The DescribeInvocationResults operation queries only the execution status of the command on each instance.
     * 
     * 
     * 
Scenario in which the RunCommand or InvokeCommand operation is called to run a Cloud Assistant command on a single instance:

     * 
The DescribeInvocations operation is equivalent to the DescribeInvocationResults operation.
     * 
     * 
     * 
If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (RepeatMode is set to Period or EveryReboot), you can call only the DescribeInvocationResults operation and must set IncludeHistory to true. The DescribeInvocations operation queries only the most recent execution status of the command.
     * 
If you want to view the command content and parameters, you can call only the DescribeInvocations operation and check the CommandContent value in the response.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeInvocations  DescribeInvocationsRequest
     * @return DescribeInvocationsResponse
     */
    CompletableFuture describeInvocations(DescribeInvocationsRequest request);

    /**
     * @param request the request parameters of DescribeKeyPairs  DescribeKeyPairsRequest
     * @return DescribeKeyPairsResponse
     */
    CompletableFuture describeKeyPairs(DescribeKeyPairsRequest request);

    /**
     * description :
     * 
Debugging
     * 
OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.
     * 
     * @param request the request parameters of DescribeLaunchTemplateVersions  DescribeLaunchTemplateVersionsRequest
     * @return DescribeLaunchTemplateVersionsResponse
     */
    CompletableFuture describeLaunchTemplateVersions(DescribeLaunchTemplateVersionsRequest request);

    /**
     * @param request the request parameters of DescribeLaunchTemplates  DescribeLaunchTemplatesRequest
     * @return DescribeLaunchTemplatesResponse
     */
    CompletableFuture describeLaunchTemplates(DescribeLaunchTemplatesRequest request);

    /**
     * @deprecated OpenAPI DescribeLimitation is deprecated  * @param request  the request parameters of DescribeLimitation  DescribeLimitationRequest
     * @return DescribeLimitationResponse
     */
    @Deprecated
    CompletableFuture describeLimitation(DescribeLimitationRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can use one of the following methods to check the responses:
     * 

     * 
Method 1: During a paged query, when you call the DescribeManagedInstances operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you call the DescribeManagedInstances operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * @param request the request parameters of DescribeManagedInstances  DescribeManagedInstancesRequest
     * @return DescribeManagedInstancesResponse
     */
    CompletableFuture describeManagedInstances(DescribeManagedInstancesRequest request);

    /**
     * @deprecated OpenAPI DescribeNatGateways is deprecated  * @param request  the request parameters of DescribeNatGateways  DescribeNatGatewaysRequest
     * @return DescribeNatGatewaysResponse
     */
    @Deprecated
    CompletableFuture describeNatGateways(DescribeNatGatewaysRequest request);

    /**
     * description :
     * 
Debugging
     * 
OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.
     * 
     * @param request the request parameters of DescribeNetworkInterfaceAttribute  DescribeNetworkInterfaceAttributeRequest
     * @return DescribeNetworkInterfaceAttributeResponse
     */
    CompletableFuture describeNetworkInterfaceAttribute(DescribeNetworkInterfaceAttributeRequest request);

    /**
     * @param request the request parameters of DescribeNetworkInterfacePermissions  DescribeNetworkInterfacePermissionsRequest
     * @return DescribeNetworkInterfacePermissionsResponse
     */
    CompletableFuture describeNetworkInterfacePermissions(DescribeNetworkInterfacePermissionsRequest request);

    /**
     * description :
     * 
Usage notes
     * 
You can call the DescribeNetworkInterfaces operation for paged query by specifying the MaxResults or NextToken parameter. Take note of the following items:
     * 

     * 
During a paged query, when you call the DescribeNetworkInterfaces operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token that can be used in the next call to retrieve a new page of results.
     * 
When you call the DescribeNetworkInterfaces operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
     * 
     * @param request the request parameters of DescribeNetworkInterfaces  DescribeNetworkInterfacesRequest
     * @return DescribeNetworkInterfacesResponse
     */
    CompletableFuture describeNetworkInterfaces(DescribeNetworkInterfacesRequest request);

    /**
     * @deprecated OpenAPI DescribeNewProjectEipMonitorData is deprecated  * @param request  the request parameters of DescribeNewProjectEipMonitorData  DescribeNewProjectEipMonitorDataRequest
     * @return DescribeNewProjectEipMonitorDataResponse
     */
    @Deprecated
    CompletableFuture describeNewProjectEipMonitorData(DescribeNewProjectEipMonitorDataRequest request);

    /**
     * @deprecated OpenAPI DescribePhysicalConnections is deprecated  * @param request  the request parameters of DescribePhysicalConnections  DescribePhysicalConnectionsRequest
     * @return DescribePhysicalConnectionsResponse
     */
    @Deprecated
    CompletableFuture describePhysicalConnections(DescribePhysicalConnectionsRequest request);

    /**
     * @param request the request parameters of DescribePrefixListAssociations  DescribePrefixListAssociationsRequest
     * @return DescribePrefixListAssociationsResponse
     */
    CompletableFuture describePrefixListAssociations(DescribePrefixListAssociationsRequest request);

    /**
     * @param request the request parameters of DescribePrefixListAttributes  DescribePrefixListAttributesRequest
     * @return DescribePrefixListAttributesResponse
     */
    CompletableFuture describePrefixListAttributes(DescribePrefixListAttributesRequest request);

    /**
     * description :
     * 
Description
     * 
You can specify the AddressFamily, PrefixListId.N, and PrefixListName request parameters to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
     * 
     * @param request the request parameters of DescribePrefixLists  DescribePrefixListsRequest
     * @return DescribePrefixListsResponse
     */
    CompletableFuture describePrefixLists(DescribePrefixListsRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The required parameters vary based on the types of resources whose prices you want to query.

     * 
When ResourceType is set to instance, you must specify InstanceType.
     * 
When ResourceType is set to disk, you must specify both DataDisk.1.Category and DataDisk.1.Size. When ResourceType is set to disk, only pay-as-you-go prices of cloud disks are returned. In this scenario, PriceUnit can be set only to Hour.
     * 
When ResourceType is set to ddh, you must specify DedicatedHostType.
     * 
When ResourceType is set to ElasticityAssurance, you must specify InstanceType.
     * 
When ResourceType is set to CapacityReservation, you must specify InstanceType.
     * 
     * 
     * 
When ResourceType is set to bandwidth, only the pay-by-traffic (PayByTraffic) price for network usage is returned.
     * 
When ResourceType is set to instance, the prices of up to four data disks can be queried.
     * 
By default, ChargeType is set to PostPaid. You can specify PriceUnit to query prices of ECS resources that have different billing cycles.
     * 
     * 
     * @param request the request parameters of DescribePrice  DescribePriceRequest
     * @return DescribePriceResponse
     */
    CompletableFuture describePrice(DescribePriceRequest request);

    /**
     * @param request the request parameters of DescribeRecommendInstanceType  DescribeRecommendInstanceTypeRequest
     * @return DescribeRecommendInstanceTypeResponse
     */
    CompletableFuture describeRecommendInstanceType(DescribeRecommendInstanceTypeRequest request);

    /**
     * description :
     * 

     * 
     * @param request the request parameters of DescribeRegions  DescribeRegionsRequest
     * @return DescribeRegionsResponse
     */
    CompletableFuture describeRegions(DescribeRegionsRequest request);

    /**
     * description :
     * 
  You can call this operation to query the price for renewing a subscription instance for a specific period of time or to a synchronized expiration date.
     * 

     * 
Take note of the following items:

     * 
If you specify only the required parameters, the price for renewing an instance for one month is queried by default.
     * 
The renewal period-related parameter pair (Period and PeriodUnit) and the synchronized expiration date-related parameter (ExpectedRenewDay) are mutually exclusive. You cannot set these parameters together to query the prices for renewing a specified instance for a period of time and to a synchronized expiration date at the same time.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeRenewalPrice  DescribeRenewalPriceRequest
     * @return DescribeRenewalPriceResponse
     */
    CompletableFuture describeRenewalPrice(DescribeRenewalPriceRequest request);

    /**
     * @param request the request parameters of DescribeReservedInstanceAutoRenewAttribute  DescribeReservedInstanceAutoRenewAttributeRequest
     * @return DescribeReservedInstanceAutoRenewAttributeResponse
     */
    CompletableFuture describeReservedInstanceAutoRenewAttribute(DescribeReservedInstanceAutoRenewAttributeRequest request);

    /**
     * @param request the request parameters of DescribeReservedInstances  DescribeReservedInstancesRequest
     * @return DescribeReservedInstancesResponse
     */
    CompletableFuture describeReservedInstances(DescribeReservedInstancesRequest request);

    /**
     * @param request the request parameters of DescribeResourceByTags  DescribeResourceByTagsRequest
     * @return DescribeResourceByTagsResponse
     */
    CompletableFuture describeResourceByTags(DescribeResourceByTagsRequest request);

    /**
     * description :
     * 
Examples of common scenarios in which this operation is used:
     * 
Example 1: Query the instance types to which you can change the instance type of an instance.
     * 
Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\\\ instance and the inventory of the queried instance types in the zone in which the instance resides.
     *     http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
     *     &RegionId=cn-hangzhou
     *     &ResourceId=i-bp67acfmxazb4p****
     *     &DestinationResource=InstanceType
     *     &OperationType=Upgrade
     *     &
     * 
Example 2: Query the instance types to which you can change the instance type of an instance after a system disk category change.
     * 
Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\\\ instance after a system disk category change and the inventory of the queried instance types in the zone in which the instance resides.
     *     http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
     *     &RegionId=cn-hangzhou
     *     &ResourceId=i-bp67acfmxazb4p****
     *     &DestinationResource=InstanceType
     *     &OperationType=Upgrade
     *     &Conditions.0=DiskCategory
     *     &
     * 
Example 3: Query the system disk categories supported by the instance type to which you want to change the instance type of an instance.
     * 
Query the system disk categories supported by the instance type to which you want to change the instance type of the i-bp67acfmxazb4p\\\\ instance and the inventory of the disk categories in the zone in which the instance resides. In this example, the ecs.g7.large instance type is used. To change to the instance type, you must change the system disk category of the instance to a category supported by the instance type.
     * 

     * 
 You can call this operation as described in Example 2 to query the instance types to which you can change the instance type of an instance.
     *     http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
     *     &RegionId=cn-hangzhou
     *     &ResourceId=i-bp67acfmxazb4p****
     *     &DestinationResource=SystemDisk
     *     &OperationType=Upgrade
     *     &InstanceType=ecs.g7.large
     *     &
     * 
     * 
     * @param request the request parameters of DescribeResourcesModification  DescribeResourcesModificationRequest
     * @return DescribeResourcesModificationResponse
     */
    CompletableFuture describeResourcesModification(DescribeResourcesModificationRequest request);

    /**
     * @deprecated OpenAPI DescribeRouteTables is deprecated  * @param request  the request parameters of DescribeRouteTables  DescribeRouteTablesRequest
     * @return DescribeRouteTablesResponse
     */
    @Deprecated
    CompletableFuture describeRouteTables(DescribeRouteTablesRequest request);

    /**
     * @deprecated OpenAPI DescribeRouterInterfaces is deprecated  * @param request  the request parameters of DescribeRouterInterfaces  DescribeRouterInterfacesRequest
     * @return DescribeRouterInterfacesResponse
     */
    @Deprecated
    CompletableFuture describeRouterInterfaces(DescribeRouterInterfacesRequest request);

    /**
     * @param request the request parameters of DescribeSavingsPlanEstimation  DescribeSavingsPlanEstimationRequest
     * @return DescribeSavingsPlanEstimationResponse
     */
    CompletableFuture describeSavingsPlanEstimation(DescribeSavingsPlanEstimationRequest request);

    /**
     * @param request the request parameters of DescribeSavingsPlanPrice  DescribeSavingsPlanPriceRequest
     * @return DescribeSavingsPlanPriceResponse
     */
    CompletableFuture describeSavingsPlanPrice(DescribeSavingsPlanPriceRequest request);

    /**
     * @param request the request parameters of DescribeSecurityGroupAttribute  DescribeSecurityGroupAttributeRequest
     * @return DescribeSecurityGroupAttributeResponse
     */
    CompletableFuture describeSecurityGroupAttribute(DescribeSecurityGroupAttributeRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
A security group can be referenced by the inbound or outbound rules of other security groups.
     * 
Up to 100 entries can be returned each time.
     * 
If a security group cannot be deleted by calling the DeleteSecurityGroup operation, you can call the DescribeSecurityGroupReferences operation to check whether the security group is referenced by the rules of other security groups. If the security group is referenced by the rules of other security groups, you must remove the reference before you can delete the security group.
     * 
     * 
     * @param request the request parameters of DescribeSecurityGroupReferences  DescribeSecurityGroupReferencesRequest
     * @return DescribeSecurityGroupReferencesResponse
     */
    CompletableFuture describeSecurityGroupReferences(DescribeSecurityGroupReferencesRequest request);

    /**
     * description :
     * 
  Paged query: We recommend that you specify MaxResults and NextToken.
     *     *   If the response does not include NextToken, the current page of results is the last page and no more results are to be returned.
     *     *   During a paged query, when you call the DescribeSecurityGroups operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token that can be used in the next call to retrieve a new page of results.
     *     *   When you call the DescribeSecurityGroups operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 

     * 
When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see Parameter formats.
     * 
     * 
     * @param request the request parameters of DescribeSecurityGroups  DescribeSecurityGroupsRequest
     * @return DescribeSecurityGroupsResponse
     */
    CompletableFuture describeSecurityGroups(DescribeSecurityGroupsRequest request);

    /**
     * description :
     * 
Usage notes:
     * 

     * 
When you send a file, the file may fail to be sent to specific Elastic Compute Service (ECS) instances. You can call this operation to check the file sending results.
     * 
You can call this operation to query the file sending records within the last six weeks.
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: During a paged query, when you call the DescribeSendFileResults operation to retrieve the first page of results, set MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you call the DescribeSendFileResults operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and set MaxResults to specify the maximum number of entries to return in this call.
     * 
Method 2: Use PageSize to specify the number of entries to return on each page and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DescribeSendFileResults  DescribeSendFileResultsRequest
     * @return DescribeSendFileResultsResponse
     */
    CompletableFuture describeSendFileResults(DescribeSendFileResultsRequest request);

    /**
     * description :
     * 
You can specify multiple request parameters to be queried, such as InstanceId, SnapshotGroupId.N, and Status.N. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
     * 
     * @param request the request parameters of DescribeSnapshotGroups  DescribeSnapshotGroupsRequest
     * @return DescribeSnapshotGroupsResponse
     */
    CompletableFuture describeSnapshotGroups(DescribeSnapshotGroupsRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
You can specify multiple request parameters, such as RegionId, DiskIds, and InstanceId, to query snapshot chains. Specified parameters have logical AND relations.
     * 
Only the specified parameters are used as filter conditions. If the DiskIds and SnapshotLinkIds parameters are set to empty JSON arrays, the values are considered as valid filter conditions. In this case, an empty result is returned.
     * 
     * 
     * @param request the request parameters of DescribeSnapshotLinks  DescribeSnapshotLinksRequest
     * @return DescribeSnapshotLinksResponse
     */
    CompletableFuture describeSnapshotLinks(DescribeSnapshotLinksRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
Up to 400 monitoring data entries can be returned at a time. Make sure that the TotalCount value does not exceed 400. The value is calculated by using the following formula: TotalCount = (EndTime - StartTime)/Period. If the TotalCount value is greater than 400, the InvalidParameter.TooManyDataQueried error is returned.
     * 
You can query the monitoring data of snapshot sizes in the last 30 days. If the value of StartTime is more than 30 days earlier than the current time, an error is returned.
     * 
     * 
     * @param request the request parameters of DescribeSnapshotMonitorData  DescribeSnapshotMonitorDataRequest
     * @return DescribeSnapshotMonitorDataResponse
     */
    CompletableFuture describeSnapshotMonitorData(DescribeSnapshotMonitorDataRequest request);

    /**
     * @param request the request parameters of DescribeSnapshotPackage  DescribeSnapshotPackageRequest
     * @return DescribeSnapshotPackageResponse
     */
    CompletableFuture describeSnapshotPackage(DescribeSnapshotPackageRequest request);

    /**
     * description :
     * 
You can configure multiple request parameters such as InstanceId, DiskId, and SnapshotIds to query snapshots. Configured parameters have logical AND relations. Only the configured parameters are included in the filter conditions.
     * When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see Parameter format overview.
     * 
     * @param request the request parameters of DescribeSnapshots  DescribeSnapshotsRequest
     * @return DescribeSnapshotsResponse
     */
    CompletableFuture describeSnapshots(DescribeSnapshotsRequest request);

    /**
     * description :
     * 
Usage notes
     * 
If you want to view the snapshot usage of each disk in the current region, we recommend that you call the DescribeSnapshotLinks operation to query snapshot chain information.
     * 
     * @param request the request parameters of DescribeSnapshotsUsage  DescribeSnapshotsUsageRequest
     * @return DescribeSnapshotsUsageResponse
     */
    CompletableFuture describeSnapshotsUsage(DescribeSnapshotsUsageRequest request);

    /**
     * description :
     * 
  This operation is applicable only to I/O optimized preemptible instances that reside in virtual private clouds (VPCs).
     * 

     * 
You can use one of the following methods to call this operation:

     * 
Specify Cores and Memory or MinCores and MinMemory to query information about the instance types that meet the specified vCPU and memory requirements.
     * 
Specify InstanceTypes.N to query information about the specified instance types.
     * 
Specify Cores and Memory or MinCores and MinMemory, and then specify InstanceTypeFamily or InstanceFamilyLevel to query information about the instance types that meet the specified vCPU and memory requirements within the specified instance family or at a specified instance family level.
     * 
     * 
     * 
You can calculate the average price of preemptible instances based on the percentage of the average preemptible instance price relative to the pay-as-you-go instance price and the pay-as-you-go instance price.
     * 
     * 
     * @param request the request parameters of DescribeSpotAdvice  DescribeSpotAdviceRequest
     * @return DescribeSpotAdviceResponse
     */
    CompletableFuture describeSpotAdvice(DescribeSpotAdviceRequest request);

    /**
     * @param request the request parameters of DescribeSpotPriceHistory  DescribeSpotPriceHistoryRequest
     * @return DescribeSpotPriceHistoryResponse
     */
    CompletableFuture describeSpotPriceHistory(DescribeSpotPriceHistoryRequest request);

    /**
     * @param request the request parameters of DescribeStorageCapacityUnits  DescribeStorageCapacityUnitsRequest
     * @return DescribeStorageCapacityUnitsResponse
     */
    CompletableFuture describeStorageCapacityUnits(DescribeStorageCapacityUnitsRequest request);

    /**
     * @param request the request parameters of DescribeStorageSetDetails  DescribeStorageSetDetailsRequest
     * @return DescribeStorageSetDetailsResponse
     */
    CompletableFuture describeStorageSetDetails(DescribeStorageSetDetailsRequest request);

    /**
     * @param request the request parameters of DescribeStorageSets  DescribeStorageSetsRequest
     * @return DescribeStorageSetsResponse
     */
    CompletableFuture describeStorageSets(DescribeStorageSetsRequest request);

    /**
     * description :
     * 
If a tag key that has no tag value is specified, all tags that contain the tag key are returned. If a tag key-value pair is specified, only tags that exactly match the key-value pair are returned.
     * 
     * @param request the request parameters of DescribeTags  DescribeTagsRequest
     * @return DescribeTagsResponse
     */
    CompletableFuture describeTags(DescribeTagsRequest request);

    /**
     * @param request the request parameters of DescribeTaskAttribute  DescribeTaskAttributeRequest
     * @return DescribeTaskAttributeResponse
     */
    CompletableFuture describeTaskAttribute(DescribeTaskAttributeRequest request);

    /**
     * description :
     * 
Debugging
     * 
OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.
     * 
     * @param request the request parameters of DescribeTasks  DescribeTasksRequest
     * @return DescribeTasksResponse
     */
    CompletableFuture describeTasks(DescribeTasksRequest request);

    /**
     * description :
     * 
You can query the session records of Session Manager that were generated in the last four weeks.
     * 
     * @param request the request parameters of DescribeTerminalSessions  DescribeTerminalSessionsRequest
     * @return DescribeTerminalSessionsResponse
     */
    CompletableFuture describeTerminalSessions(DescribeTerminalSessionsRequest request);

    /**
     * @deprecated OpenAPI DescribeUserBusinessBehavior is deprecated  * @param request  the request parameters of DescribeUserBusinessBehavior  DescribeUserBusinessBehaviorRequest
     * @return DescribeUserBusinessBehaviorResponse
     */
    @Deprecated
    CompletableFuture describeUserBusinessBehavior(DescribeUserBusinessBehaviorRequest request);

    /**
     * description :
     * 
  If no user data is configured for the ECS instance, an empty string is returned.
     * 
     * @param request the request parameters of DescribeUserData  DescribeUserDataRequest
     * @return DescribeUserDataResponse
     */
    CompletableFuture describeUserData(DescribeUserDataRequest request);

    /**
     * @deprecated OpenAPI DescribeVRouters is deprecated  * @param request  the request parameters of DescribeVRouters  DescribeVRoutersRequest
     * @return DescribeVRoutersResponse
     */
    @Deprecated
    CompletableFuture describeVRouters(DescribeVRoutersRequest request);

    /**
     * @deprecated OpenAPI DescribeVSwitches is deprecated  * @param request  the request parameters of DescribeVSwitches  DescribeVSwitchesRequest
     * @return DescribeVSwitchesResponse
     */
    @Deprecated
    CompletableFuture describeVSwitches(DescribeVSwitchesRequest request);

    /**
     * @deprecated OpenAPI DescribeVirtualBorderRouters is deprecated  * @param request  the request parameters of DescribeVirtualBorderRouters  DescribeVirtualBorderRoutersRequest
     * @return DescribeVirtualBorderRoutersResponse
     */
    @Deprecated
    CompletableFuture describeVirtualBorderRouters(DescribeVirtualBorderRoutersRequest request);

    /**
     * @deprecated OpenAPI DescribeVirtualBorderRoutersForPhysicalConnection is deprecated  * @param request  the request parameters of DescribeVirtualBorderRoutersForPhysicalConnection  DescribeVirtualBorderRoutersForPhysicalConnectionRequest
     * @return DescribeVirtualBorderRoutersForPhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture describeVirtualBorderRoutersForPhysicalConnection(DescribeVirtualBorderRoutersForPhysicalConnectionRequest request);

    /**
     * @deprecated OpenAPI DescribeVpcs is deprecated, please use Vpc::2016-04-28::DescribeVpcs instead.  * @param request  the request parameters of DescribeVpcs  DescribeVpcsRequest
     * @return DescribeVpcsResponse
     */
    @Deprecated
    CompletableFuture describeVpcs(DescribeVpcsRequest request);

    /**
     * description :
     * 
When you call this operation, only a list of zones and some resource information of each zone are returned. If you want to query instance types and disk categories that are available for purchase in a specific zone, we recommend that you call the DescribeAvailableResource operation.
     * 
     * @param request the request parameters of DescribeZones  DescribeZonesRequest
     * @return DescribeZonesResponse
     */
    CompletableFuture describeZones(DescribeZonesRequest request);

    /**
     * @param request the request parameters of DetachClassicLinkVpc  DetachClassicLinkVpcRequest
     * @return DetachClassicLinkVpcResponse
     */
    CompletableFuture detachClassicLinkVpc(DetachClassicLinkVpcRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The disk that you want to detach must be attached to an ECS instance and in the In Use (In_use) state.
     * 
The instance from which you want to detach a data disk must be in the Running (Running) or Stopped (Stopped) state.
     * 
The instance from which you want to detach a system disk must be in the Stopped state.``
     * 
If the OperationLocks parameter in the response contains "LockReason" : "security" when you query the instance information, the instance is locked for security reasons and all operations are prohibited on the instance.
     * 
DetachDisk is an asynchronous operation. After you call the operation to detach a disk from an ECS instance, the disk is detached in approximately 1 minute.
     * 
If you want to attach an elastic ephemeral disk that you detached from an instance, you can attach the disk only to the instance.
     * 
     * 
     * @param request the request parameters of DetachDisk  DetachDiskRequest
     * @return DetachDiskResponse
     */
    CompletableFuture detachDisk(DetachDiskRequest request);

    /**
     * @param request the request parameters of DetachInstanceRamRole  DetachInstanceRamRoleRequest
     * @return DetachInstanceRamRoleResponse
     */
    CompletableFuture detachInstanceRamRole(DetachInstanceRamRoleRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
After you unbind an SSH key pair from an instance, you must call the RebootInstance operation to restart the instance to allow the unbind operation to take effect.
     * 
After you unbind an SSH key pair from an instance, the username and password authentication method is selected for the instance.
     * 
     * 
     * @param request the request parameters of DetachKeyPair  DetachKeyPairRequest
     * @return DetachKeyPairResponse
     */
    CompletableFuture detachKeyPair(DetachKeyPairRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
You cannot detach the primary ENI of an instance.
     * 
Make sure that the ENI to be detached is in the Detaching (Unbinding) or InUse (Bound) state.
     * 
Make sure that the instance from which you want to detach an ENI is in the Running (Running) or Stopped (Stopped) state.
     * 
The DetachNetworkInterface operation is an asynchronous operation. After this operation is called to detach an ENI, you can check the status or events of the ENI to determine whether the ENI is detached. The following figure shows the transitions between the states of the ENI.

     * 
If the ENI is in the Detaching state, the ENI detachment request is sent and the ENI is being detached from the associated instance.
     * 
If the ENI is in the Available state, the ENI is detached from the associated instance.
     * 
If the ENI is stuck in the Detaching state, the ENI may fail to be detached from the associated instance due to specific reasons. For example, the ENI may fail to be detached because the operating system of the instance did not respond to the ENI detachment request. If this issue occurs, you can re-initiate the request to detach the ENI. If the issue persists, restart the instance.
     * For information about examples on how to call the DetachNetworkInterface operation, see Detach an ENI from an ECS instance.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DetachNetworkInterface  DetachNetworkInterfaceRequest
     * @return DetachNetworkInterfaceResponse
     */
    CompletableFuture detachNetworkInterface(DetachNetworkInterfaceRequest request);

    /**
     * description :
     * 
The region ID. The following regions are supported: China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), and China (Hong Kong).
     * You can call the DescribeRegions operation to query the most recent region list.
     * 
     * @param request the request parameters of DisableActivation  DisableActivationRequest
     * @return DisableActivationResponse
     */
    CompletableFuture disableActivation(DisableActivationRequest request);

    /**
     * description :
     * 
  Instructions
     *     *   Only Alibaba Cloud accounts can call this operation.
     * 

     * 
Considerations

     * 
After Account-level EBS Default Encryption is disabled, the encryption status of existing cloud disks is not affected.
     * 
After Account-level EBS Default Encryption is disabled, you can still choose to encrypt new cloud disks when you purchase the disks.
     * 
     * 
     * 
     * 
     * @param request the request parameters of DisableDiskEncryptionByDefault  DisableDiskEncryptionByDefaultRequest
     * @return DisableDiskEncryptionByDefaultResponse
     */
    CompletableFuture disableDiskEncryptionByDefault(DisableDiskEncryptionByDefaultRequest request);

    /**
     * description :
     * 

     * 
 The Account-level EBS Default Encryption feature is available only in specific regions and to specific users. To use Account-level EBS Default Encryption, submit a ticket.
     * 
     * 

     * 
Precautions

     * 
Only Alibaba Cloud accounts can call this operation.
     * 
Before you can enable the Account-level EBS Default Encryption feature in a region, you must activate Key Management Service (KMS) in the region.
     * 
After you enable the Account-level EBS Default Encryption feature in a region, you can purchase only encrypted cloud disks in the region. For more information, see the Limits section of the "Encrypt cloud disks" topic.
     * 
     * 
     * 
Considerations

     * 
After you enable the Account-level EBS Default Encryption feature in a region, new pay-as-you-go and subscription cloud disks in the region must be encrypted. You can use the KMS key configured for the Account-level EBS Default Encryption feature or specify other KMS keys to encrypt the cloud disks.
     * 
The first time you enable the Account-level EBS Default Encryption feature in a region, the service key in the region is automatically used to encrypt EBS resources.
     * 
     * 
     * 
Suggestions

     * 
You can call the DescribeDiskEncryptionByDefaultStatus operation to query whether the Account-level EBS Default Encryption feature is enabled in a region and the DescribeDiskDefaultKMSKeyId operation to query the ID of the KMS key used by the Account-level EBS Default Encryption feature in a region.
     * 
You can call the ModifyDiskDefaultKMSKeyId or ResetDiskDefaultKMSKeyId operation to change or reset the KMS key used by the Account-level EBS Default Encryption feature in a region.
     * 
You can call the DisableDiskEncryptionByDefault operation to disable the Account-level EBS Default Encryption feature in a region.
     * 
     * 
     * 
     * 
     * @param request the request parameters of EnableDiskEncryptionByDefault  EnableDiskEncryptionByDefaultRequest
     * @return EnableDiskEncryptionByDefaultResponse
     */
    CompletableFuture enableDiskEncryptionByDefault(EnableDiskEncryptionByDefaultRequest request);

    /**
     * @deprecated OpenAPI EnablePhysicalConnection is deprecated  * @param request  the request parameters of EnablePhysicalConnection  EnablePhysicalConnectionRequest
     * @return EnablePhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture enablePhysicalConnection(EnablePhysicalConnectionRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
Make sure that you are familiar with the prerequisites and considerations. For more information, see Export a custom image.
     * 
The ImageFormat parameter is available only for the following regions: Japan (Tokyo), Indonesia (Jakarta), Germany (Frankfurt), UAE (Dubai), US (Virginia), UK (London), Singapore, Malaysia (Kuala Lumpur), and US (Silicon Valley). By default, custom images are exported in the RAW format in regions where the ImageFormat parameter is unsupported.
     * 
Use Resource Access Management (RAM) to authorize Elastic Compute Service (ECS) to write data to OSS. To complete the authorization, perform the following operations:

     * 
Create a role named AliyunECSImageExportDefaultRole and attach the following policy to the role:
     *    {
     *      "Statement": [
     *        {
     *          "Action": "sts:AssumeRole",
     *          "Effect": "Allow",
     *          "Principal": {
     *            "Service": [
     *              "ecs.aliyuncs.com"
     *            ]
     *          }
     *        }
     *      ],
     *      "Version": "1"
     *    }
     * 
Attach the AliyunECSImageExportRolePolicy system policy, which is the default policy that grants ECS the permissions to export images, to the AliyunECSImageExportDefaultRole role. For more information, go to the Cloud Resource Access Authorization page. You can also create a custom policy that contains the following content and attach the policy to the role:
     *      {
     *        "Version": "1",
     *        "Statement": [
     *          {
     *            "Action": [
     *              "oss:GetObject",
     *              "oss:PutObject",
     *              "oss:DeleteObject",
     *              "oss:GetBucketLocation",
     *              "oss:GetBucketInfo",
     *              "oss:AbortMultipartUpload",
     *              "oss:ListMultipartUploads",
     *              "oss:ListParts"
     *            ],
     *            "Resource": "*",
     *            "Effect": "Allow"
     *          }
     *        ]
     *      }
     * 
     * 
     * 
     * 
After you export the images, take note of the following items:
     * Each exported custom image is stored in the specified OSS bucket. You can download the custom image. For more information, see Download OSS objects by using simple download.
     * 
     * @param request the request parameters of ExportImage  ExportImageRequest
     * @return ExportImageResponse
     */
    CompletableFuture exportImage(ExportImageRequest request);

    /**
     * @deprecated OpenAPI ExportSnapshot is deprecated  * @param request  the request parameters of ExportSnapshot  ExportSnapshotRequest
     * @return ExportSnapshotResponse
     */
    @Deprecated
    CompletableFuture exportSnapshot(ExportSnapshotRequest request);

    /**
     * description :
     * 
  ECS is a virtualized cloud-based service and cannot be connected to display devices. Alibaba Cloud caches system command outputs for the last start, restart, or shutdown of ECS instances. You can call the GetInstanceConsoleOutput operation to query the command outputs.
     * 

     * 
For instances of the retired instance types, you cannot obtain command outputs. For more information, see Retired instance types.
     * 
You cannot obtain the command outputs of Windows instances.
     * 
     * 
     * @param request the request parameters of GetInstanceConsoleOutput  GetInstanceConsoleOutputRequest
     * @return GetInstanceConsoleOutputResponse
     */
    CompletableFuture getInstanceConsoleOutput(GetInstanceConsoleOutputRequest request);

    /**
     * description :
     * 
After ECS returns a Base64-encoded instance screenshot in the JPG format, you must decode the screenshot. We recommend that you call this operation for troubleshooting and diagnosis. When you call this operation, take note of the following items:
     * 

     * 
The instance must be in the Running state.
     * 
For instances of the retired instance types, you cannot obtain screenshots. For more information, see Retired instance types.
     * 
If you call this operation on an instance for multiple times, the call interval must be at least 10 seconds. Otherwise, the Throttling error is returned.
     * 
     * 
     * @param request the request parameters of GetInstanceScreenshot  GetInstanceScreenshotRequest
     * @return GetInstanceScreenshotResponse
     */
    CompletableFuture getInstanceScreenshot(GetInstanceScreenshotRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
Before you import an image, you must upload the image to an Object Storage Service (OSS) bucket. For more information, see Upload objects.
     * 
In specific scenarios, you may want to create a custom image based on the operating system data of a source server, import the image to Alibaba Cloud, and then create an ECS instance from the image. The source server can be a physical server, a virtual machine, or a cloud host. If the virtio driver is not installed on the source server, the created ECS instance may be unable to start. To prevent this issue, verify that the virtio driver is installed on the source server before you import the image to Alibaba Cloud. For more information, see Install the virtio driver.
     * 
Before you import images for the first time, you must use Resource Access Management (RAM) to authorize ECS to access your OSS buckets. If ECS is not authorized to access your OSS buckets, the NoSetRoletoECSServiceAccount or InvalidOperation.CloudBoxImageImportRoleRequired error code is returned when you call the ImportImage operation. The authorization configuration varies based on whether the image files are imported from a cloud box.

     * 
If the image files are not imported from a cloud box, you can complete the authorization on the Cloud Resource Access Authorization page of the RAM console. You can also complete the authorization by using a RAM role and RAM policies. The following example shows the policies and permissions required for specific steps in the authorization procedure. For more information, see Control access to ECS resources by using RAM users.

     * 
Create a RAM role named AliyunECSImageImportDefaultRole. You must use this exact role name. Otherwise, the image cannot be imported. Configure the following trust policy for the role:
     * {
     *     "Statement": [
     *     {
     *         "Action": "sts:AssumeRole",
     *         "Effect": "Allow",
     *         "Principal": {
     *         "Service": [
     *             "ecs.aliyuncs.com"
     *         ]
     *         }
     *     }
     * ],
     *     "Version": "1"
     * }
     * 
Attach the AliyunECSImageImportRolePolicy system policy to the RAM role. You can also create a custom policy that contains the following content and attach the policy to the role:
{
     *     "Version": "1",
     *     "Statement": [
     *     {
     *         "Action": [
     *                 "oss:GetObject",
     *                 "oss:GetBucketLocation",
     *                 "oss:GetBucketInfo"
     *     ],
     *             "Resource": "*",
     *             "Effect": "Allow"
     *             }
     *     ]
     * }
     * 
     * 
     * 
     * 
     * 
If the image files are imported from a cloud box, you can complete the authorization on the Cloud Resource Access Authorization page of the RAM console. You can also complete the authorization by using a RAM role and RAM policies. The following example shows the policies and permissions required for specific steps in the authorization procedure. For more information, see Control access to ECS resources by using RAM users.

     * 
Create a RAM role named AliyunECSCloudBoxImageImportDefaultRole. You must use this exact role name. Otherwise, the image cannot be imported. Configure the following trust policy for the role:
     * {
     *     "Statement": [
     *     {
     *         "Action": "sts:AssumeRole",
     *         "Effect": "Allow",
     *         "Principal": {
     *         "Service": [
     *             "ecs.aliyuncs.com"
     *         ]
     *         }
     *     }
     * ],
     *     "Version": "1"
     * }
     * 
Attach the AliyunECSCloudBoxImageImportRolePolicy system policy to the RAM role. You can also create a custom policy that contains the following content and attach the policy to the role:
{
     *     "Version": "1",
     *     "Statement": [
     *     {
     *         "Action": [
     *                 "oss-cloudbox:GetObject",
     *                 "oss-cloudbox:GetBucketLocation",
     *                 "oss-cloudbox:GetBucketInfo"
     *     ],
     *             "Resource": "*",
     *             "Effect": "Allow"
     *             }
     *     ]
     * }
     * 
     * 
     * 
     * 
     * 
     * 
     * 
You cannot delete an image that is being imported. However, you can call the CancelTask operation to cancel the image import task.
     * 
You can import an image only to the same region as the OSS bucket to which the image file is uploaded.
     * 
The valid values of N in DiskDeviceMapping.N range from 1 to 17. When N is set to 1, the disk is a system disk. When N is set to a value from 2 to 17, the disk is a data disk. When N is set to a value greater than 17, parameters prefixed with DiskDeviceMapping.N are ignored.
     * 
When you set Architecture to arm64 or when you set Platform to CentOS Stream, Anolis, AlmaLinux, UOS, Kylin, or Rocky Linux, take note of the following items:

     * 
To ensure that the password can be set or the key pair can be modified for an imported image, make sure that the image meets the following requirements before you import it:

     * 
The kernel of the operating system supports the CONFIG_FW_CFG_SYSFS feature. By default, Linux community kernel 4.6 and later and CentOS kernel 3.10.0-826.el7 and later support the CONFIG_FW_CFG_SYSFS feature. You can run the grep -nr CONFIG_FW_CFG_SYSFS /boot/config-$(uname -r) command on the source server of the image. If the command output contains CONFIG_FW_CFG_SYSFS=y, the kernel of the image supports the CONFIG_FW_CFG_SYSFS feature.
     * 
Alibaba Cloud cloud-init of the latest version is installed on the operating system. If the version of cloud-init is 19.1, the minor version must be 19.1.3 or later. If the version of cloud-init is 0.7.6a in some early versions of operating systems, the minor version must be 0.7.6a15 or later. For more information, see Install cloud-init.
     * 
The operating system supports the SHA-512 encryption algorithm.
     * 
     * 
     * 
If you want an imported image to support the resizing of disks and file systems, make sure that the image meets the following requirements before you import it:

     * 
The kernel version of the operating system is later than 3.6.
     * 
The image supports the growpart command. To support this command, you must install the cloud-utils-growpart package. The methods of installing the package vary based on operating systems. For more information, see Extend the partitions and file systems of disks on a Linux instance.
     * 
The image supports the resize2fs command. To support this command, you must install the e2fsprogs package. By default, the package is installed on the operating system. If the package is not installed, install it.
     * 
Alibaba Cloud cloud-init of the latest version is installed on the operating system. If the version of cloud-init is 19.1, the minor version must be 19.1.3 or later. If the version of cloud-init is 0.7.6a in some early versions of operating systems, the minor version must be 0.7.6a15 or later. For more information, see Install cloud-init.
     * 
     * 
     * 
     * 
     * 
If the image that you want to import uses the Arm64 architecture, configure the real-time clock (RTC) to use the Coordinated Universal Time (UTC) time standard. For more information, see Linux time and time zones.
     * 
When you import images, we recommend that you specify DetectionStrategy. This way, you can optimize the images based on the image check results. For more information, see Overview of image check.
     * 
     * 
     * @param request the request parameters of ImportImage  ImportImageRequest
     * @return ImportImageResponse
     */
    CompletableFuture importImage(ImportImageRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
A maximum of 500 key pairs can be created in each region.
     * 
The key pair to be imported must support one of the following encryption methods:

     * 
rsa
     * 
dsa
     * 
ssh-rsa
     * 
ssh-dss
     * 
ecdsa
     * 
[email protected]
     * 
[email protected]
     * 
[email protected]
     * 
[email protected]
     * 
[email protected]
     * 
[email protected]
     * 
[email protected]
     * 
     * 
     * 
     * 
     * @param request the request parameters of ImportKeyPair  ImportKeyPairRequest
     * @return ImportKeyPairResponse
     */
    CompletableFuture importKeyPair(ImportKeyPairRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After you call the InstallCloudAssistant operation to install Cloud Assistant Agent on an ECS instance, call the RebootInstance operation to restart the instance to make the installation take effect.
     * 
     * @param request the request parameters of InstallCloudAssistant  InstallCloudAssistantRequest
     * @return InstallCloudAssistantResponse
     */
    CompletableFuture installCloudAssistant(InstallCloudAssistantRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The ECS instances on which you want to run the Cloud Assistant command must meet the following requirements. If multiple ECS instances are specified and one of the instances does not meet the requirements for running the command, the call fails. You must specify instances that meet the requirements and call the InvokeCommand operation again.

     * 
The instances are in the Running (Running) state. You can call the DescribeInstances operation to query the status of instances.
     * 
Cloud Assistant Agent is installed on the instances. For more information, see Install Cloud Assistant Agent.
     * 
If the command is a PowerShell command, make sure that the instances have the PowerShell module configured.
     * 
     * 
     * 
You can configure the command to run only once on the instances.
     * 
You can configure the command to run on the instances based on a schedule.

     * 
The schedule is specified by Frequency. The results of each execution of the command do not affect the next execution of the command.
     * 
When you use a cron expression to specify a schedule, you can specify a time zone based on your business requirements. If you do not specify a time zone, the schedule is determined by the system time of the instances. Make sure that the time or time zone of the instances meets your business requirements. For more information, see Manage the time synchronization service.
     * To ensure that scheduled tasks can run as expected, make sure that the version of Cloud Assistant Agent is not earlier than the following versions. A scheduled task can run a command at a fixed interval, only once at a specific time, or at specific times based on a cron expression in a specified year or time zone. If the ClientNeedUpgrade error code is returned, you must upgrade Cloud Assistant Agent to the latest version. For more information, see Upgrade or disable upgrades for Cloud Assistant Agent.
     * 
Linux: 2.2.3.282
     * 
Windows: 2.1.3.282
     * 
     * 
     * 
Command executions may fail due to instance status exceptions, network exceptions, or exceptions on Cloud Assistant Agent. If a command execution fails, no execution information is generated. For more information, see Check execution results and troubleshoot common issues.
     * 
If you enable the custom parameter feature when you create the command, you must specify custom parameters (Parameters) to run the command.
     * 
Before you run the command on instances, especially new instances, we recommend that you call the DescribeCloudAssistantStatus operation to query the status of Cloud Assistant Agent on the instances and run the command when the value of CloudAssistantStatus in the response is true for the instances.
     * 
     * 
     * @param request the request parameters of InvokeCommand  InvokeCommandRequest
     * @return InvokeCommandResponse
     */
    CompletableFuture invokeCommand(InvokeCommandRequest request);

    /**
     * description :
     * 
Usage notes
     * 
A resource is a cloud service entity that you create on Alibaba Cloud, such as an ECS instance, an elastic network interface (ENI), or an image. A resource group is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources and monitor and run tasks in a centralized manner without the need to switch between Alibaba Cloud services.
     * 
     * @param request the request parameters of JoinResourceGroup  JoinResourceGroupRequest
     * @return JoinResourceGroupResponse
     */
    CompletableFuture joinResourceGroup(JoinResourceGroupRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
 This operation is not recommended. We recommend that you call the ModifyInstanceAttribute operation to add an instance to or remove an instance from a security group, and call the ModifyNetworkInterfaceAttribute operation to add an ENI to or remove an ENI from a security group.
     * Take note of the following items:
     * 
     * 

     * 
Before you add an instance to a security group, the instance must be in the Stopped (Stopped) or Running (Running) state.
     * 
An instance can be added to up to five security groups by default.
     * 
You can submit a ticket to change the maximum number of security groups to which an instance can be added to 4 or 10.
     * 
A basic security group can contain up to 2,000 instances. An advanced security group can contain up to 65,536 instances.
     * 
The security group and the instance must reside in the same region.
     * 
The security group and the instance must be of the same network type. If the network type is Virtual Private Cloud (VPC), the security group and the instance must reside in the same VPC.
     * 
An instance and an ENI cannot be added to a security group at the same time. You cannot specify InstanceId and NetworkInterfaceId at the same time in a request.
     * For more information, see Limits.
     * 
     * 
     * @param request the request parameters of JoinSecurityGroup  JoinSecurityGroupRequest
     * @return JoinSecurityGroupResponse
     */
    CompletableFuture joinSecurityGroup(JoinSecurityGroupRequest request);

    /**
     * description :
     * 

     * 
 This operation is not recommended. We recommend that you call the ModifyInstanceAttribute operation to add an instance to or remove an instance from a security group, and call the ModifyNetworkInterfaceAttribute operation to add an ENI to or remove an ENI from a security group.
     *  Alibaba Cloud modified verification rules for the LeaveSecurityGroup operation on July 8, 2024. When you remove an ECS instance or ENI that does not belong to a security group from the security group, the "InvalidSecurityGroupAssociation.NotFound" error code is returned instead of a success response. Update the LeaveSecurityGroup operation to use the new verification rules with the new error code based on your business requirements.
     * 
     * 

     * 
You cannot remove an instance and an ENI from a security group at the same time. This indicates that you cannot specify InstanceId and NetworkInterfaceId in one request.
     * 
Before you remove an instance from a security group, the instance must be in the Stopped (Stopped) or Running (Running) state.
     * 
An instance or ENI must be added to at least one security group. If you remove an instance or ENI from the only security group, the removal request fails and an error is returned.
     * 
When you remove an instance or ENI that is not in a security group from the security group, the removal request fails and an error is returned.
     * 
     * 
     * @param request the request parameters of LeaveSecurityGroup  LeaveSecurityGroupRequest
     * @return LeaveSecurityGroupResponse
     */
    CompletableFuture leaveSecurityGroup(LeaveSecurityGroupRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
Before you call this operation to query the status of Cloud Assistant plug-ins on ECS instances, make sure that the versions of Cloud Assistant Agent on the instances are not earlier than the following ones:

     * 
2.2.3.344 for Linux instances
     * 
2.1.3.344 for Windows instances
     * 
     * 
     * 
You can use one of the following methods to check the responses:

     * 
Method 1: When you call the ListPluginStatus operation to retrieve the first page of results during a paged query, use MaxResults to specify the maximum number of entries to return in the call. The return value of NextToken is a pagination token, which you can use in the next request to retrieve a new page of results. When you call the ListPluginStatus operation to retrieve a new page of results, set NextToken to the NextToken value returned in the previous call and use MaxResults to specify the maximum number of entries to return in this call. 
     * 
Method 2: Use PageSize to specify the number of entries to return on each page, and then use PageNumber to specify the number of the page to return. You can use only one of the preceding methods. If you specify MaxResults or NextToken, the PageSize and PageNumber request parameters do not take effect and the TotalCount response parameter is invalid.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ListPluginStatus  ListPluginStatusRequest
     * @return ListPluginStatusResponse
     */
    CompletableFuture listPluginStatus(ListPluginStatusRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Specify at least one of the following parameters or parameter pairs in a request to determine a query object:
     * 

     * 
ResourceId.N
     * 
Tag.N parameter pair (Tag.N.Key and Tag.N.Value)
     * 
TagFilter.N
     * If one of the following sets of request parameters is specified as filter conditions, only ECS resources that meet all the specified filter conditions are returned:
     * 
Set 1: Tag.N.Key, Tag.N.Value and ResourceId.N
     * 
Set 2: TagFilter.N.TagKey, TagFilter.N.TagValues.N and ResourceId.N
     * 
     * 
     * @param request the request parameters of ListTagResources  ListTagResourcesRequest
     * @return ListTagResourcesResponse
     */
    CompletableFuture listTagResources(ListTagResourcesRequest request);

    /**
     * description :
     * 
Before you call this operation, take note of the following items:
     * 

     * 
If you modify the capacity or capacity-related settings of an auto-provisioning group, the group executes a scheduling task after the group is modified.
     * 
You cannot modify an auto-provisioning group when the group is being deleted.
     * 
     * 
     * @param request the request parameters of ModifyAutoProvisioningGroup  ModifyAutoProvisioningGroupRequest
     * @return ModifyAutoProvisioningGroupResponse
     */
    CompletableFuture modifyAutoProvisioningGroup(ModifyAutoProvisioningGroupRequest request);

    /**
     * @deprecated OpenAPI ModifyAutoSnapshotPolicy is deprecated, please use Ecs::2014-05-26::ModifyAutoSnapshotPolicyEx instead.  * @param request  the request parameters of ModifyAutoSnapshotPolicy  ModifyAutoSnapshotPolicyRequest
     * @return ModifyAutoSnapshotPolicyResponse
     */
    @Deprecated
    CompletableFuture modifyAutoSnapshotPolicy(ModifyAutoSnapshotPolicyRequest request);

    /**
     * @param request the request parameters of ModifyAutoSnapshotPolicyEx  ModifyAutoSnapshotPolicyExRequest
     * @return ModifyAutoSnapshotPolicyExResponse
     */
    CompletableFuture modifyAutoSnapshotPolicyEx(ModifyAutoSnapshotPolicyExRequest request);

    /**
     * @deprecated OpenAPI ModifyBandwidthPackageSpec is deprecated  * @param request  the request parameters of ModifyBandwidthPackageSpec  ModifyBandwidthPackageSpecRequest
     * @return ModifyBandwidthPackageSpecResponse
     */
    @Deprecated
    CompletableFuture modifyBandwidthPackageSpec(ModifyBandwidthPackageSpecRequest request);

    /**
     * @param request the request parameters of ModifyCapacityReservation  ModifyCapacityReservationRequest
     * @return ModifyCapacityReservationResponse
     */
    CompletableFuture modifyCapacityReservation(ModifyCapacityReservationRequest request);

    /**
     * @param request the request parameters of ModifyCloudAssistantSettings  ModifyCloudAssistantSettingsRequest
     * @return ModifyCloudAssistantSettingsResponse
     */
    CompletableFuture modifyCloudAssistantSettings(ModifyCloudAssistantSettingsRequest request);

    /**
     * description :
     * 
You can modify a command when it is run. After the command is modified, the new command content applies to subsequent executions.
     * You cannot modify the command type. For example, you cannot change a shell command (RunShellScript) to a batch command (RunBatScript).
     * 
     * @param request the request parameters of ModifyCommand  ModifyCommandRequest
     * @return ModifyCommandResponse
     */
    CompletableFuture modifyCommand(ModifyCommandRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
All Elastic Compute Service (ECS) instances that are hosted on a dedicated host must be in the Stopped (Stopped) state before you can modify the CPU overcommit ratio of the dedicated host.
     * 
Changes to the CPU overcommit ratio of a dedicated host do not affect the running status of the dedicated host. After the CPU overcommit ratio is changed, the number of allocated vCPUs on the dedicated host cannot exceed the new total number of vCPUs. Otherwise, ECS instances that use the excess vCPUs cannot start.
     * 
     * 
     * @param request the request parameters of ModifyDedicatedHostAttribute  ModifyDedicatedHostAttributeRequest
     * @return ModifyDedicatedHostAttributeResponse
     */
    CompletableFuture modifyDedicatedHostAttribute(ModifyDedicatedHostAttributeRequest request);

    /**
     * description :
     * 
Usage notes
     * 
A pay-as-you-go dedicated host can be automatically released at the specified time. Before you release a pay-as-you-go dedicated host, make sure that the host is no longer required and all necessary application data is backed up.
     * 
     * @param request the request parameters of ModifyDedicatedHostAutoReleaseTime  ModifyDedicatedHostAutoReleaseTimeRequest
     * @return ModifyDedicatedHostAutoReleaseTimeResponse
     */
    CompletableFuture modifyDedicatedHostAutoReleaseTime(ModifyDedicatedHostAutoReleaseTimeRequest request);

    /**
     * description :
     * 
  If you enable auto-renewal for your subscription dedicated host, the system attempts to deduct the renewal payment at 08:00:00 (UTC+8) nine days before the dedicated host expires to renew the dedicated host. If this deduction attempt fails, the system attempt to deduct the payment at the same point in time the next day. The system attempts to deduct the payment once every day until the dedicated host expires or until the payment is deducted. Make sure that your account balance is sufficient.
     * 

     * 
Subscription dedicated hosts can be automatically renewed along with the subscription Elastic Compute Service (ECS) instances hosted on the dedicated hosts. For more information, see the description of the AutoRenewWithEcs parameter.
     * 
     * 
     * @param request the request parameters of ModifyDedicatedHostAutoRenewAttribute  ModifyDedicatedHostAutoRenewAttributeRequest
     * @return ModifyDedicatedHostAutoRenewAttributeResponse
     */
    CompletableFuture modifyDedicatedHostAutoRenewAttribute(ModifyDedicatedHostAutoRenewAttributeRequest request);

    /**
     * @param request the request parameters of ModifyDedicatedHostClusterAttribute  ModifyDedicatedHostClusterAttributeRequest
     * @return ModifyDedicatedHostClusterAttributeResponse
     */
    CompletableFuture modifyDedicatedHostClusterAttribute(ModifyDedicatedHostClusterAttributeRequest request);

    /**
     * @param request the request parameters of ModifyDedicatedHostsChargeType  ModifyDedicatedHostsChargeTypeRequest
     * @return ModifyDedicatedHostsChargeTypeResponse
     */
    CompletableFuture modifyDedicatedHostsChargeType(ModifyDedicatedHostsChargeTypeRequest request);

    /**
     * @deprecated OpenAPI ModifyDemand is deprecated, please use Ecs::2014-05-26::ModifyCapacityReservation instead.  * @description You can call this operation to modify the demand information of instance types. Alibaba Cloud provides the requested resources based on your demand. You can file demands only for I/O optimized instance types and instances of the virtual private cloud (VPC) type. Parameters except `DemandName` and `DemandDescription` can be modified only for demands that are in the Rejected state.
     * > This operation is in invitational preview and is not publicly available.
     * 
     * @param request the request parameters of ModifyDemand  ModifyDemandRequest
     * @return ModifyDemandResponse
     */
    @Deprecated
    CompletableFuture modifyDemand(ModifyDemandRequest request);

    /**
     * @param request the request parameters of ModifyDeploymentSetAttribute  ModifyDeploymentSetAttributeRequest
     * @return ModifyDeploymentSetAttributeResponse
     */
    CompletableFuture modifyDeploymentSetAttribute(ModifyDeploymentSetAttributeRequest request);

    /**
     * @param request the request parameters of ModifyDiagnosticMetricSet  ModifyDiagnosticMetricSetRequest
     * @return ModifyDiagnosticMetricSetResponse
     */
    CompletableFuture modifyDiagnosticMetricSet(ModifyDiagnosticMetricSetRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
When you call this operation to modify the attributes of a disk, if you set DeleteWithInstance to false and the instance to which the disk is attached is locked for security reasons, the DeleteWithInstance settings of the disk are ignored and the disk is released together with the instance. If "LockReason" : "security" is displayed in the response when you query the information about an instance, the instance is locked for security reasons.
     * 
You can use DiskIds.N to specify multiple block storage devices and batch modify the attributes of the devices, including the names and descriptions of the devices and whether to release the devices together with the associated instances.
     * 
     * 
     * @param request the request parameters of ModifyDiskAttribute  ModifyDiskAttributeRequest
     * @return ModifyDiskAttributeResponse
     */
    CompletableFuture modifyDiskAttribute(ModifyDiskAttributeRequest request);

    /**
     * description :
     * 
Usage notes
     * 
After you change the billing method, the payment (if any) is automatically completed. Maintain sufficient balance in your account. Otherwise, your order becomes invalid and must be canceled. If your account balance is insufficient, you can set AutoPay to false to generate an unpaid order. Then, log on to the Expenses and Costs console, go to the Orders page, and pay for the order.
     * Take note of the following items:
     * 

     * 
Only pay-as-you-go disks can be attached to pay-as-you-go instances, and the billing methods of the disks cannot be changed.
     * 
The instance cannot be in the Stopped state due to expiration.
     * 
The price difference is refunded to the payment account that you used. Vouchers that have been redeemed are nonrefundable.
     * 
You cannot change the billing method again within 5 minutes of a successful change.
     * 
     * 
     * @param request the request parameters of ModifyDiskChargeType  ModifyDiskChargeTypeRequest
     * @return ModifyDiskChargeTypeResponse
     */
    CompletableFuture modifyDiskChargeType(ModifyDiskChargeTypeRequest request);

    /**
     * description :
     * 
  Only Alibaba Cloud accounts can call this operation.
     * 

     * 
Before you can call this operation in a region, make sure that the Account-level EBS Default Encryption feature is enabled in the region.
     * 
The first time you use a customer master key (CMK), you must use the AliyunECSDiskEncryptDefaultRole role to grant Elastic Compute Service (ECS) access to KMS resources. For more information, see Grant access to KMS keys through RAM roles.
     * 
     * 
     * @param request the request parameters of ModifyDiskDefaultKMSKeyId  ModifyDiskDefaultKMSKeyIdRequest
     * @return ModifyDiskDefaultKMSKeyIdResponse
     */
    CompletableFuture modifyDiskDefaultKMSKeyId(ModifyDiskDefaultKMSKeyIdRequest request);

    /**
     * description :
     * 

     * 
 The Dedicated Block Storage Cluster feature is available in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Heyuan), Indonesia (Jakarta), Germany (Frankfurt), and China South 1 Finance.
     * Before you call the ModifyDiskDeployment operation, make sure that you fully understand the billing methods and prices of disks and dedicated block storage clusters. In addition, make sure that the dedicated block storage clusters are unexpired and your account has no overdue payments. For more information, see Dedicated block storage cluster and Block storage devices.
     * Take note of the following items:
     * 
     * 

     * 
The disks and a dedicated block storage cluster to which you want to migrate the disk must be in the same zone.
     * 
You can migrate only pay-as-you-go disks. If you want to migrate subscription disks, change the disks to pay-as-you-go disks first. For more information, see Change the billing method of a disk.
     * 
The specifications of disks that you want to migrate to a destination block storage cluster must the same as the disk specifications that the destination dedicated block storage cluster supports. During migration, you can change the specifications of the disks to ensure specification consistency.
     * 
The disk must be in the In Use (In_Use) or Available (Available) state.
     * 
If the disk is attached to an Elastic Compute Service (ECS) instance, the instance must be in the Running (Running) or Stopped (Stopped) state. The ECS instance cannot be in the Expired state.
     * 
The performance level of an Enterprise SSD (ESSD) is limited by the ESSD disk size. If you cannot upgrade the performance level of an ESSD, extend the ESSD and try again. For more information, see ResizeDisk and ESSDs.
     * 
An account can perform up to five disk migration tasks in the same region at the same time.
     * 
When a disk is being migrated, you cannot cancel the migration task, create snapshots for the disk, change the disk configurations, resize the disk, mount the disk, unmount the disk, or re-initialize the disk.

     * 
 After you migrate a disk to a destination cluster by calling the ModifyDiskDeployment operation, the billing method, disk specifications, and capabilities of the destination cluster take effect immediately on the disk. Alibaba Cloud charges the disk based on the disk category and performance level. For more information, see Dedicated block storage cluster and Block storage devices.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyDiskDeployment  ModifyDiskDeploymentRequest
     * @return ModifyDiskDeploymentResponse
     */
    CompletableFuture modifyDiskDeployment(ModifyDiskDeploymentRequest request);

    /**
     * description :
     * 
To minimize impacts on your business, change the disk categories or performance levels of cloud disks during off-peak hours.
     * Take note of the following items:
     * 

     * 
To change the performance level of an ESSD, take note of the following items:

     * 
If the ESSD is a subscription ESSD, you can only upgrade its performance level.
     * 
If the ESSD is a pay-as-you-go ESSD, you can upgrade or downgrade its performance level. However, you cannot downgrade the performance level to PL0.
     * 
The ESSD must be in the In Use (In_Use) or Unattached (Available) state.
     * 
If the ESSD is attached to an Elastic Compute Service (ECS) instance, the instance must be in the Running (Running) or Stopped (Stopped) state. The instance cannot be in the Expired state or stopped due to an overdue payment.
     * 
If you cannot upgrade the performance level of an ESSD due to the capacity limit, extend the ESSD by calling the ResizeDisk operation and then try again. For more information, see ESSDs.
     * 
     * 
     * 
For information about the limits on changing the disk category of a cloud disk, see Change the category of a disk.
     * 
For the disk categories to which cloud disks of each disk category can be changed, see Change the category of a disk.
     * After the disk category of a cloud disk is changed, the billing of the cloud disk has the following changes:
     * 
If the cloud disk is a pay-as-you-go disk, you are charged for the disk based on the new disk category.
     * 
If the cloud disk is a subscription disk, you may be charged additionally based on the price difference between the old and new disk categories and the remaining days of the billing cycle, starting from 00:00 the next day until the end of the subscription period.
     * For information about the billing of cloud disks, see Block storage devices.
     * 
     * 
     * @param request the request parameters of ModifyDiskSpec  ModifyDiskSpecRequest
     * @return ModifyDiskSpecResponse
     */
    CompletableFuture modifyDiskSpec(ModifyDiskSpecRequest request);

    /**
     * @deprecated OpenAPI ModifyEipAddressAttribute is deprecated  * @param request  the request parameters of ModifyEipAddressAttribute  ModifyEipAddressAttributeRequest
     * @return ModifyEipAddressAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyEipAddressAttribute(ModifyEipAddressAttributeRequest request);

    /**
     * @param request the request parameters of ModifyElasticityAssurance  ModifyElasticityAssuranceRequest
     * @return ModifyElasticityAssuranceResponse
     */
    CompletableFuture modifyElasticityAssurance(ModifyElasticityAssuranceRequest request);

    /**
     * @deprecated OpenAPI ModifyForwardEntry is deprecated  * @param request  the request parameters of ModifyForwardEntry  ModifyForwardEntryRequest
     * @return ModifyForwardEntryResponse
     */
    @Deprecated
    CompletableFuture modifyForwardEntry(ModifyForwardEntryRequest request);

    /**
     * @deprecated OpenAPI ModifyHaVipAttribute is deprecated  * @param request  the request parameters of ModifyHaVipAttribute  ModifyHaVipAttributeRequest
     * @return ModifyHaVipAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyHaVipAttribute(ModifyHaVipAttributeRequest request);

    /**
     * @param request the request parameters of ModifyHpcClusterAttribute  ModifyHpcClusterAttributeRequest
     * @return ModifyHpcClusterAttributeResponse
     */
    CompletableFuture modifyHpcClusterAttribute(ModifyHpcClusterAttributeRequest request);

    /**
     * @param request the request parameters of ModifyImageAttribute  ModifyImageAttributeRequest
     * @return ModifyImageAttributeResponse
     */
    CompletableFuture modifyImageAttribute(ModifyImageAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyImageShareGroupPermission is deprecated, please use Ecs::2014-05-26::ModifyImageSharePermission instead.  * @param request  the request parameters of ModifyImageShareGroupPermission  ModifyImageShareGroupPermissionRequest
     * @return ModifyImageShareGroupPermissionResponse
     */
    @Deprecated
    CompletableFuture modifyImageShareGroupPermission(ModifyImageShareGroupPermissionRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
You can share only your own custom images to other Alibaba Cloud accounts.
     * 
You can share a custom image to up to 10 Alibaba Cloud accounts at a time. You can specify up to 10 Alibaba Cloud account IDs by using AddAccount.N or RemoveAccount.N. If you specify more than 10 account IDs, the system processes only the first 10 account IDs. The excess account IDs are ignored.
     * 
You can share a custom image to up to 50 Alibaba Cloud accounts.
     * 
If an Elastic Compute Service (ECS) instance was created (RunInstances) from a shared image, you cannot re-initialize the instance (ReInitDisk) after the image owner unshares or deletes the image (DeleteImage).
     * When you publish or unpublish a community image, take note of the following items:
     * 
Alibaba Cloud provides only the platform on which community images can be published and managed. The owner of a community image is responsible for the quality and updates of the image. Make sure that you acknowledge and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see Publish a community image.
     * 
You cannot publish encrypted images as community images.
     * 
Community images are publicly available. A community image is available to all Alibaba Cloud accounts in the region where the image resides.
     * 
You cannot share, export, or copy community images.
     * 
After you unpublish a community image, the image is no longer available to other Alibaba Cloud accounts. If an image is shared to other Alibaba Cloud accounts before it is unpublished, the image remains available to the accounts.
     * 
     * 
     * @param request the request parameters of ModifyImageSharePermission  ModifyImageSharePermissionRequest
     * @return ModifyImageSharePermissionResponse
     */
    CompletableFuture modifyImageSharePermission(ModifyImageSharePermissionRequest request);

    /**
     * description :
     * 
A private pool is generated after an elasticity assurance or a capacity reservation is created. The private pool is associated with information about the instances that are created by using the resources in the private pool. When you create ECS instances, you can configure the instances to use private pool resources, matching them to active elasticity assurances or capacity reservations.
     * 

     * 
This operation does not require you to restart the instances for the changes to take effect.
     * 
When you call the following operations on an instance, the system attempts to match the instance with active private pools. If the instance is configured to a specific private pool. the call may fail because the private pool is no longer active or does not have sufficient resources. If the call fails, call the ModifyInstanceAttachmentAttributes operation to change the match mode of the private pool to Open.

     * 
StartInstance: starts an instance that is stopped in economical mode.
     * 
ReActivateInstances
     * 
ModifyInstanceChargeType
     * 
ModifyPrepayInstanceSpec
     * 
ReplaceSystemDisk
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceAttachmentAttributes  ModifyInstanceAttachmentAttributesRequest
     * @return ModifyInstanceAttachmentAttributesResponse
     */
    CompletableFuture modifyInstanceAttachmentAttributes(ModifyInstanceAttachmentAttributesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
If the response contains {"OperationLocks": {"LockReason" : "security"}} when you query the information of the instance, the instance is locked for security reasons and no operations are allowed on the instance.
     * Take note of the following items:
     * 

     * 
If you change the hostname (HostName), restart the instance in the ECS console or by calling the RebootInstance operation for the new hostname to take effect. For information about how to restart an instance in the ECS console, see Restart an instance. The new hostname may not take effect if you restart the instance from within the operating system.
     * 
If you reset the password (Password), take note of the following items:

     * 
The instance cannot be in the Starting (Starting) state.
     * 
After you reset the password, restart the instance in the ECS console or by calling the RebootInstance operation for the new password to take effect. For information about how to restart an instance in the ECS console, see Restart an instance. The new password does not take effect if you restart the instance from within the operating system.
     * 
     * 
     * 
If you modify user data (UserData), take note of the following items: The instance must meet the limits for user data. For more information, see Instance user data.
     * **
     * Note After you restart the instance, the new user data is displayed but not run as scripts.
     * 
If you change the security groups (SecurityGroupIds.N), take note of the following items:

     * 
You can move the instance to a security group of a different type. If you want to move the instance to a security group of a different type, you must familiarize yourself with the differences between the rule configurations of the two security group types to prevent impacts on the instance network.
     * 
Security groups of instances in the classic network cannot be changed. For more information, see the description of SecurityGroupIds.N.
     * 
     * 
     * 
If you change the number of queues supported by the primary elastic network interface (ENI) (NetworkInterfaceQueueNumber), take note of the following items:

     * 
The instance must be in the Stopped (Stopped) state.
     * 
The value of this parameter cannot exceed the maximum number of queues allowed per ENI.
     * 
The total number of queues for all ENIs on the instance cannot exceed the queue quota for the instance type. To query the maximum number of queues per ENI and the queue quota for an instance type, you can call the DescribeInstanceTypes operation and view the values of the MaximumQueueNumberPerEni and TotalEniQueueQuantity response parameters.
     * 
If you set this parameter to -1, the value is reset to the default value for the instance type. To query the default number of queues supported per primary ENI for an instance type, you can call the DescribeInstanceTypes operation and view the value of the PrimaryEniQueueNumber response parameter.
     * 
     * 
     * 
If you enable or disable the Jumbo Frames feature (EnableJumboFrame), take note of the following items. For more information, see MTUs.

     * 
The instance must be in the Running (Running) or Stopped (Stopped) state.
     * 
The instance must reside in a virtual private cloud (VPC).
     * 
After the Jumbo Frames feature is enabled, the MTU value of the instance is set to 8500. After the Jumbo Frames feature is disabled, the MTU value of the instance is set to 1500.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceAttribute  ModifyInstanceAttributeRequest
     * @return ModifyInstanceAttributeResponse
     */
    CompletableFuture modifyInstanceAttribute(ModifyInstanceAttributeRequest request);

    /**
     * @param request the request parameters of ModifyInstanceAutoReleaseTime  ModifyInstanceAutoReleaseTimeRequest
     * @return ModifyInstanceAutoReleaseTimeResponse
     */
    CompletableFuture modifyInstanceAutoReleaseTime(ModifyInstanceAutoReleaseTimeRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that you are familiar with the billing methods and pricing of Elastic Compute Service (ECS). For more information, see the Elastic Compute Service product page.
     * 

     * 
The payment for auto-renewal of an instance is automatically deducted at 08:00:00 (UTC+8) nine days before the instance expires.
     * 
If the deduction fails, Alibaba Cloud attempts to deduct the payment every day until the payment is deducted or until the instance is locked after the nine-day period ends. Make sure that your account balance or credit balance is sufficient.
     * 
     * 
     * @param request the request parameters of ModifyInstanceAutoRenewAttribute  ModifyInstanceAutoRenewAttributeRequest
     * @return ModifyInstanceAutoRenewAttributeResponse
     */
    CompletableFuture modifyInstanceAutoRenewAttribute(ModifyInstanceAutoRenewAttributeRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that you are familiar with the billing methods and pricing of Elastic Compute Service (ECS). For more information, see the Elastic Compute Service product page.
     * Take note of the following items:
     * 

     * 
The instances must be in the Running (Running) or Stopped (Stopped) state, and you cannot have overdue payments for them.
     * 
After you change the billing method, outstanding payments are automatically completed. Make sure that your account balance is sufficient. Otherwise, your order becomes invalid and is canceled. If your account balance is insufficient, you can set AutoPay to false to generate an unpaid order. Then, you can log on to the ECS console to pay for the order.
     * 
Change the billing method from subscription to pay-as-you-go:

     * 
Your ECS usage determines whether the billing method of an instance can be changed from subscription to pay-as-you-go.
     * 
After you change the billing method of an instance from subscription to pay-as-you-go, the new billing method remains in effect for the remaining lifecycle of the instance. The price difference is refunded to the payment account that you used. Vouchers that have been redeemed are not refundable.
     * 
Refund rule: You have a quota for the total refund amount each month, and unused balance of this quota is not carried forward into the next month. After you use up the refund quota of the current month, you can change the billing method only in the next month. The refund amount incurred when you change the billing method is calculated based on the following formula: Number of vCPUs × (Number of remaining days × 24 ± Number of remaining or elapsed hours).
     * 
     * 
     * 
Change the billing method from pay-as-you-go to subscription:

     * 
You can change the billing method of all data disks that are attached to an instance from pay-as-you-go to subscription.
     * 
This operation cannot be called for a pay-as-you-go instance that has an automatic release time set.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceChargeType  ModifyInstanceChargeTypeRequest
     * @return ModifyInstanceChargeTypeResponse
     */
    CompletableFuture modifyInstanceChargeType(ModifyInstanceChargeTypeRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
The instance must be in the Stopped (Stopped) state. The instance is automatically restarted after it is migrated.
     * 
The network type of the instance must be Virtual Private Cloud (VPC).
     * 
The instance and the destination dedicated host to which to migrate the instance must belong to the same account and reside in the same region and zone.
     * 
A pay-as-you-go instance can be migrated to a subscription dedicated host. A subscription instance can be migrated only between subscription dedicated hosts. The expiration date of the subscription instance cannot be later than that of the destination dedicated host.
     * 
You can migrate only pay-as-you-go instances from a shared host to a dedicated host. You cannot migrate subscription instances or preemptible instances from a shared host to a dedicated host.
     * 
You can redeploy an instance to a specific dedicated host cluster.
     * 
     * 
     * @param request the request parameters of ModifyInstanceDeployment  ModifyInstanceDeploymentRequest
     * @return ModifyInstanceDeploymentResponse
     */
    CompletableFuture modifyInstanceDeployment(ModifyInstanceDeploymentRequest request);

    /**
     * description :
     * 
This operation is used to modify the maintenance policy of an instance. The maintenance policy consists of the following maintenance attributes:
     * 

     * 
Maintenance window: the time period that you specify for maintenance.
     * 
Maintenance action: the action that you specify in response to instance shutdown.
     * 
     * 
     * @param request the request parameters of ModifyInstanceMaintenanceAttributes  ModifyInstanceMaintenanceAttributesRequest
     * @return ModifyInstanceMaintenanceAttributesResponse
     */
    CompletableFuture modifyInstanceMaintenanceAttributes(ModifyInstanceMaintenanceAttributesRequest request);

    /**
     * @param request the request parameters of ModifyInstanceMetadataOptions  ModifyInstanceMetadataOptionsRequest
     * @return ModifyInstanceMetadataOptionsResponse
     */
    CompletableFuture modifyInstanceMetadataOptions(ModifyInstanceMetadataOptionsRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a subscription (PrePaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, a public IP address is automatically assigned to the instance.
     * 
If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a pay-as-you-go (PostPaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, no public IP address is automatically assigned to the instance. In this case, you can set AllocatePublicIp to true or call the AllocatePublicIpAddress operation to assign a public IP address to the instance.
     * 
You can upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of an instance in the classic network from 0 Mbit/s only if the instance is in the Stopped state.

     * 
 For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the Public bandwidth limits section of the "Limits" topic.
     * 
     * 
     * 
Billing:

     * 
After the bandwidth is upgraded, AutoPay is set to true by default and the payment is automatically made. Make sure that your account balance is sufficient. Otherwise, your order becomes invalid and is canceled. If your account balance is insufficient, you can set AutoPay to false. In this case, when you call the ModifyInstanceNetworkSpec operation, an unpaid order is generated. Then, you can log on to the ECS console to pay for the order.
     * 
After the bandwidth is downgraded, the price difference is refunded to the payment account that you used. Vouchers or coupons that have been redeemed are not refundable.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceNetworkSpec  ModifyInstanceNetworkSpecRequest
     * @return ModifyInstanceNetworkSpecResponse
     */
    CompletableFuture modifyInstanceNetworkSpec(ModifyInstanceNetworkSpecRequest request);

    /**
     * description :
     * 
Before you call this operation, familiarize yourself with the billing and pricing of ECS resources.*
     * Before you change the instance type of a pay-as-you-go instance, call the DescribeResourcesModification operation to query compatible instance types.
     * Considerations
     * 

     * 
Make sure that you have no overdue payments in your account.
     * 
You can change only the instance type or only the public bandwidth of an ECS instance at a time. The instance type and the public bandwidth of an ECS instance cannot be changed together.
     * 
You can change the public bandwidth of an ECS instance only when the instance is in the Running (Running) or Stopped (Stopped) state. The change immediately takes effect.
     * 
You can change the instance type of an ECS instance only when the instance is in the Stopped (Stopped) state. You must start the instance for the change to take effect.

     * 
 A limit is imposed on the sum of public bandwidths of all ECS instances that use the pay-by-bandwidth billing method for network usage per region in an Alibaba Cloud account. For more information, see the Public bandwidth limits section of the "Limits and quotas" topic.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceSpec  ModifyInstanceSpecRequest
     * @return ModifyInstanceSpecResponse
     */
    CompletableFuture modifyInstanceSpec(ModifyInstanceSpecRequest request);

    /**
     * description :
     * 
  The VNC password must be six characters in length and can contain uppercase letters, lowercase letters, and digits.
     * 

     * 
After you modify the VNC password of an ECS instance, take note of the following items:

     * 
If the instance is I/O optimized, the new password takes effect immediately without the need to restart the instance.
     * 
If the instance is not I/O optimized, you must restart the instance in the ECS console or by calling the RebootInstance operation for the new password to take effect.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceVncPasswd  ModifyInstanceVncPasswdRequest
     * @return ModifyInstanceVncPasswdResponse
     */
    CompletableFuture modifyInstanceVncPasswd(ModifyInstanceVncPasswdRequest request);

    /**
     * description :
     * 
Usage notes
     * 
The instance that you want to manage must be in the Stopped (Stopped) state.
     * 

     * 
When you call this operation to change the private IP address or vSwitch of an instance, take note of the following items:

     * 
If the instance is a new instance, you must restart the instance before you call this operation.
     * 
After the private IP address or vSwitch of the instance is changed, you must restart the instance before you can recall this operation.
     * 
     * 
     * 
When you call this operation to change the VPC of an instance, take note of the following items:

     * 
Instance:

     * 
The instance cannot be associated with Server Load Balancer (SLB) instances.
     * 
The instance cannot be in the Locked, To Be Released, Expired, Expired and Being Recycled, or Overdue and Being Recycled state. For more information, see Instance lifecycle.
     * 
The instance cannot be used in other Alibaba Cloud services. For example, the instance cannot be in the process of being migrated or having its VPC changed, or the databases deployed on the instance cannot be managed by Data Transmission Service (DTS).
     * 
     * 
     * 
Network:

     * 
The cut-through mode or the multi-elastic IP address (EIP)-to-elastic network interface (ENI) mode cannot be enabled for the instance.
     * 
The instance cannot be associated with a high-availability virtual IP address (HAVIP).
     * 
The vSwitch of the instance cannot be associated with a custom route table.
     * 
Global Accelerator (GA) cannot be activated for the instance.
     * 
The instance cannot have secondary ENIs.
     * 
The instance cannot be assigned an IPv6 address.
     * 
The primary ENI of the instance cannot be associated with multiple IP addresses.
     * 
The new vSwitch that you specify must belong to the new VPC.
     * 
The original and new vSwitches must reside in the same zone.
     * 
If you assign a private IP address to the primary ENI of the instance, the private IP address must be an idle IP address within the CIDR block of the new vSwitch. If you do not assign a private IP address to the primary ENI of the instance, a private IP address is randomly assigned to the ENI. Make sure that sufficient IP addresses are available in the CIDR block of the new vSwitch.
     * 
The Alibaba Cloud account that owns the new VPC cannot share the VPC with other accounts.
     * 
     * 
     * 
Security group (SecurityGroupId.N):

     * 
All security groups must be of the same type.
     * 
The valid values of N vary based on the maximum number of security groups to which an instance can belong. For more information, see the "Security group limits" section in Limits.
     * 
The security groups that you specify must belong to the new VPC.
     * 
You can switch the instance to security groups of a different type. To ensure network connectivity, we recommend that you understand the differences in rule configurations of the two security group types before you switch an instance to security groups of a different type. For more information, see Overview.
     * 
     * 
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyInstanceVpcAttribute  ModifyInstanceVpcAttributeRequest
     * @return ModifyInstanceVpcAttributeResponse
     */
    CompletableFuture modifyInstanceVpcAttribute(ModifyInstanceVpcAttributeRequest request);

    /**
     * description :
     * 
  You can modify the execution information of a task that runs a command in one of the following modes. To query the execution mode of a command, you can call the DescribeInvocations operation and check the RepeatMode value in the response.
     *     *   Period: The task runs the command on a schedule.
     *     *   NextRebootOnly: The task runs the command the next time the associated instances start.
     *     *   EveryReboot: The task runs the command every time the associated instances start.
     * 

     * 
You can modify the execution information of a command task in one of the following execution states. To query the execution status of a command, you can call the DescribeInvocations operation and check the InvocationStatus value.

     * 
Pending: The command is being verified or sent. When the execution state on at least one instance is Pending, the overall execution state is Pending.
     * 
Running: The command is being run on instances. When the execution state on at least one instance is Running, the overall execution state is Running.
     * 
Scheduled: The command that is set to run on a schedule is sent and waiting to be run. When the execution state on at least one instance is Scheduled, the overall execution state is Scheduled.
     * 
Stopping: The command task is being stopped. When the execution state on at least one instance is Stopping, the overall execution state is Stopping.
     * 
     * 
     * 
Before you modify the execution information of a scheduled task, such as the command content, custom parameters, and execution frequency, make sure that the version of Cloud Assistant Agent on the ECS instances or managed instances associated with the task is later than the following versions:

     * 
Linux: 2.2.3.541
     * 
Windows: 2.1.3.541
     * 
If the InvalidOperation.CloudAssistantVersionUnsupported error code is returned in the response, update Cloud Assistant Agent to the latest version.
     * 
     * 
     * 
You cannot modify CommandContent for a common Cloud Assistant command.
     * 
If you modify the CommandContent value of a command and set KeepCommand to true when you call the InvokeCommand or RunCommand operation to run the command, a new command is added and retained. The new command consumes the quota for Cloud Assistant commands. You can retain up to 500 to 50,000 Cloud Assistant commands in each region. You can apply for a quota increase. For information about how to query and increase quotas, see Manage quotas.
     * 
     * 
     * @param request the request parameters of ModifyInvocationAttribute  ModifyInvocationAttributeRequest
     * @return ModifyInvocationAttributeResponse
     */
    CompletableFuture modifyInvocationAttribute(ModifyInvocationAttributeRequest request);

    /**
     * description :
     * 
Debugging
     * 
OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.
     * 
     * @param request the request parameters of ModifyLaunchTemplateDefaultVersion  ModifyLaunchTemplateDefaultVersionRequest
     * @return ModifyLaunchTemplateDefaultVersionResponse
     */
    CompletableFuture modifyLaunchTemplateDefaultVersion(ModifyLaunchTemplateDefaultVersionRequest request);

    /**
     * description :
     * 
The region ID. The following regions are supported: China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), and China (Hong Kong).
     * You can call the DescribeRegions operation to query the most recent region list.
     * 
     * @param request the request parameters of ModifyManagedInstance  ModifyManagedInstanceRequest
     * @return ModifyManagedInstanceResponse
     */
    CompletableFuture modifyManagedInstance(ModifyManagedInstanceRequest request);

    /**
     * @param request the request parameters of ModifyNetworkInterfaceAttribute  ModifyNetworkInterfaceAttributeRequest
     * @return ModifyNetworkInterfaceAttributeResponse
     */
    CompletableFuture modifyNetworkInterfaceAttribute(ModifyNetworkInterfaceAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyPhysicalConnectionAttribute is deprecated  * @param request  the request parameters of ModifyPhysicalConnectionAttribute  ModifyPhysicalConnectionAttributeRequest
     * @return ModifyPhysicalConnectionAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyPhysicalConnectionAttribute(ModifyPhysicalConnectionAttributeRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The specified CIDR block must be valid. For example, 10.0.0.0/8 is a valid CIDR block while 10.0.0.1/8 is not. For more information, see the What is CIDR? section in the "Network FAQ" topic.
     * 
When you add or delete an entry, you cannot specify duplicate CIDR blocks. Examples:

     * 
For IPv4 CIDR blocks, you cannot specify the 10.0.0.0/8 CIDR block in two entries. You cannot specify the 10.0.0.1/32 CIDR block in one entry and the 10.0.0.1 CIDR block in another entry. The two CIDR blocks are the same.
     * 
For IPv6 CIDR blocks, you cannot specify the 2001:fd01:0:0:0:0:0:0/32 CIDR block in one entry and the 2001:fd01::/32 CIDR block in another entry. The two CIDR blocks are the same.
     * 
     * 
     * 
The CIDR block in an entry to be added cannot the same as that in an entry to be deleted. For example, when you add an entry in which the 10.0.0.0/8 CIDR block is specified, make sure that the 10.0.0.0/8 CIDR block is not specified in an entry to be deleted.
     * 
If you want to modify the description of an entry, you must specify the CIDR block (AddEntry.N.Cidr) and new description (AddEntry.N.Description) for the entry.
     * 
     * 
     * @param request the request parameters of ModifyPrefixList  ModifyPrefixListRequest
     * @return ModifyPrefixListResponse
     */
    CompletableFuture modifyPrefixList(ModifyPrefixListRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that you are familiar with the billing methods, prices, and rules for unsubscribing from resources of ECS.*
     * ModifyPrepayInstanceSpec is an asynchronous operation. After a request is sent, wait for 5 to 10 seconds for the instance type change to complete. Before you change the instance type of a subscription ECS instance, call the DescribeResourcesModification operation to query the instance types to which you can change the instance.
     * Considerations
     * 

     * 
Before you change the instance type of an expired instance, you must renew the instance.
     * 
When you downgrade the instance type of a subscription ECS instance, take note of the following items:

     * 
The instance must be in the Stopped (Stopped) state.
     * 
The price difference is refunded to the payment account that you used. Redeemed vouchers are not refundable.
     * 
The new instance type takes effect only after you start the instance.
     * 
     * 
     * 
When you upgrade the instance type of a subscription ECS instance, take note of the following items:

     * 
The instance must be in the Stopped (Stopped) or Running (Running) state.
     * 
The new instance type takes effect only after you start the instance or restart the instance.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ModifyPrepayInstanceSpec  ModifyPrepayInstanceSpecRequest
     * @return ModifyPrepayInstanceSpecResponse
     */
    CompletableFuture modifyPrepayInstanceSpec(ModifyPrepayInstanceSpecRequest request);

    /**
     * @param request the request parameters of ModifyReservedInstanceAttribute  ModifyReservedInstanceAttributeRequest
     * @return ModifyReservedInstanceAttributeResponse
     */
    CompletableFuture modifyReservedInstanceAttribute(ModifyReservedInstanceAttributeRequest request);

    /**
     * @param request the request parameters of ModifyReservedInstanceAutoRenewAttribute  ModifyReservedInstanceAutoRenewAttributeRequest
     * @return ModifyReservedInstanceAutoRenewAttributeResponse
     */
    CompletableFuture modifyReservedInstanceAutoRenewAttribute(ModifyReservedInstanceAutoRenewAttributeRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to modify a reserved instance, the operation starts the modification process and returns the ID of the resulting new reserved instance. The original reserved instance enters the Updating state and then the Inactive state. At the same time, the resulting new reserved instance is generated and enters the Creating state and then the Active state. You can call the DescribeReservedInstances operation to query the states of the reserved instance.
     * 

     * 
You can modify the configurations of a reserved instance only when the reserved instance is in the Active state.
     * 
Make sure that the computing power of the reserved instance remains unchanged before and after the modification. Otherwise, the modification fails.
     * 
You cannot split, merge, or change the scope of a reserved instance at the same time.
     * For more information, see Split, merge, or modify reserved instances.
     * 
     * 
Sample requests
     * 

     * 
Sample request to split a reserved instance: Split a regional reserved instance that is scoped to the China (Hangzhou) region and can match two pay-as-you-go instances of the ecs.g5.xlarge instance type into two regional reserved instances that are scoped to the China (Hangzhou) region and each can match one pay-as-you-go instance of the ecs.g5.large instance type:
     * "RegionId":"cn-hangzhou", //The ID of the region.
     * "ReservedInstanceId":["ecsri-bp1hd03e9uv19e75****"], //The ID of the reserved instance that you want to split.
     * "Configuration":[
     *   {
     * "ReservedInstanceName":"testReservedInstanceName1", //The name of the new reserved instance.
     * "InstanceType":"ecs.g5.large", //The instance type that the new reserved instance can match.
     * "Scope":"Region", //The scope level of the new reserved instance, which must be the same as the scope level of the original reserved instance.
     * "InstanceAmount":1 //The number of pay-as-you-go instances of the specified instance type that each new reserved instance can match.
     *   },
     *   {
     * "ReservedInstanceName":"testReservedInstanceName2",
     * "InstanceType":"ecs.g5.large",
     * "Scope":"Region",
     * "InstanceAmount":1
     *   }
     * ]
     * 
Sample request to merge reserved instance:: Merge two zonal reserved instances that are scoped to Hangzhou Zone H and can match four pay-as-you-go instances of the ecs.g5.xlarge instance type into one zonal reserved instance that is scoped to Hangzhou Zone H and can match two pay-as-you-go instance of the ecs.g5.4xlarge instance type:
     * "RegionId":"cn-hangzhou", //The ID of the region.
     * "ReservedInstanceId":["ecsri-bp1hd03e9uv16b75****",""ecsri-bp1hd03e9uv16b76****""], //The IDs of the reserved instances that you want to merge.
     * "Configuration":[
     *   {
     * "ReservedInstanceName":"testReservedInstanceName", //The name of the new reserved instance.
     * "InstanceType":"ecs.g5.4xlarge", //The instance type that the new reserved instance can match.
     * "Scope":"Zone", //The scope level of the new reserved instance, which must be the same as the scope level of the original reserved instances.
     * "ZoneId":"cn-hangzhou-h", //
     * "InstanceAmount":2 //The number of pay-as-you-go instances of the specified instance type that the new reserved instance can match.
     *   }
     * ]
     * 
Sample request to change the scope of a reserved instance: Change a regional reserved instance that is scoped to Hangzhou Zone H and can match six pay-as-you-go instances of the ecs.g5.xlarge instance type to a regional reserved instance that is scoped to the China (Hangzhou) region and can match three pay-as-you-go instances of the ecs.g5.2xlarge instance type.
     * "RegionId":"cn-hangzhou", //The ID of the region.
     * "ReservedInstanceId":["ecsri-bp1hd03e9uv16b77****"], //The ID of the reserved instance whose scope you want to change.
     * "Configuration":[
     *   {
     * "ReservedInstanceName":"testReservedInstanceName", //The name of the new reserved instance.
     * "InstanceType":"ecs.g5.2xlarge", //The instance type that the new reserved instance can match.
     * "Scope":"Region", //The scope level of the new reserved instance.
     * "InstanceAmount":3 //The number of pay-as-you-go instances of the specified instance type that the new reserved instance can match.
     *   }
     * ]
     * 
     * 
     * @param request the request parameters of ModifyReservedInstances  ModifyReservedInstancesRequest
     * @return ModifyReservedInstancesResponse
     */
    CompletableFuture modifyReservedInstances(ModifyReservedInstancesRequest request);

    /**
     * @deprecated OpenAPI ModifyRouterInterfaceAttribute is deprecated  * @param request  the request parameters of ModifyRouterInterfaceAttribute  ModifyRouterInterfaceAttributeRequest
     * @return ModifyRouterInterfaceAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyRouterInterfaceAttribute(ModifyRouterInterfaceAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyRouterInterfaceSpec is deprecated  * @param request  the request parameters of ModifyRouterInterfaceSpec  ModifyRouterInterfaceSpecRequest
     * @return ModifyRouterInterfaceSpecResponse
     */
    @Deprecated
    CompletableFuture modifyRouterInterfaceSpec(ModifyRouterInterfaceSpecRequest request);

    /**
     * @param request the request parameters of ModifySecurityGroupAttribute  ModifySecurityGroupAttributeRequest
     * @return ModifySecurityGroupAttributeResponse
     */
    CompletableFuture modifySecurityGroupAttribute(ModifySecurityGroupAttributeRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
An authorization object in a security group rule can be of one of the following types: IPv4 CIDR block or address, IPv6 CIDR block or address, security group, or prefix list. You cannot call this operation to change the type of an existing authorization object. For example, if an authorization object is an IPv4 CIDR block, you can change the authorization object to a different IPv4 CIDR block or an IPv4 address, but you cannot change the authorization object to an IPv6 CIDR block or address, a security group, or a prefix list.
     * 
You cannot delete the value of a non-empty parameter. If you want to delete the values of non-empty parameters, we recommend that you create a security group rule and delete the original security group rule.
     * 
     * 
     * @param request the request parameters of ModifySecurityGroupEgressRule  ModifySecurityGroupEgressRuleRequest
     * @return ModifySecurityGroupEgressRuleResponse
     */
    CompletableFuture modifySecurityGroupEgressRule(ModifySecurityGroupEgressRuleRequest request);

    /**
     * description :
     * 
  By default, advanced security groups use the internal isolation policy, and Elastic Compute Service (ECS) instances in each advanced security group cannot communicate with each other. The internal access control policy of advanced security groups cannot be modified.
     * 

     * 
You can call the DescribeSecurityGroupAttribute operation to query the internal access control policy of a security group.
     * 
If the internal access control policy of a security group is set to Accept, the security group uses the internal interconnectivity policy and all ECS instances in the security group can communicate with each other over the internal network, regardless of whether custom rules exist in the security group.
     * 
If the internal access control policy of a security group is set to Drop and the security group contains no custom rules, the security group uses the internal isolation policy and all ECS instances in the security group cannot communicate with each other over the internal network. In this case, you can use custom rules to allow ECS instances in the security group to communicate with each other. For example, you can call the AuthorizeSecurityGroup operation to configure custom rules.
     * 
     * 
     * @param request the request parameters of ModifySecurityGroupPolicy  ModifySecurityGroupPolicyRequest
     * @return ModifySecurityGroupPolicyResponse
     */
    CompletableFuture modifySecurityGroupPolicy(ModifySecurityGroupPolicyRequest request);

    /**
     * description :
     * 
Take note of the following items:
     * 

     * 
An authorization object in a security group rule can be of one of the following types: IPv4 CIDR block or address, IPv6 CIDR block or address, security group, or prefix list. You cannot call this operation to change the type of an existing authorization object. For example, if an authorization object is an IPv4 CIDR block, you can change the authorization object to a different IPv4 CIDR block or an IPv4 address, but you cannot change the authorization object to an IPv6 CIDR block or address, a security group, or a prefix list.
     * 
You cannot delete the value of a non-empty parameter. If you want to delete the values of non-empty parameters, we recommend that you create a security group rule and delete the original security group rule.
     * 
     * 
     * @param request the request parameters of ModifySecurityGroupRule  ModifySecurityGroupRuleRequest
     * @return ModifySecurityGroupRuleResponse
     */
    CompletableFuture modifySecurityGroupRule(ModifySecurityGroupRuleRequest request);

    /**
     * @param request the request parameters of ModifySnapshotAttribute  ModifySnapshotAttributeRequest
     * @return ModifySnapshotAttributeResponse
     */
    CompletableFuture modifySnapshotAttribute(ModifySnapshotAttributeRequest request);

    /**
     * @param request the request parameters of ModifySnapshotGroup  ModifySnapshotGroupRequest
     * @return ModifySnapshotGroupResponse
     */
    CompletableFuture modifySnapshotGroup(ModifySnapshotGroupRequest request);

    /**
     * @param request the request parameters of ModifyStorageCapacityUnitAttribute  ModifyStorageCapacityUnitAttributeRequest
     * @return ModifyStorageCapacityUnitAttributeResponse
     */
    CompletableFuture modifyStorageCapacityUnitAttribute(ModifyStorageCapacityUnitAttributeRequest request);

    /**
     * @param request the request parameters of ModifyStorageSetAttribute  ModifyStorageSetAttributeRequest
     * @return ModifyStorageSetAttributeResponse
     */
    CompletableFuture modifyStorageSetAttribute(ModifyStorageSetAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyUserBusinessBehavior is deprecated  * @param request  the request parameters of ModifyUserBusinessBehavior  ModifyUserBusinessBehaviorRequest
     * @return ModifyUserBusinessBehaviorResponse
     */
    @Deprecated
    CompletableFuture modifyUserBusinessBehavior(ModifyUserBusinessBehaviorRequest request);

    /**
     * @deprecated OpenAPI ModifyVRouterAttribute is deprecated  * @param request  the request parameters of ModifyVRouterAttribute  ModifyVRouterAttributeRequest
     * @return ModifyVRouterAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyVRouterAttribute(ModifyVRouterAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyVSwitchAttribute is deprecated  * @param request  the request parameters of ModifyVSwitchAttribute  ModifyVSwitchAttributeRequest
     * @return ModifyVSwitchAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyVSwitchAttribute(ModifyVSwitchAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyVirtualBorderRouterAttribute is deprecated  * @param request  the request parameters of ModifyVirtualBorderRouterAttribute  ModifyVirtualBorderRouterAttributeRequest
     * @return ModifyVirtualBorderRouterAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyVirtualBorderRouterAttribute(ModifyVirtualBorderRouterAttributeRequest request);

    /**
     * @deprecated OpenAPI ModifyVpcAttribute is deprecated  * @param request  the request parameters of ModifyVpcAttribute  ModifyVpcAttributeRequest
     * @return ModifyVpcAttributeResponse
     */
    @Deprecated
    CompletableFuture modifyVpcAttribute(ModifyVpcAttributeRequest request);

    /**
     * description :
     * 
Before you call this operation, familiarize yourself with the billing rules and pricing of elasticity assurances.
     * Before you purchase an elasticity assurance, you can call the DescribeElasticityAssurances operation to query the elasticity assurances that you can purchase.
     * 
     * @param request the request parameters of PurchaseElasticityAssurance  PurchaseElasticityAssuranceRequest
     * @return PurchaseElasticityAssuranceResponse
     */
    CompletableFuture purchaseElasticityAssurance(PurchaseElasticityAssuranceRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that you are familiar with the billing methods and pricing of reserved instances.*
     * 

     * 
Before you call this operation, make sure that you are familiar with the billing rules of reserved instances. For more information, see Reserved instances.
     * 
You can retain up to 20 regional reserved instances in all regions per Alibaba Cloud account.
     * 
You can retain up to 20 zonal reserved instances per zone per Alibaba Cloud account.
     * 
     * 
Sample requests
     * 

     * 
Purchase a one-year regional reserved instance in the China (Hangzhou) region to offset the bills of three ecs.g5.large Linux pay-as-you-go instances.
     * "RegionId":"cn-hangzhou", // Specify the China (Hangzhou) region."InstanceType":"ecs.g5.large", // Specify the instance type."Scope":"Region", // Set the scope of the reserved instance to regional."InstanceAmount":3, // Specify the reserved instance to match three pay-as-you-go instances of the same instance type."OfferingType":"All Upfront", // Specify the payment option. In this example, the default value is used, which is All Upfront."Platform":"Linux", // Specify the operating system platform of the ECS instances eligible for the reserved instance. In this example, the Linux or Unix-like operating system is used."Period":1, // Specify the term of the reserved instance. In this example, the one-year duration is used."PeriodUnit":"Year", // Set the unit of the term to year.
     * 
Purchase a two-year zonal reserved instance in Hangzhou Zone H to offset the bills of five ecs.g5.large Windows pay-as-you-go instances.
     * "RegionId":"cn-hangzhou",
     * "ZoneId":"cn-hangzhou-h", // Specify Hangzhou Zone H."InstanceType":"ecs.g5.large",
     * "Scope":"Zone", // Set the scope of the reserved instance to zonal."InstanceAmount":5, // Specify the reserved instance to match five pay-as-you-go instances of the same instance type."OfferingType":"All Upfront",
     * "Platform":"Windows", // Specify the operating system platform of the ECS instances eligible for the reserved instance. In this example, the Windows operating system is used."Period":2, // Specify the term of the reserved instance. In this example, the two-year duration is used."PeriodUnit":"Year", // Set the unit of the term to year.
     * 
     * 
     * @param request the request parameters of PurchaseReservedInstancesOffering  PurchaseReservedInstancesOfferingRequest
     * @return PurchaseReservedInstancesOfferingResponse
     */
    CompletableFuture purchaseReservedInstancesOffering(PurchaseReservedInstancesOfferingRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Before you call this operation, make sure that you are familiar with the billing and pricing of SCUs. For more information, see Storage capacity units.
     * 
     * @param request the request parameters of PurchaseStorageCapacityUnit  PurchaseStorageCapacityUnitRequest
     * @return PurchaseStorageCapacityUnitResponse
     */
    CompletableFuture purchaseStorageCapacityUnit(PurchaseStorageCapacityUnitRequest request);

    /**
     * description :
     * 
  You cannot call this operation to start ECS instances that are locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 

     * 
The instance must be in the Stopped (Stopped) state.
     * 
You must pay the bills and reactivate the instance within 15 days after the instance is suspended due to overdue payments. Otherwise, the instance is released and the data cannot be restored. If you cannot restart an instance of the Virtual Private Cloud (VPC) type, try again later.
     * 
After the operation is called, the instance enters the Starting (Starting) state.
     * 
     * 
     * @param request the request parameters of ReActivateInstances  ReActivateInstancesRequest
     * @return ReActivateInstancesResponse
     */
    CompletableFuture reActivateInstances(ReActivateInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
The disk that you want to re-initialize must be in the In Use (In_use) state and the instance to which the disk is attached must be in the Stopped (Stopped) state.
     * 
If an instance has never been started since it was created, the disks attached to it cannot be re-initialized.
     * 
If a local snapshot has been created for a disk, the disk cannot be re-initialized.
     * 
If a system disk is re-initialized, the disk is restored to the state of the image from which it was created. If the image has been deleted, the disk cannot be re-initialized.
     * 
If a separately created data disk is re-initialized, the disk is restored to an empty data disk.
     * 
If a data disk that was created from a snapshot is re-initialized, the disk is restored to the state of the snapshot.

     * 
 If the source snapshot is deleted, the disk cannot be re-initialized and an error is returned.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ReInitDisk  ReInitDiskRequest
     * @return ReInitDiskResponse
     */
    CompletableFuture reInitDisk(ReInitDiskRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to restart an ECS instance, the operation sets the status of the ECS instance to Starting and begins the restart process. You can call the DescribeInstanceStatus operation to query the status of the ECS instance. When the status of the ECS instance changes to Running, the instance is restarted.
     * 

     * 
Notes

     * 
You cannot call this operation to restart an ECS instance that is locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
The ECS instance that you want to restart must be in the Running (Running) state.
     * 
     * 
     * 
     * 
     * @param request the request parameters of RebootInstance  RebootInstanceRequest
     * @return RebootInstanceResponse
     */
    CompletableFuture rebootInstance(RebootInstanceRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to restart an ECS instance, the operation sets the status of the ECS instance to Starting and begins the restart process. You can call the DescribeInstanceStatus operation to query the status of the instance. When the status of the ECS instance changes to Running, the instance is restarted.
     * 
Limits
     * 

     * 
You cannot call this operation to restart ECS instances that are locked due to security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
The ECS instances that you want to restart must be in the Running (Running) state.
     * 
     * 
     * @param request the request parameters of RebootInstances  RebootInstancesRequest
     * @return RebootInstancesResponse
     */
    CompletableFuture rebootInstances(RebootInstancesRequest request);

    /**
     * @deprecated OpenAPI RecoverVirtualBorderRouter is deprecated  * @param request  the request parameters of RecoverVirtualBorderRouter  RecoverVirtualBorderRouterRequest
     * @return RecoverVirtualBorderRouterResponse
     */
    @Deprecated
    CompletableFuture recoverVirtualBorderRouter(RecoverVirtualBorderRouterRequest request);

    /**
     * description :
     * 
If a dedicated host is in the UnderAssessment state, we recommend that you call this operation to migrate ECS instances away from the dedicated host to prevent permanent failures. You can call the DescribeDedicatedHosts operation to query the status of a dedicated host.
     * 
     * @param request the request parameters of RedeployDedicatedHost  RedeployDedicatedHostRequest
     * @return RedeployDedicatedHostResponse
     */
    CompletableFuture redeployDedicatedHost(RedeployDedicatedHostRequest request);

    /**
     * description :
     * 
RedeployInstance is an asynchronous operation. This operation migrates data before it restarts the instance. After the instance is redeployed, the instance enters the Running state. If the instance fails to be redeployed, the instance returns to the original physical server and the state before redeployment.
     * Take note of the following items:
     * 

     * 
The instance must be in the Running or Stopped state. After the instance is redeployed, the following changes occur to the status of the instance:

     * 
If the instance is in the Running state before redeployment, the instance enters the Stopping state.
     * 
If the instance is in the Stopped state before redeployment, the instance enters the Starting state.
     * 
     * 
     * 
If an instance is deployed on a dedicated host, you cannot redeploy the instance.
     * 
If the OperationLocks parameter in the response of the DescribeInstances operation contains "LockReason" : "security" for an instance, the instance is locked for security reasons and cannot be redeployed.
     * 
If you receive notifications about simulated events that are created by calling the CreateSimulatedSystemEvent operation for an instance, you cannot redeploy the instance.
     * 
If the damaged local disk is isolated but the SystemMaintenance.RebootAndReInitErrorDisk event is not sent when you handle a local disk-related system event for an instance, you can still call the RedeployInstance operation to redeploy the instance. The SystemMaintenance.RebootAndReInitErrorDisk event indicates that the instance is restarted and the damaged disks are reinitialized due to system maintenance. For more information, see System events for ECS instances equipped with local disks.
     * The following table describes the system events that you can handle by calling the RedeployInstance operation. The table also provides possible event status.
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
     * 
System event
Event status
Instance restart due to system maintenance (SystemMaintenance.Reboot)
Inquiring and Scheduled
Instance redeployment due to system maintenance (SystemMaintenance.Redeploy)
Inquiring and Scheduled
Instance restart and replacement of damaged disks due to system maintenance (SystemMaintenance.RebootAndIsolateErrorDisk)
Inquiring
Instance restart and re-initialization of damaged disks due to system maintenance (SystemMaintenance.RebootAndReInitErrorDisk)
Inquiring
Instance redeployment due to system errors (SystemFailure.Redeploy)
Inquiring and Scheduled
For ECS instances that use only local disks: instance restart due to a system error (SystemFailure.Reboot)
Executing
Isolation of damaged disks due to system maintenance (SystemMaintenance.IsolateErrorDisk)
Inquiring
Re-initialization of damaged disks due to system maintenance (SystemMaintenance.ReInitErrorDisk)
Inquiring
NoteWhen instances that use local disks are redeployed, the local disks are re-initialized and data on the local disks is cleared.

     * 
     * 
     * 
     * @param request the request parameters of RedeployInstance  RedeployInstanceRequest
     * @return RedeployInstanceResponse
     */
    CompletableFuture redeployInstance(RedeployInstanceRequest request);

    /**
     * description :
     * 
If the release mode of a capacity reservation that takes effect immediately is set to manual release, you can call this operation to release the capacity reservation.
     * 
     * @param request the request parameters of ReleaseCapacityReservation  ReleaseCapacityReservationRequest
     * @return ReleaseCapacityReservationResponse
     */
    CompletableFuture releaseCapacityReservation(ReleaseCapacityReservationRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Before you release a pay-as-you-go dedicated host, make sure that no ECS instances are deployed on the dedicated host.
     * 
     * @param request the request parameters of ReleaseDedicatedHost  ReleaseDedicatedHostRequest
     * @return ReleaseDedicatedHostResponse
     */
    CompletableFuture releaseDedicatedHost(ReleaseDedicatedHostRequest request);

    /**
     * @deprecated OpenAPI ReleaseEipAddress is deprecated  * @param request  the request parameters of ReleaseEipAddress  ReleaseEipAddressRequest
     * @return ReleaseEipAddressResponse
     */
    @Deprecated
    CompletableFuture releaseEipAddress(ReleaseEipAddressRequest request);

    /**
     * @param request the request parameters of ReleasePublicIpAddress  ReleasePublicIpAddressRequest
     * @return ReleasePublicIpAddressResponse
     */
    CompletableFuture releasePublicIpAddress(ReleasePublicIpAddressRequest request);

    /**
     * @deprecated OpenAPI RemoveBandwidthPackageIps is deprecated  * @param request  the request parameters of RemoveBandwidthPackageIps  RemoveBandwidthPackageIpsRequest
     * @return RemoveBandwidthPackageIpsResponse
     */
    @Deprecated
    CompletableFuture removeBandwidthPackageIps(RemoveBandwidthPackageIpsRequest request);

    /**
     * @param request the request parameters of RemoveTags  RemoveTagsRequest
     * @return RemoveTagsResponse
     */
    CompletableFuture removeTags(RemoveTagsRequest request);

    /**
     * description :
     * 
Usage notes
     * 
When you renew subscription dedicated hosts, vouchers are used first by default. Make sure that your account supports credit card payments or balance payments.
     * 
     * @param request the request parameters of RenewDedicatedHosts  RenewDedicatedHostsRequest
     * @return RenewDedicatedHostsResponse
     */
    CompletableFuture renewDedicatedHosts(RenewDedicatedHostsRequest request);

    /**
     * @param request the request parameters of RenewElasticityAssurances  RenewElasticityAssurancesRequest
     * @return RenewElasticityAssurancesResponse
     */
    CompletableFuture renewElasticityAssurances(RenewElasticityAssurancesRequest request);

    /**
     * description :
     * 
  Before you call this operation, make sure that you are familiar with the billing methods and pricing of ECS. For more information, see the Elastic Compute Service product page.
     * 

     * 
You can call this operation to renew a subscription instance for a specific period of time or to a synchronized expiration date.
     * 
You cannot call this operation to renew a subscription instance for a specific period of time and to a synchronized expiration date at the same time. The parameter pair (Period and PeriodUnit) that is related to the renewal period and ExpectedRenewDay are mutually exclusive.
     * 
Your account must have sufficient credits.
     * 
     * 
     * @param request the request parameters of RenewInstance  RenewInstanceRequest
     * @return RenewInstanceResponse
     */
    CompletableFuture renewInstance(RenewInstanceRequest request);

    /**
     * description :
     * 
Before you call this operation, make sure that you are familiar with the billing and pricing of reserved instances.*
     * 

     * 
You can manually renew reserved instances or enable auto-renewal for reserved instances. For more information, see the Renewal section of the "Reserved instances" topic.
     * 
You can call the DescribeReservedInstances operation to query the reserved instances that you purchased.
     * 
You can call this operation to enable auto-renewal for reserved instances but cannot call this operation to disable auto-renewal for reserved instances. To disable auto-renewal for a reserved instance, call the ModifyReservedInstanceAutoRenewAttribute operation.
     * 
     * 
     * @param request the request parameters of RenewReservedInstances  RenewReservedInstancesRequest
     * @return RenewReservedInstancesResponse
     */
    CompletableFuture renewReservedInstances(RenewReservedInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
The category of the system disk cannot be changed.
     * 
The billing method of the system disk cannot be changed.
     * 
The instance must be in the Stopped state.
     * **
     * Note The operation is applicable only to instances of the Virtual Private Cloud (VPC) type. If the instance is a pay-as-you-go instance and economical mode is enabled by default for the instance, you must disable economical mode and enable standard mode when you stop the instance. This prevents the instance from being unable to restart due to insufficient ECS resources after the system disk is replaced. For more information, see StopInstance.
     * 
The ECS instance cannot be locked for security reasons. If the value of OperationLocks in the DescribeInstances response contains "LockReason": "security" for an instance, the instance is locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
No unpaid orders are associated with the instance.
     * 
You can configure SystemDisk.Size to specify the capacity of the new system disk.
     * After you call the ReplaceSystemDisk operation, you can use one of the following methods to check whether the system disk is replaced:
     * 
Call the DescribeDisks operation to query the status of the new system disk. If the new system disk is in the In Use state, the system disk is replaced.
     * 
Call the DescribeInstances operation to query the status of the instance whose system disk is replaced. If the OperationLocks parameter is empty, the system disk is replaced.
     * 
     * 
     * @param request the request parameters of ReplaceSystemDisk  ReplaceSystemDiskRequest
     * @return ReplaceSystemDiskResponse
     */
    CompletableFuture replaceSystemDisk(ReplaceSystemDiskRequest request);

    /**
     * @param request the request parameters of ReportInstancesStatus  ReportInstancesStatusRequest
     * @return ReportInstancesStatusResponse
     */
    CompletableFuture reportInstancesStatus(ReportInstancesStatusRequest request);

    /**
     * description :
     * 
When you call this operation, take note of the following items:
     * 

     * 
The disk must be in the In Use (In_Use) or Unattached (Available) state.
     * 
The Elastic Compute Service (ECS) instance to which the disk is attached must be in the Stopped (Stopped) state. You can call the StopInstances operation to stop an instance.
     * 
The snapshot specified by the SnapshotId parameter must be created from the disk specified by the DiskId parameter.
     * 
When you call the DescribeInstances operation to query instance information and the response contains {"OperationLocks": {"LockReason" : "security"}}, then this indicates that the instance is locked for security reasons and no operations can be performed on the instance.
     * 
     * 
     * @param request the request parameters of ResetDisk  ResetDiskRequest
     * @return ResetDiskResponse
     */
    CompletableFuture resetDisk(ResetDiskRequest request);

    /**
     * description :
     * 
  Only Alibaba Cloud accounts can call this operation.
     * 

     * 
Before you can call this operation in a region, you must enable account-level default encryption of Elastic Block Storage (EBS) resources in the region.
     * 
     * 
     * @param request the request parameters of ResetDiskDefaultKMSKeyId  ResetDiskDefaultKMSKeyIdRequest
     * @return ResetDiskDefaultKMSKeyIdResponse
     */
    CompletableFuture resetDiskDefaultKMSKeyId(ResetDiskDefaultKMSKeyIdRequest request);

    /**
     * description :
     * 
This operation will be removed in the future. We recommend that you call the ResetDisk operation to roll back a disk.
     * 
     * @param request the request parameters of ResetDisks  ResetDisksRequest
     * @return ResetDisksResponse
     */
    CompletableFuture resetDisks(ResetDisksRequest request);

    /**
     * description :
     * 

     * 
 Before you call this operation to resize a disk, you must check the partition format of the disk. You cannot resize a master boot record (MBR) disk to a size that is larger than 2 TiB. If you resize an MBR disk to a size that is larger than 2 TiB, data may be lost. If you want to resize an MBR disk to a size that is larger than 2 TiB, we recommend that you perform the following steps: Create a new data disk that is larger than 2 TiB in size, partition and format the new data disk by using the GUID Partition Table (GPT) format, and then copy data from the MBR disk to the GPT data disk. For more information, see Step 1: Resize a disk to extend the capacity of the disk.
     * 
     * 

     * 
You can resize disks of the following disk categories: basic disks (cloud), ultra disks (cloud_efficiency), standard SSDs (cloud_ssd), Enterprise SSDs (ESSDs) (cloud_essd), ESSD AutoPL disks (cloud_auto), standard elastic ephemeral disks (elastic_ephemeral_disk_standard), and premium elastic ephemeral disks (elastic_ephemeral_disk_premium).
     * 
You cannot resize a disk for which a snapshot is being created. Wait until the snapshot is created before you resize the disk.
     * 
You cannot call this operation to resize partitions or file systems on a disk. You must manually resize the partitions and file systems after the disk is resized. For more information, see Step 2: Resize partitions and file systems.
     * 
If the multi-attach feature is enabled for a disk, you can resize the disk online or offline. Make sure that the Elastic Compute Service (ECS) instances to which the disk is attached meet the following requirements:

     * 
If you want to resize the disk online, the ECS instances must be in the Running (Running) state.
     * 
If you want to resize the disk offline, the ECS instances must be in the Running (Running) or Stopped (Stopped) state.
     * 
     * 
     * 
The disk that you want to resize must meet the following requirements:

     * 
The disk is in the In_use (In Use) or Available (Unattached) state.
     * 
(Recommended) Snapshots are created for the disk to back up disk data. For information about how to create snapshots for a disk, see Create a snapshot.
     * 
If the disk is a new data disk, initialize the disk before you resize the disk. For more information, see Overview.
     * 
     * 
     * 
     * 
     * @param request the request parameters of ResizeDisk  ResizeDiskRequest
     * @return ResizeDiskResponse
     */
    CompletableFuture resizeDisk(ResizeDiskRequest request);

    /**
     * description :
     * 
In the security group-related API documents, inbound traffic refers to the traffic sent by the source and received by the destination.
     * When you call this operation, you can use one of the following groups of parameters to specify the security group rules that you want to delete:
     * 

     * 
Parameters used to specify the IDs of security group rules. We recommend that you specify the IDs of security group rules to delete the rules. - If the security group rule ID that you specify does not exist, an error is reported. - You cannot specify the parameters that are no longer available and their Permissions.N-prefixed counterparts at the same time. - Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &SecurityGroupRuleId.1=sgr-bpdfmk****
     * &SecurityGroupRuleId.2=sgr-bpdfmg****
     * &
     * 
Parameters that are prefixed with Permissions.N.

     * 
If no security group rule matches the specified parameters, the call to RevokeSecurityGroup is successful but no security group rules are deleted.
     * 
You cannot specify SecurityGroupRuleId.N or the parameters that are not prefixed with Permissions.N.
     * 
You can determine an inbound security group rule by specifying one of the following groups of parameters. You cannot determine an inbound security group rule by specifying only one parameter.
     * 
Parameters used to determine an inbound security group rule that controls access from a CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestCidrIp (optional), and SourceCidrIp. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourceCidrIp=10.0.0.0/8
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=80/80
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
Parameters used to determine an inbound security group rule that controls access from another security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestCidrIp (optional), and SourceGroupId. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourceGroupId=sg-bp67acfmxa123b****
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=80/80
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
Parameters used to determine an inbound security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestCidrIp (optional), and SourcePrefixListId. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroup
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=80/80
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
     * 
     * 
     * 
     * @param request the request parameters of RevokeSecurityGroup  RevokeSecurityGroupRequest
     * @return RevokeSecurityGroupResponse
     */
    CompletableFuture revokeSecurityGroup(RevokeSecurityGroupRequest request);

    /**
     * description :
     * 
In the security group-related API documents, outbound traffic refers to the traffic sent by the source and received by the destination.
     * When you call this operation, you can use one of the following groups of parameters to specify the security group rules that you want to delete:
     * 

     * 
Parameters used to specify the IDs of security group rules. We recommend that you specify the IDs of security group rules to delete the rules. - If the security group rule ID that you specify does not exist, an error is reported. - You cannot specify the parameters that are no longer available and their Permissions.N-prefixed counterparts at the same time. - Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
     * &SecurityGroupId=sg-bp67acfmxazb4p****
     * &SecurityGroupRuleId.1=sgr-bpdfmk****
     * &SecurityGroupRuleId.2=sgr-bpdfmg****
     * &
     * 
Parameters that are prefixed with Permissions.N.

     * 
If no security group rule matches the specified parameters, the call to RevokeSecurityGroupEgress is successful but no security group rules are deleted.
     * 
You cannot specify SecurityGroupRuleId.N or the parameters that are not prefixed with Permissions.N.
     * 
You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.

     * 
Parameters used to determine an outbound security group rule that controls access to a CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestCidrIp. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
     * &SecurityGroupId=sg-bp67acfmxazb4ph***
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.DestCidrIp=10.0.0.0/8
     * &Permissions.1.PortRange=-22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
Parameters used to determine an outbound security group rule that controls access to another security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestGroupId. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
     * &SecurityGroupId=sg-bp67acfmxazb4ph***
     * &Permissions.1.DestGroupId=sg-bp67acfmxa123b****
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.PortRange=22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
Parameters used to determine an outbound security group rule that controls access to a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestPrefixListId. Sample request:
     * http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
     * &SecurityGroupId=sg-bp67acfmxazb4ph***
     * &Permissions.1.IpProtocol=TCP
     * &Permissions.1.DestPrefixListId=pl-x1j1k5ykzqlixdcy****
     * &Permissions.1.PortRange=-22/22
     * &Permissions.1.NicType=intranet
     * &Permissions.1.Policy=accept
     * &
     * 
     * 
     * 
     * 
     * 
     * 
     * @param request the request parameters of RevokeSecurityGroupEgress  RevokeSecurityGroupEgressRequest
     * @return RevokeSecurityGroupEgressResponse
     */
    CompletableFuture revokeSecurityGroupEgress(RevokeSecurityGroupEgressRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Unlike the CreateCommand and InvokeCommand operations, the RunCommand operation can be used to create and run a command in a single request.
     * Take note of the following items:
     * 

     * 
The instances on which you want to run a command must be in the Running (Running) state. You can call the DescribeInstances operation to query the status of instances.
     * 
Cloud Assistant Agent must be installed on the instances.
     * 
Before you run a PowerShell command on a Windows instance, make sure that the PowerShell module is installed on the instance.
     * 
When you use a cron expression to specify a schedule, you can specify a time zone based on your business requirements. If you do not specify a time zone, the schedule is determined by the system time of the instances. Make sure that the time or time zone of the instances meets your business requirements. For information about time zones, see Configure the NTP service for ECS instances that run CentOS 6 or Configure the NTP service for Windows instances.
     * 
You can set Timeout to specify the timeout period for executions of the command on ECS instances. If an execution times out, Cloud Assistant Agent forcefully terminates the command process.

     * 
When the one-time execution of the command times out, the execution state (InvokeRecordStatus) of the command becomes Failed.
     * 
For a scheduled task, the timeout period takes effect on each execution of the command. When a command execution times out, the subsequent executions of the command are not affected. When a scheduled execution of the command times out, the execution state (InvokeRecordStatus) of the command becomes Failed.
     * To ensure that scheduled tasks can run as expected, make sure that the version of Cloud Assistant Agent is not earlier than the following ones. A scheduled task can run a command at a specified interval, only once at a specified time, or at designated times based on a cron expression in a specified year or time zone. If the ClientNeedUpgrade error code is returned, you must update Cloud Assistant Agent to the latest version. For more information, see Upgrade or disable upgrades of Cloud Assistant Agent.

     * 
Linux: 2.2.3.282.
     * 
Windows: 2.1.3.282.
     * 
     * 
     * 
     * 
     * 
Command executions may fail due to instance status exceptions, network exceptions, or exceptions on Cloud Assistant Agent. If a command execution fails, no execution information is generated. For more information, see the Command errors and solutions section in the "Check execution results and troubleshoot common issues" topic.
     * 
If you set EnableParameter to true, the custom parameter feature is enabled. When you configure CommandContent, you can define custom parameters in the {{parameter}} format. Then, when the command is run, the key-value pairs of the custom parameters are passed in.
     * 
You can retain up to 500 to 50,000 Cloud Assistant commands in each region. You can also apply for a quota increase. For information about how to query and increase quotas, see Manage quotas.
     * 
Before you run a command on instances, especially new instances, we recommend that you call the DescribeCloudAssistantStatus operation to query the status of Cloud Assistant Agent on the instances and run the command when the value of CloudAssistantStatus in the response is true for the instances.
     * 
     * 
     * @param request the request parameters of RunCommand  RunCommandRequest
     * @return RunCommandResponse
     */
    CompletableFuture runCommand(RunCommandRequest request);

    /**
     * description :
     * 
Before you call this operation, familiarize yourself with the billing rules and pricing of ECS resources.*
     * This operation is an asynchronous operation. After a request to create ECS instances is sent, ECS instance IDs are returned but the creation and startup of the instances may be incomplete. You can call the DescribeInstanceStatus operation to query the status of the instances. When the status of an instance is Running in the DescribeInstanceStatus response, the instance is created and started.
     * 
Considerations
     * 

     * 
Make sure that the number of ECS instances you create or the number of vCPUs on ECS instances of all instance types you create does not exceed the corresponding quota. Go to the Quota Center to view the quotas.
     * 
Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, create a VPC in the region. For more information, see Create a VPC.
     * 
     * 
Precautions
     * 

     * 
You can call the RunInstances operation to create up to 100 ECS instances at a time. To create more than 100 ECS instances, we recommend that you initiate multiple requests in batches or concurrently.
     * 
If you set InternetMaxBandwidthOut to a value greater than 0, public IP addresses are automatically assigned to the ECS instances to be created.

     * 
 For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the Public bandwidth limits section of the "Limits" topic.
     * 
     * 
     * 
     * 
Suggestions
     * 

     * 
Test scenarios: Set DryRun to true to perform a dry run without performing the actual request.
     * 
Release of ECS instances: Use AutoReleaseTime to configure an automatic release time for ECS instances in the request to RunInstances or call the DeleteInstances operation to release the instances.
     * 
Management and search of ECS instances: Add tags to the ECS instances by specifying Tag.N.Key and Tag.N.Value and append incremental suffixes by specifying UniqueSuffix to the hostname specified by HostName and the instance name specified by InstanceName. For more information, see Batch configure sequential names or hostnames for multiple instances.
     * 
Launch template: A launch template contains the parameters required to create an ECS instance so that you do not have to specify the parameters every time you create ECS instances. You can call the CreateLaunchTemplate operation to create a launch template. Then, in the request to RunInstances, you can specify LaunchTemplateId and LaunchTemplateVersion to use the launch template.
     * 
Disabling of Hyper-Threading (HT): In memory-intensive scenarios, set CpuOptions.ThreadsPerCore to 1 to disable HT and increase the memory-to-vCPU ratio.
     * 
Enabling of Jumbo Frames: Set NetworkOptions.EnableJumboFrame to true to enable the Jumbo Frames feature when you create ECS instances. For more information, see MTUs.
     * 
     * 
Sample requests
     * 
Use a specific image to create ECS instances of a specific instance type in the China (Hangzhou) region. The instances use disks with a specific capacity as the system disk and data disks and are automatically assigned public IP addresses. The instances have user-defined names and logon passwords. The instances are assigned to a specific security group and connected to a specific vSwitch. Request parameters:
     *     RegionId: Set the region ID to cn-hangzhou, which indicates the China (Hangzhou) region.
     *     ImageId: Set the image ID to aliyun_3_x64_20G_alibase_20221102.vhd.
     *     InstanceType: Set the instance type to ecs.g7.large.SecurityGroupId: Set the security group ID to sg-bp150uqocpf9jj70****.
     *     VSwitchId: Set the vSwitch ID to vsw-bp1qo7s91cbch5i4l****.
     *     SystemDisk.Category: Set the system disk category to cloud_essd, which specifies the Enterprise SSD (ESSD) category.
     *     SystemDisk.Size: Set the system disk size to 40. Unit: GiB.
     *     DataDisk.Category: Set the data disk category to cloud_essd, which specifies the ESSD category.
     *     DataDisk.Size: Set the data disk size to 100. Unit: GiB.
     *     HostName: Set the instance hostname to ECS-test.
     *     Password: Set the logon password to ECS@test1234.
     *     InternetMaxBandwidthOut: Set the outbound public bandwidth to 10. Unit: Mbit/s.
     * Examples on how to create instances of different types based on the preceding parameters:
     * Example: Create five subscription ECS instances for which auto-renewal is enabled
     *     Amount: Set the number of ECS instances that you want to create to 5.
     *     InstanceChargeType: Set the billing method to PrePaid, which specifies the subscription billing method.
     *     PeriodUnit: Set the period unit to Month.
     *     Period: Set the subscription period to 1. The unit is specified by PeriodUnit, which is Month in this example.
     *     AutoRenew: Set this parameter to true to enable auto-renewal.
     *     AutoRenewPeriod: Set the renewal period to 1. The unit is specified by PeriodUnit, which is Month in this example.
     * Example: Create 10 pay-as-you-go ECS instances
     *     Amount: Set the number of ECS instances that you want to create to 10.
     *     InstanceChargeType: Set the billing method to PostPaid, which specifies the pay-as-you-go billing method.
     *     SpotStrategy: Set this parameter to NoSpot, which is the default value and specifies that the instances are created as pay-as-you-go instances.
     * Example: Create 20 preemptible instances that have a specified bidding policy and a protection period
     *     Amount: Set the number of ECS instances that you want to create to 20.
     *     InstanceChargeType: Set the billing method to PostPaid, which specifies the pay-as-you-go billing method.
     *     SpotStrategy: Set the bidding policy to SpotAsPriceGo, which specifies that the instances are created as preemptible instances for which the market price at the time of purchase is automatically used as the bid price.
     *     SpotDuration: Set the protection period of the preemptible instances to 1. Unit: hours.
     * Call the CreateLaunchTemplate operation to create a launch template. Then, use the launch template to create ECS instances in the China (Hangzhou) region. Sample request:
     * Example: Create 10 ECS instances based on a launch template
     *     RegionId: Set RegionId to cn-hangzhou, which indicates the China (Hangzhou) region.
     *     Amount: Set the number of ECS instances that you want to create to 10.
     *     LaunchTemplateId: Set the launch template ID to lt-bp14xczpoxvb6rre****.
     * 

     * 
 If a parameter is specified both in the launch template that you reference in a request and in the instance parameters of the same request, the value specified in the instance parameters takes precedence. For example, if you set InstanceChargeType in the launch template to PrePaid (subscription) and set InstanceChargeType in the instance parameters to PostPaid (pay-as-you-go), the created instances are pay-as-you-go instances.
     * 
     * 
     * @param request the request parameters of RunInstances  RunInstancesRequest
     * @return RunInstancesResponse
     */
    CompletableFuture runInstances(RunInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The instances to which you want to send a file must be in the Running (Running) state.
     * 
Cloud Assistant Agent must be installed on the instances.
     * 
Only Cloud Assistant Agent versions that are later than the following ones support file sending. If the ClientNeedUpgrade error code is returned, update Cloud Assistant Agent to the latest version.

     * 
For Linux instances, the version of Cloud Assistant Agent must be later than 1.0.2.569.
     * 
For Windows instances, the version of Cloud Assistant Agent must be later than 1.0.0.149.
     * 
     * 
     * 
The file to be sent must not exceed 32 KB in size after it is encoded in Base64.
     * 
The file may fail to be sent due to instance exceptions, network exceptions, or exceptions on Cloud Assistant Agent. If the file fails to be sent, call the DescribeSendFileResults operation or see Check execution results and troubleshoot common issues for troubleshooting.
     * 
     * 
     * @param request the request parameters of SendFile  SendFileRequest
     * @return SendFileResponse
     */
    CompletableFuture sendFile(SendFileRequest request);

    /**
     * description :
     * 
  After you create an image template, you can call the StartImagePipelineExecution operation to create a pipeline task. The system creates, copies, and shares images based on the parameters configured in the image template.
     * 

     * 
You can execute only one pipeline task for each image template.
     * 
     * 
     * @param request the request parameters of StartImagePipelineExecution  StartImagePipelineExecutionRequest
     * @return StartImagePipelineExecutionResponse
     */
    CompletableFuture startImagePipelineExecution(StartImagePipelineExecutionRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to start an ECS instance, the operation sets the status of the ECS instance to Starting and begins the startup process. You can call the DescribeInstanceStatus operation to query the status of the ECS instance. When the status of the ECS instance changes to Running, the instance is started.
     * 
Precautions
     * 

     * 
You cannot call this operation to start an ECS instance that is locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
The ECS instance that you want to start must be in the Stopped (Stopped) state.
     * 
If an ECS instance is stopped in economical mode, the instance may fail to be started due to insufficient resources.
     * 
     * 
     * @param request the request parameters of StartInstance  StartInstanceRequest
     * @return StartInstanceResponse
     */
    CompletableFuture startInstance(StartInstanceRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to start ECS instances, the operation sets the status of the ECS instances to Starting and begins the startup process. You can call the DescribeInstanceStatus operation to query the status of the instances. When the status of the ECS instances changes to Running, the instances are started.
     * 
Precautions
     * 

     * 
You cannot call this operation to start ECS instances that are locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
The ECS instances that you want to start must be in the Stopped (Stopped) state.
     * 
ECS instances stopped in economical mode may fail to be started due to insufficient resources.
     * 
     * 
     * @param request the request parameters of StartInstances  StartInstancesRequest
     * @return StartInstancesResponse
     */
    CompletableFuture startInstances(StartInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 
When you use custom code to connect to an ECS instance that serves as a client, you can call this operation to obtain the WebSocket URL that is used to connect to the instance. Take note of the following items:
     * 

     * 
The ECS instance must be in the Running state.
     * 
Cloud Assistant Agent must be installed on the ECS instance. You can call the DescribeCloudAssistantStatus operation to check whether Cloud Assistant Agent is installed on the ECS instance and query the version number of the installed Cloud Assistant Agent.

     * 
If Cloud Assistant Agent is not installed on the ECS instance, call the InstallCloudAssistant operation to install Cloud Assistant Agent.
     * 
The Cloud Assistant Agent versions that are later than the following ones support the session management feature. If you need to upgrade the Cloud Assistant Agent version, follow the instructions in Upgrade or disable upgrades for Cloud Assistant Agent.

     * 
Linux operating system: 2.2.3.256
     * 
Windows operating system: 2.1.3.256
     * 
     * 
     * 
     * 
     * 
Each WebSocket URL returned by the StartTerminalSession operation remains valid for 10 minutes.
     * 
Up to 1,000 sessions can be created and available in a region. Each ECS instance can have up to 20 sessions in the connected state.
     * 
     * 
     * @param request the request parameters of StartTerminalSession  StartTerminalSessionRequest
     * @return StartTerminalSessionResponse
     */
    CompletableFuture startTerminalSession(StartTerminalSessionRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to stop an ECS instance, the operation sets the status of the ECS instance to Stopping and begins the stop process. You can call the DescribeInstanceStatus operation to query the status of the ECS instance. When the status of the ECS instance changes to Stopped, the instance is stopped.
     * 
Precautions
     * 

     * 
You cannot call this operation to stop an ECS instance that is locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
After you enable the default economical mode for all pay-as-you-go ECS instances located in virtual private clouds (VPCs) in your account, you can set StoppedMode to KeepCharging for the ECS instance that you want to stop to enable standard mode. This way, the ECS instance continues to be billed after the instance is stopped. The instance type resources and public IP address of the instance are retained.
     * 
     * 
     * @param request the request parameters of StopInstance  StopInstanceRequest
     * @return StopInstanceResponse
     */
    CompletableFuture stopInstance(StopInstanceRequest request);

    /**
     * description :
     * 
This operation is an asynchronous operation. After you call this operation to stop ECS instances, the operation sets the status of the ECS instances to Stopping and begins the stop process. You can call the DescribeInstanceStatus operation to query the status of the ECS instances. When the status of the ECS instances changes to Stopped, the instances are stopped.
     * 
Precautions
     * 

     * 
You cannot call this operation to stop ECS instances that are locked for security reasons. For more information, see API behavior when an instance is locked for security reasons.
     * 
After you enable the default economical mode for all pay-as-you-go ECS instances located in virtual private clouds (VPCs) in your account, you can set StoppedMode to KeepCharging for the pay-as-you-go ECS instances that you want to stop to enable standard mode. This way, the instances continue to be billed after they are stopped. The instance type resources and public IP addresses of the instances are retained.
     * 
     * 
     * @param request the request parameters of StopInstances  StopInstancesRequest
     * @return StopInstancesResponse
     */
    CompletableFuture stopInstances(StopInstancesRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
If you stop the process of a command that runs only once, the executions that have started are not interrupted. The executions that have not started are canceled.
     * 
If you stop the process of a command that runs on a schedule, the executions that have started are not interrupted. Subsequent executions are not scheduled.
     * 
     * 
     * @param request the request parameters of StopInvocation  StopInvocationRequest
     * @return StopInvocationResponse
     */
    CompletableFuture stopInvocation(StopInvocationRequest request);

    /**
     * description :
     * 
Before you add tags to a resource, Alibaba Cloud checks the number of existing tags of the resource. If the maximum number of tags is reached, an error message is returned. For more information, see the "Tag limits" section in Limits.
     * 
     * @param request the request parameters of TagResources  TagResourcesRequest
     * @return TagResourcesResponse
     */
    CompletableFuture tagResources(TagResourcesRequest request);

    /**
     * @deprecated OpenAPI TerminatePhysicalConnection is deprecated  * @param request  the request parameters of TerminatePhysicalConnection  TerminatePhysicalConnectionRequest
     * @return TerminatePhysicalConnectionResponse
     */
    @Deprecated
    CompletableFuture terminatePhysicalConnection(TerminatePhysicalConnectionRequest request);

    /**
     * @deprecated OpenAPI TerminateVirtualBorderRouter is deprecated  * @param request  the request parameters of TerminateVirtualBorderRouter  TerminateVirtualBorderRouterRequest
     * @return TerminateVirtualBorderRouterResponse
     */
    @Deprecated
    CompletableFuture terminateVirtualBorderRouter(TerminateVirtualBorderRouterRequest request);

    /**
     * description :
     * 
Usage notes
     * 
Take note of the following items:
     * 

     * 
The ENI must be in the Available (Available) or InUse (InUse) state.
     * 
If the ENI is a primary ENI, the Elastic Compute Service (ECS) instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
     * 
     * 
     * @param request the request parameters of UnassignIpv6Addresses  UnassignIpv6AddressesRequest
     * @return UnassignIpv6AddressesResponse
     */
    CompletableFuture unassignIpv6Addresses(UnassignIpv6AddressesRequest request);

    /**
     * description :
     * 
Usage notes
     * 

     * 
The ENI from which to unassign secondary private IP addresses must be in the Available (Available) or InUse (InUse) state.
     * 
If the ENI is a primary ENI, the Elastic Compute Service (ECS) instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
     * 
     * 
     * @param request the request parameters of UnassignPrivateIpAddresses  UnassignPrivateIpAddressesRequest
     * @return UnassignPrivateIpAddressesResponse
     */
    CompletableFuture unassignPrivateIpAddresses(UnassignPrivateIpAddressesRequest request);

    /**
     * @deprecated OpenAPI UnassociateEipAddress is deprecated  * @param request  the request parameters of UnassociateEipAddress  UnassociateEipAddressRequest
     * @return UnassociateEipAddressResponse
     */
    @Deprecated
    CompletableFuture unassociateEipAddress(UnassociateEipAddressRequest request);

    /**
     * @deprecated OpenAPI UnassociateHaVip is deprecated  * @param request  the request parameters of UnassociateHaVip  UnassociateHaVipRequest
     * @return UnassociateHaVipResponse
     */
    @Deprecated
    CompletableFuture unassociateHaVip(UnassociateHaVipRequest request);

    /**
     * @param request the request parameters of UntagResources  UntagResourcesRequest
     * @return UntagResourcesResponse
     */
    CompletableFuture untagResources(UntagResourcesRequest request);

}