Modifying Route Tables Associated with a VPC Endpoint
Function
This API is used to modify route tables associated with a VPC endpoint.
Calling Method
For details, see Calling APIs.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
 - If you are using identity policy-based authorization, the following identity policy-based permissions are required. 
     
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
vpcep:endpoints:updateRouteTables
Write
endpoints *
g:ResourceTag/<tag-key>
- vpcep:endpoints:update
 
-
routeTable *
-
 
URI
PUT /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}/routetables
| 
         Parameter  | 
       
         Mandatory  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|---|
| 
         project_id  | 
       
         Yes  | 
       
         String  | 
       
         Project ID  | 
      
| 
         vpc_endpoint_id  | 
       
         Yes  | 
       
         String  | 
       
         Specifies the ID of the VPC endpoint.  | 
      
Request Parameters
| 
         Parameter  | 
       
         Mandatory  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|---|
| 
         X-Auth-Token  | 
       
         Yes  | 
       
         String  | 
       
         Specifies the user token. It can be obtained by calling the IAM API. The value of X-Subject-Token in the response header is the user token.  | 
      
| 
         Content-Type  | 
       
         No  | 
       
         String  | 
       
         Specifies the MIME type of the request body. Default value application/json is recommended. For APIs used to upload objects or images, the MIME type varies depending on the flow type.  | 
      
| 
         Parameter  | 
       
         Mandatory  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|---|
| 
         routetables  | 
       
         Yes  | 
       
         Array of strings  | 
       
         Lists the IDs of route tables.  | 
      
Response Parameters
Status code: 200
| 
         Parameter  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|
| 
         routetables  | 
       
         Array of strings  | 
       
         Specifies the IDs of route tables. If this parameter is not specified, the ID of the route table of the default VPC is returned. This parameter is available when you update VPC endpoints for connecting to gateway VPC endpoint services.  | 
      
| 
         error  | 
       
         Array of RoutetableInfoError objects  | 
       
         Specifies the error message returned when the route table of the VPC endpoint subnet fails to be modified.  | 
      
| 
         Parameter  | 
       
         Type  | 
       
         Description  | 
      
|---|---|---|
| 
         bind_failed  | 
       
         Array of RoutetableInfoErrorDetial objects  | 
       
         Failed to bind the route table to the VPC endpoint subnet.  | 
      
| 
         unbind_failed  | 
       
         Array of RoutetableInfoErrorDetial objects  | 
       
         Failed to unbind the route table from the VPC endpoint subnet.  | 
      
Example Requests
Modifying route tables associated with a VPC endpoint
PUT https://{endpoint}/v1/{project_id}/vpc-endpoints/4189d3c2-8882-4871-a3c2- d380272eed83/routetables
{
  "routetables" : [ "705290f3-0d00-41f2-aedc-71f09844e879" ]
}
  Example Responses
Status code: 200
The server has successfully processed the request.
{
  "routetables" : [ "705290f3-0d00-41f2-aedc-71f09844e879" ]
}
  Status Codes
| 
         Status Code  | 
       
         Description  | 
      
|---|---|
| 
         200  | 
       
         The server has successfully processed the request.  | 
      
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.