CreateSecurityPolicy-阿里云帮助中心

Creates a custom security policy in a specified region.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

alb:CreateSecurityPolicy

create

*SecurityPolicy

acs:alb:{#regionId}:{#accountId}:securitypolicy/*

None

Request parameters

Parameter	Type	Required	Description	Example
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. Note If you do not specify this parameter, the system automatically uses the RequestId as the ClientToken. The RequestId of each API request may be different.	593B0448-D13E-4C56-AC0D-FDF0F******
DryRun	boolean	No	Specifies whether to perform a dry run. Valid values: true: performs a dry run. The system checks the required parameters, the request format, and business limits. If the request fails the check, an error message is returned. If the request passes the check, the `DryRunOperation` error code is returned. false (default): sends a normal request. After the request passes the check, a 2xx HTTP status code is returned and the operation is performed.	true
TLSVersions	array	Yes	The TLS protocol versions that are supported.
	string	Yes	The TLS protocol version. Valid values: TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3.	TLSv1.0
ResourceGroupId	string	No	The ID of the resource group.	rg-atstuj3rtop****
SecurityPolicyName	string	Yes	The name of the security policy. The name must be 2 to 128 characters in length, and can contain letters, digits, Chinese characters, periods (.), underscores (_), hyphens (-), and spaces. The name must start with a letter, a Chinese character, or a digit.	test-secrity
Ciphers	array	Yes	The supported cipher suites.
	string	Yes	The supported cipher suites, which are determined by the TLS versions that you specify in the TLSVersions parameter. A cipher suite is valid if it is supported by at least one of the specified TLS versions. Note If you specify TLSv1.3, the cipher suites that you specify must be supported by TLSv1.3. Cipher suites supported by TLSv1.0 and TLSv1.1: ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-SHA ECDHE-RSA-AES128-SHA ECDHE-RSA-AES256-SHA AES128-SHA AES256-SHA DES-CBC3-SHA Cipher suites supported by TLSv1.2: ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-SHA ECDHE-RSA-AES128-SHA ECDHE-RSA-AES256-SHA AES128-SHA AES256-SHA DES-CBC3-SHA ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES256-SHA384 AES128-GCM-SHA256 AES256-GCM-SHA384 AES128-SHA256 AES256-SHA256 ECDHE-RSA-CHACHA20-POLY1305 ECDHE-ECDSA-CHACHA20-POLY1305 Cipher suites supported by TLSv1.3: TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_SHA256 TLS_AES_128_CCM_8_SHA256	ECDHE-ECDSA-AES128-SHA
Tag	array<object>	No	The tags.
	object	No	A tag.
Key	string	No	The tag key. The key can be up to 128 characters long, cannot start with `aliyun` or `acs:`, and cannot contain `http://` or `https://`.	env
Value	string	No	The tag value. The value can be up to 128 characters long, cannot start with `aliyun` or `acs:`, and cannot contain `http://` or `https://`.	product

Response elements

Element	Type	Description	Example
	object	The response parameters.
RequestId	string	The ID of the request.	593B0448-D13E-4C56-AC0D-FDF0******
SecurityPolicyId	string	The ID of the security policy.	sp-9cdjz6o8ha70******

Examples

Success response

JSON format

{
  "RequestId": "593B0448-D13E-4C56-AC0D-FDF0******",
  "SecurityPolicyId": "sp-9cdjz6o8ha70******"
}

Error codes

HTTP status code	Error code	Error message	Description
400	QuotaExceeded.SecurityPoliciesNum	The quota of %s is exceeded, usage %s/%s.	The quota of %s is exceeded. Usage: %s/%s.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.