Creates a Transport Layer Security (TLS) policy.
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 |
|---|---|---|---|---|
| slb:CreateTLSCipherPolicy | Read |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The ID of the region where the Server Load Balancer (SLB) instance is created. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
| Name | string | Yes | The name of the TLS policy. The name must be 1 to 200 characters in length, and can contain letters, digits, periods (.), underscores (_), and hyphens (-). | TLSPolicy-test |
| Ciphers | array | Yes | The supported cipher suites, which are determined by the TLS protocol version. You can specify at most 32 cipher suites. TLS 1.0 and TLS 1.1 support the following cipher suites:
TLS 1.2 supports the following cipher suites:
TLS 1.3 supports the following cipher suites:
| |
| string | Yes | The supported cipher suites, which are determined by the TLS protocol version. You can specify at most 32 cipher suites. TLS 1.0 and TLS 1.1 support the following cipher suites:
TLS 1.2 supports the following cipher suites:
TLS 1.3 supports the following cipher suites:
| ECDHE-ECDSA-AES128-SHA | |
| TLSVersions | array | Yes | The version of the TLS protocol. Valid values: TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3. You can specify at most four TLS versions. | |
| string | Yes | The version of the TLS protocol. Valid values: TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3. You can specify at most four TLS versions. | TLSv1.0 |
Response parameters
Examples
Sample success responses
JSONformat
{
"TLSCipherPolicyId": "tls-bp14bb1e7dll4f****",
"RequestId": "D7A8875F-373A-5F48-8484-25B07A61F2AF"
}Error codes
| HTTP status code | Error code | Error message |
|---|---|---|
| 400 | MissingParam.Name | The param Name is missing. |
| 400 | MissingParam.TlsVersions | The param TlsVersions is missing. |
| 400 | MissingParam.Ciphers | The param Ciphers is missing. |
| 400 | ParamDuplicateError.TlsVersions | The param TlsVersions is duplicate in request. |
| 400 | ParamDuplicateError.Ciphers | The param Ciphers is duplicate in request. |
| 400 | TLSPolicyNoSupportVersion | The specified TLS version is not supported. |
| 400 | TLSPolicyNoSupportCipher | The specified TLS cipher is not supported. |
| 400 | TLSCipherPolicyOverLimit | The TLSCipherPolicy is over the limit. |
For a list of error codes, visit the Service error codes.