Creates a custom domain name.
Operation description
If you want to use a fixed domain name to access an application or function in a production environment of Function Compute, or to resolve the issue of forced downloads when accessing an HTTP trigger, you can bind a custom domain name to the application or function.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| fc:CreateCustomDomain | create | *All Resources * |
| none |
Request syntax
POST /2023-03-30/custom-domains HTTP/1.1
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| body | CreateCustomDomainInput | Yes | The information about the custom domain name. |
Response parameters
Examples
Sample success responses
JSONformat
{
"accountId": "",
"apiVersion": "2023-03-30",
"authConfig": {
"authInfo": "{}",
"authType": "anonymous, function, jwt"
},
"certConfig": {
"certName": "my-cert",
"certificate": "PEM format",
"privateKey": "PEM format"
},
"createdTime": "2023-03-30T08:02:19Z",
"domainName": "example.com",
"lastModifiedTime": "2023-03-30T08:02:19Z",
"protocol": "HTTP",
"routeConfig": {
"routes": [
{
"functionName": "myFunction",
"methods": [
"GET"
],
"path": "/api/*",
"qualifier": "myAlias",
"rewriteConfig": {
"equalRules": [
{
"match": "/old",
"replacement": "/new"
}
],
"regexRules": [
{
"match": "^/api/.+?/(.*)",
"replacement": "/api/v2/$1"
}
],
"wildcardRules": [
{
"match": "/api/*",
"replacement": "/$1"
}
]
}
}
]
},
"subdomainCount": "1",
"tlsConfig": {
"cipherSuites": [
"TLS_RSA_WITH_RC4_128_SHA"
],
"maxVersion": "TLSv1.3",
"minVersion": "TLSv1.0"
},
"wafConfig": {
"enableWAF": true
}
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-06-14 | The API operation is not deprecated. | View Change Details |
| 2024-02-22 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
| 2023-08-30 | API Description Update | View Change Details |
| 2023-08-30 | API Description Update. The response structure of the API has changed | View Change Details |
| 2023-07-05 | The request parameters of the API has changed | View Change Details |
| 2023-06-28 | Add Operation | View Change Details |