POST /#Action=CreateRoute
Creates a route in a route table within a VPC.
You must specify either a destination CIDR block or a prefix list ID. You must also specify exactly one of the resources from the parameter list.
When determining how to route traffic, we use the route with the most specific match. For example, traffic is destined for the IPv4 address 192.0.2.3, and the route table includes the following two IPv4 routes:
-
192.0.2.0/24(goes to some target A) -
192.0.2.0/28(goes to some target B)
Both routes apply to the traffic destined for 192.0.2.3. However, the second route in the list covers a smaller number of IP addresses and is therefore more specific, so we use that route to determine where to target the traffic.
For more information about route tables, see Route tables in the Amazon Virtual Private Cloud User Guide.
Servers
- https://ec2.{region}.amazonaws.com
- https://ec2.amazonaws.com
- https://ec2.{region}.amazonaws.com.cn
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
X-Amz-Content-Sha256 |
String | No | |
X-Amz-Credential |
String | No | |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "text/xml" |
X-Amz-Date |
String | No | |
X-Amz-Algorithm |
String | No | |
X-Amz-SignedHeaders |
String | No | |
X-Amz-Security-Token |
String | No | |
X-Amz-Signature |
String | No |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
Version |
String | Yes |
Possible values:
|
Action |
String | Yes |
Possible values:
|
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
DestinationCidrBlock |
String | No |
The IPv4 CIDR address block used for the destination match. Routing decisions are based on the most specific match. We modify the specified CIDR block to its canonical form; for example, if you specify |
CoreNetworkArn |
String | No |
The Amazon Resource Name (ARN) of the core network. |
GatewayId |
String | No |
The ID of an internet gateway or virtual private gateway attached to your VPC. |
VpcPeeringConnectionId |
String | No |
The ID of a VPC peering connection. |
DestinationPrefixListId |
String | No |
The ID of a prefix list used for the destination match. |
InstanceId |
String | No |
The ID of a NAT instance in your VPC. The operation fails if you specify an instance ID unless exactly one network interface is attached. |
NatGatewayId |
String | No |
[IPv4 traffic only] The ID of a NAT gateway. |
CarrierGatewayId |
String | No |
The ID of the carrier gateway. You can only use this option when the VPC contains a subnet which is associated with a Wavelength Zone. |
NetworkInterfaceId |
String | No |
The ID of a network interface. |
RouteTableId |
String | Yes |
The ID of the route table for the route. |
EgressOnlyInternetGatewayId |
String | No |
[IPv6 traffic only] The ID of an egress-only internet gateway. |
VpcEndpointId |
String | No |
The ID of a VPC endpoint. Supported for Gateway Load Balancer endpoints only. |
LocalGatewayId |
String | No |
The ID of the local gateway. |
DestinationIpv6CidrBlock |
String | No |
The IPv6 CIDR block used for the destination match. Routing decisions are based on the most specific match. |
DryRun |
Boolean | No |
Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is |
TransitGatewayId |
String | No |
The ID of a transit gateway. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.