Creates a custom security policy for a TCP/SSL listener.
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:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level,
All Resources
is 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 |
---|---|---|---|---|
nlb:CreateSecurityPolicy | create | *SecurityPolicy acs:nlb:{#regionId}:{#accountId}:securitypolicy/* |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
TlsVersions | array | Yes | The Transport Layer Security (TLS) versions supported by the security policy. Valid values: TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3. | |
string | Yes | A TLS version supported by the security policy. Valid values: TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3. All four versions can be specified for a security policy. | TLSv1.0 | |
SecurityPolicyName | string | No | The name of the security policy. It must be 1 to 200 characters in length, and can contain letters, digits, periods (.), underscores (_), and hyphens (-). | TLSCipherPolicy |
ResourceGroupId | string | No | The ID of the resource group to which the security policy belongs. | rg-atstuj3rtop**** |
Ciphers | array | Yes | The cipher suites supported by the security policy. Valid values of this parameter vary based on TlsVersions. A security policy supports up to 32 cipher suites. TLSv1.0 and TLSv1.1 support the following cipher suites:
TLSv1.2 supports the following cipher suites:
TLSv1.3 supports the following cipher suites:
| |
Cipher | string | Yes | A cipher suite supported by the security policy. Valid values of this parameter vary based on TlsVersions. You can specify up to 32 cipher suites. TLSv1.0 and TLSv1.1 support the following cipher suites:
TLSv1.2 supports the following cipher suites:
TLSv1.3 supports the following cipher suites:
| ECDHE-ECDSA-AES128-SHA |
DryRun | boolean | No | Specifies whether to perform a dry run. Valid values:
| false |
ClientToken | string | No | The client token used to ensure the idempotence of the request. You can use the client to generate the token. Ensure that the token is unique among different requests. Only ASCII characters are allowed. Note
If you do not set this parameter, the value of RequestId is used.**** The value of RequestId is different for each request.
| 123e4567-e89b-12d3-a456-426655440000 |
RegionId | string | No | The ID of the region where the NLB instance is deployed. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
Tag | array<object> | No | The tags. | |
object | No | The tag. | ||
Key | string | No | The key of the tag. It must be 1 to 64 characters in length, cannot start with You can add up to 20 tags for the security policy in each call. | KeyTest |
Value | string | No | The value of the tag. It must be 1 to 128 characters in length, cannot start with You can add up to 20 tags for the security policy in each call. | ValueTest |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "D7A8875F-373A-5F48-8484-25B07A61F2AF",
"SecurityPolicyId": "tls-bp14bb1e7dll4f****",
"JobId": "72dcd26b-f12d-4c27-b3af-18f6aed5****"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | IllegalParam | The param of %s is illegal. | - |
403 | Forbidden.NoPermission | Authentication is failed for NoPermission. | Authentication is failed for NoPermission. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-01-22 | The Error code has changed | View Change Details |
2023-09-05 | The Error code has changed | View Change Details |
2023-08-22 | The Error code has changed | View Change Details |
2023-06-30 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-06-29 | The request parameters of the API has changed | View Change Details |