Re-applies a prefix list.

Usage notes

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

Scenarios

A prefix list can be successfully modified if the following requirements are met: CIDR blocks are valid, CIDR blocks do not conflict, and the number of CIDR blocks does not exceed the maximum number of CIDR blocks supported by the prefix list. If issues occur on the resource that references the prefix list, the reference may fail. The issues include the number of prefix list entries exceeding the quota or CIDR blocks conflicting with existing routes. After you resolve the issues, you can call the RetryVpcPrefixListAssociation operation to re-apply the prefix list.

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.

Request parameters

Parameter Type Required Example Description
Action String Yes RetryVpcPrefixListAssociation

The operation that you want to perform. Set the value to RetryVpcPrefixListAssociation.

PrefixListId String Yes pl-0b7hwu67****

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

ResourceType String Yes vpcRouteTable

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
ResourceId String Yes vtb-bp1drpcfz9srr393h****

The ID of the associated resource.

ClientToken String No 123e4567-e89b-12d3-a456-426655440000

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.
DryRun Boolean No false

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.
RegionId String Yes cn-hangzhou

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

Parameter Type Example Description
RequestId String 4EC47282-1B74-4534-BD0E-403F3EE64CAF

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=RetryVpcPrefixListAssociation
&PrefixListId=pl-0b7hwu67****
&ResourceType=vpcRouteTable
&ResourceId=vtb-bp1drpcfz9srr393h****
&ClientToken=123e4567-e89b-12d3-a456-426655440000
&DryRun=false
&RegionId=cn-hangzhou
&Common request parameters

Sample success responses

XML format 

HTTP/1.1 200 OK
Content-Type:application/xml

<RetryVpcPrefixListAssociationResponse>
    <RequestId>4EC47282-1B74-4534-BD0E-403F3EE64CAF</RequestId>
</RetryVpcPrefixListAssociationResponse>

JSON format 

HTTP/1.1 200 OK
Content-Type:application/json

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

Error codes

HTTP status code Error code Error message Description
400 UnsupportedRegion The feature of prefixList entry is not supported in this region. The error message returned because you cannot manage the prefix list in the current region.
400 OperationDenied.SystemPrefixList The operation is not allowed because of SystemPrefixList. The error message returned because you cannot manage the system prefix list.
400 OperationFailed.OperateShareResource This is not allowed to operate shared prefixList. The error message returned because you cannot manage a shared prefix list.
400 IncorrectStatus.PrefixList The status of prefixList is incorrect. The error message returned because the prefix list is in an unstable state.
400 OperationFailed.NotExistAssociateRelation The operation is failed because of association not exist. The error message returned because the association of the prefix list does not exist.

For a list of error codes, visit the API Error Center.