Create a NAT Gateway.
Note the following before creating a NAT Gateway:
A NAT Gateway and a self-built SNAT Gateway cannot coexist in a VPC.
If a route entry of which the destination CIDR block is 0.0.0.0/0 already exists in the route table of the VPC, delete the router entry.
After a NAT Gateway is created, a route entry of which the destination CIDR block is 0.0.0.0/0 and the next hop is the NAT Gateway is automatically added to the route table of the VPC. Therefore, traffic can be routed to the NAT Gateway.
The NAT Gateway has different specifications. Different specifications correspond to different SNAT performance metrics including Max Connection and CPS, but the specification does not affect data throughput.
The following table lists available NAT Gateway specifications:
The action to perform.
The region of the NAT Gateway.
You can obtain the region ID by calling the DescribeRegions API.
|VpcId||String||Yes||The ID of the VPC to which the NAT Gateway belongs.|
The specification of the NAT Gateway. Valid value:
The name of the NAT Gateway.
The name must start with an English letter, but cannot start with
The name can contain from 2 to 128 characters including a-z, A-Z, 0-9, underlines, and hyphens./td>
The description of the NAT Gateway.
The description must start with English letters, but cannot start with
The description can contain from 2 to 256 characters.
A client token used to guarantee the idempotence of requests. This parameter value is generated by the client and must be unique. It cannot exceed 64 ASCII characters.
For more information, see How to ensure idempotence.
|RequestId||String||The ID of the request.|
The ID of the NAT Gateway.
|ForwardTableIds||Array||The list of forwarding entries.|
See VPC API Error Center.