This topic describes the endpoints, communication protocols, HTTP request methods, and request parameters of KMS API.


The following table lists the endpoints of the KMS API.

Region RegionId Public endpoint VPC endpoint
Japan (Tokyo) ap-northeast-1
Singapore ap-southeast-1
Australia (Sydney) ap-southeast-2
Malaysia (Kuala Lumpur) ap-southeast-3
Indonesia (Jakarta) ap-southeast-5
India (Mumbai) ap-south-1
China (Hangzhou) cn-hangzhou
China (Shanghai) cn-shanghai
China (Qingdao) cn-qingdao
China (Beijing) cn-beijing
China (Zhangjiakou-Beijing Winter Olympic) cn-zhangjiakou
China (Hohhot) cn-huhehaote
China (Shenzhen) cn-shenzhen
Germany (Frankfurt) eu-central-1
UAE (Dubai) me-east-1
China (Hong Kong) cn-hongkong
US (Virginia) us-east-1
US (Silicon Valley) us-west-1
China East 1 Finance cn-hangzhou-finance N/A
China East 2 Finance cn-shanghai-finance-1
China South 1 Finance cn-shenzhen-finance-1
UK (London) eu-west-1
China (Heyuan) cn-heyuan
China (Ulanqab) cn-wulanchabu


You must call KMS API operations by sending HTTPS requests.

KMS supports only TLS1.0 and later.


You can use the HTTP POST and GET methods to send requests. If you use these methods, the request parameters must be included in the request URL.


Each request must specify the operation to be performed. For example, to create a CMK, you must set the Action parameter to CreateKey. Request parameters include both common parameters and operation-specific parameters.

For more information, see Common parameters.


Requests and responses are encoded using UTF-8.