All Products
Document Center

Virtual Private Cloud:RetryVpcPrefixListAssociation

Last Updated:Dec 01, 2023

Re-applies a prefix list.

Operation Description

  • If you modify the information about a prefix list but the modification is not automatically applied to the route table that is associated with the prefix list, you can call this operation to apply the latest prefix list to the associated route table.

  • The RetryVpcPrefixListAssociation operation is asynchronous. After you send the request, the system returns a request ID. However, the operation is still being performed in the background. You can call the GetVpcPrefixListAssociations to check whether the prefix list is re-applied.

    • If the prefix list is in the Modifying state, the prefix list is being re-applied.
    • If the prefix list is in the ModifyFailed state, the prefix list fails to be re-applied.
    • If the prefix list is in the Created state, the prefix list is re-applied.
  • After you call the RetryVpcPrefixListAssociation operation to re-apply a prefix list, you cannot call the operation again until the current task is complete.


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
  • PrefixList

Request parameters


The ID of the prefix list that you want to re-apply.


The type of the resource with which the prefix list is associated. Valid values:

  • vpcRouteTable: VPC route table
  • trRouteTable: route table of a transit router

The ID of the associated resource.


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

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

Note If you do not set this parameter, the system automatically uses RequestId as ClientToken. RequestId may be different for each API request.

Specifies whether to only precheck the request. Valid values:

  • true: prechecks the request without associating the prefix list. The system prechecks the required parameters, request syntax, and limits. If the request fails the precheck, an error message is returned. If the request passes the precheck, the DryRunOperation error code is returned.
  • false: sends the request. If the request passes the precheck, a 2xx HTTP status code is returned and the prefix list is associated. This is the default value.

The region ID of the prefix list that you want to re-apply.

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


Response parameters


The ID of the request.



Sample success responses


  "RequestId": "4EC47282-1B74-4534-BD0E-403F3EE64CAF"

Error codes

HTTP status codeError codeError messageDescription
400UnsupportedRegionThe feature of prefixList entry is not supported in this region.-
400OperationDenied.SystemPrefixListThe operation is not allowed because of SystemPrefixList.You cannot manage the system prefix list.
400OperationFailed.OperateShareResourceThis is not allowed to operate shared prefixList.-
400IncorrectStatus.PrefixListThe status of prefixList is incorrect.The prefix list is in an unstable state.
400OperationFailed.NotExistAssociateRelationThe operation is failed because of association not exist.-
400ResourceNotFound.PrefixListThe specified resource of prefixList is not found.The prefix list does not exist.

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

Change history

Change timeSummary of changesOperation
2023-09-21The error codes of the API operation change.see changesets
Change itemChange content
Error CodesThe error codes of the API operation change.
    Error Codes 400 change
2023-08-30API Description Update,The API operation is not deprecated.,The error codes of the API operation change.see changesets
Change itemChange content
API DescriptionAPI Description Update
API Deprecation DescriptionThe API operation is not deprecated.
Error CodesThe error codes of the API operation change.
    delete Error Codes: 400