This topic describes the basic information about Cloud Config API. For more information about how to call Alibaba Cloud API operations, see Overview.
Version
Version | Description |
We recommend that you use this version. |
Endpoints
Cloud Config endpoints depend on whether you are using the China site or international site, rather than the region. The following table describes the Cloud Config endpoints in different sites.
Site | Region | Region ID | Public endpoint | VPC endpoint |
China site (aliyun.com) | China (Shanghai) | cn-shanghai | config.cn-shanghai.aliyuncs.com | config-vpc.cn-shanghai.aliyuncs.com |
International site (alibabacloud.com) | Singapore | ap-southeast-1 | config.ap-southeast-1.aliyuncs.com | config-vpc.ap-southeast-1.aliyuncs.com |
User identities
User identity | Supported |
Yes | |
RAM user (recommended) | Yes |
RAM role (recommended) | Yes |
We recommend that you call API operations as a Resource Access Management (RAM) user or by using a RAM role. Before you call API operations, you must grant permissions to the RAM user or RAM role based on your business requirements.
API style
The remote procedure call (RPC) style is used.
Call methods
Call method | Supported | Reference |
Alibaba Cloud SDKs | Yes | For information about the languages supported by Cloud Config SDKs and how to install their dependencies, see Cloud Config SDKs. Note For more information about how to use Alibaba Cloud SDKs to call Cloud Config API operations, see Alibaba Cloud SDKs. |
Alibaba Cloud CLI | Yes | For information about how to use Alibaba Cloud CLI to call Cloud Config API operations, see Alibaba Cloud CLI. |
Resource Orchestration Service (ROS) | No | For information about how to use ROS to call Cloud Config API operations, see ROS. |
Terraform | Yes | For information about how to use Terraform to call Cloud Config API operations, see Terraform. |
If none of the preceding solutions meets your business requirements, you can encapsulate your API requests. For more information, see Custom encapsulation.