All Products
Search
Document Center

NAT Gateway:Use OpenAPI

Last Updated:Mar 26, 2024

For more information about how to call the API operations of Alibaba Cloud, see Use OpenAPI. This topic describes how to use OpenAPI to call NAT Gateway operations, including the descriptions of versions, endpoints, styles, and call methods.

Note

NAT Gateway and Virtual Private Cloud (VPC) use the same endpoint.

Versions

API version

Description

2016-04-28

We recommend that you use this version.

Endpoints

The NAT Gateway API supports multiple access points. For more information, see Endpoints.

Identities

Identity

Supported

Alibaba Cloud account

Yes

RAM user (recommended)

Yes

RAM role (recommended)

Yes

API style

The API operations of NAT Gateway are called in the remote procedure call (RPC) style. For more information, see API styles.

Call methods

Method

Supported

References

(Recommended) Alibaba Cloud SDK

Yes

  • For more information about the supported languages and dependencies of NAT Gateway SDKs, see VPC SDKs.

  • For more information about how to integrate Alibaba Cloud SDKs, see Alibaba Cloud SDKs.

Alibaba Cloud CLI

Yes

For more information about how to use Alibaba Cloud CLI to call NAT Gateway API operations, see Alibaba Cloud CLI.

Cloud Shell

Yes

For more information about Cloud Shell, see Cloud Shell.

Terraform

Yes

For more information about how to use Terraform to call NAT Gateway API operations, see Terraform.

Resource Orchestration Service (ROS)

Yes

For more information about how to use ROS to call NAT Gateway API operations, see ROS.

Custom HTTP encapsulation

Yes

You can encapsulate API requests based on your business requirements. For more information, see Custom encapsulation.