To send a Cloud Firewall API request, you must send an HTTP GET request to the Cloud Firewall endpoint. You must add the request parameters that correspond to the API operation being called. After you call the API operation, the system returns a response. The request and response are encoded in UTF-8.
Request structure
Cloud Firewall API operations use the RPC protocol. You can call Cloud Firewall API operations by sending HTTP GET requests.
The request syntax is as follows:
https://Endpoint/?Action=xx&Parameters- Endpoint: the endpoint of the Cloud Firewall API is cloudfw.cn-hangzhou.aliyuncs.com.
- Action: the name of the operation being performed. For example, to add an access control policy, you must set the Action parameter to AddControlPolicy.
- Version: The version number of the API. The current version of the Cloud Firewall API is 2017-12-07.
- Parameters: the request parameters for the operation. Separate multiple parameters with ampersands (&).
Request parameters include both common parameters and operation-specific parameters. Common request parameters include the API version number and authentication information. For more information about common request parameters, see Common parameters.
http(s)://cloudfw.cn-hangzhou.aliyuncs.com/?Action=AddControlPolicy
&Format=xml
&Version=2017-12-07
&Signature=xxxx%xxxx%3D
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId=key-test
&TimeStamp=2012-06-01T12:00:00Z
...Request signatures
You must sign all API requests to ensure security. Cloud Firewall uses the request signature to verify the identity of the API caller.
Cloud Firewall implements symmetric encryption with an AccessKey pair to verify the identity of the request sender. An AccessKey pair is an identity credential issued to Alibaba Cloud accounts and RAM users that is similar to a logon username and password. An AccessKey pair consists of an AccessKey ID and an AccessKey secret. The AccessKey ID is used to verify the identity of the user, while the AccessKey secret is used to encrypt and verify the signature string. You must keep your AccessKey secret strictly confidential.
https://endpoint/?SignatureVersion=1.0&SignatureMethod=HMAC-SHA1&Signature=CT9X0VtwR86fNWSnsc6v8YGOjuE%3D&SignatureNonce=3ee8c1b8-83d3-44af-a94f-4e0ad82fd6cftestid and the AccessKey secret is
testsecret, the following code shows the request URL before the request is signed:
https://cloudfw.cn-hangzhou.aliyuncs.com/?Action=AddControlPolicy
&TimeStamp=2016-02-23T12:46:24Z
&Format=XML
&AccessKeyId=testid
&SignatureMethod=HMAC-SHA1
&SignatureNonce=3ee8c1b8-83d3-44af-a94f-4e0ad82fd6cf
&Version=2017-12-07
&SignatureVersion=1.0- Use the request parameters to create a string-to-sign.
GET&%2F&AccessKeyId%3Dtestid&Action%3DAddControlPolicy&Format%3DXML&SignatureMethod%3DHMAC-SHA1&SignatureNonce%3D3ee8c1b8-83d3-44af-a94f-4e0ad82fd6cf&SignatureVersion%3D1.0&TimeStamp%3D2016-02-23T12%253A46%253A24Z&Version%3D2018-12-03 - Calculate the HMAC value of the string-to-sign.
Append an ampersand (&) to the end of the AccessKey secret as the key to calculate the HMAC value. In this example, the key is
testsecret&.CT9X0VtwR86fNWSnsc6v8YGOjuE= - Add the signature string to the request as the Signature parameter.
https://cloudfw.cn-hangzhou.aliyuncs.com/?Action=AddControlPolicy &TimeStamp=2016-02-23T12:46:24Z &Format=XML &AccessKeyId=testid &SignatureMethod=HMAC-SHA1 &SignatureNonce=3ee8c1b8-83d3-44af-a94f-4e0ad82fd6cf &Version=2017-12-07 &SignatureVersion=1.0 &Signature=CT9X0VtwR86fNWSnsc6v8YGOjuE%3D