All Products
Document Center

Virtual Private Cloud:EnableVpcClassicLink

Last Updated:Dec 06, 2023

Enables ClassicLink for a VPC.


You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.


Authorization information

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

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

Request parameters


The region ID of the VPC for which you want to enable ClassicLink.

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


The ID of the VPC.


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

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

Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.

Response parameters


The request ID.


The request ID.



Sample success responses


  "RequestId": "54B48E3D-DF70-471B-AA93-08E683A1B45"

Error codes

HTTP status codeError codeError messageDescription
400IncorrectVpcStatusCurrent VPC status does not support this operation.This operation cannot be performed when the VPC is in the current state.
400Forbidden.EnableClassicLinkthe specified resource does not support this operation.-
400RouteConflict.AlreadyExistRoute conflict exists in routing table.Route conflicts exist in the route table.
404InvalidRegionId.NotFoundSpecified value of "regionId" is not supported.RegionId is set to an invalid value. Check whether the service is available in the specified region and try again.
404InvalidVpcId.NotFoundSpecified VPC does not exist.The specified VPC does not exist.
404OperationFailed.RouteConflictOperation failed because a specified route entry is already exist.The operation conflicts with an existing route.

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

Change history

Change timeSummary of changesOperation
2023-08-15The error codes of the API operation change.see changesets
Change itemChange content
Error CodesThe error codes of the API operation change.
    Error Codes 404 change
    delete Error Codes: 400