Enforce Container Image Signature Policies via API - Security Center

This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Modify Container Image Signature Security Policy.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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
yundun-sas:ModifyBinarySecurityPolicy	update	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
SourceIp	string	No	The IP address of the access source.	1.2.3.4
Name	string	No	Policy name.	test-policy-04-11
Remark	string	No	Remark.	Remark
Policy	string	Yes	Policy content. JSON format, Key values: policyMode: Type of policy, default is requireAttestor. requiredAttestors: Required attestors.	{\"PolicyMode\":\"requireAttestor\",\"RequiredAttestors\":[\"test-xcs-04-11-hhht\"]}
Clusters	string	Yes	Cluster information.	[{\"Namespaces\":[\"default\"],\"ClusterId\":\"c9f5b93a8da8f4341b77*********\"},{\"Namespaces\":[\"default\"],\"ClusterId\":\"cc12429dbb8f644f690b0*********\"}]
Status	string	No	Set to enable or disable the policy. Values: enabled: Enable the protection policy. disabled: Disable the protection policy.	enabled

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The request ID of the result.	C699E4E4-F2F4-58FC-A949-457FFE59****

Examples

Sample success responses

JSONformat

{
  "RequestId": "C699E4E4-F2F4-58FC-A949-457FFE59****"
}

Error codes

HTTP status code	Error code	Error message	Description
403	NoPermission	caller has no permission	You are not authorized to do this operation.
500	ServerError	ServerError	-

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation

No change history