UpdateTrafficMarkingPolicyAttribute - Cloud Enterprise Network

Modifies the name, description, and traffic classification rules of a traffic marking policy.

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 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 support 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 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. For more information, see Common condition keys.
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

cen:UpdateTrafficMarkingPolicyAttribute

update

*CenInstance

acs:cen:*:{#accountId}:ceninstance/{#CenId}

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 value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.	123e4567-e89b-12d3-a456-426****
DryRun	boolean	No	Specifies whether to perform a dry run. Valid values: true: preforms a dry run. The system checks the required parameters, request syntax, and limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the `DryRunOperation` error code is returned. false (default): performs a dry run and sends the request.	false
TrafficMarkingPolicyId	string	Yes	The ID of the traffic marking policy.	tm-u9nxup5kww5po8****
TrafficMarkingPolicyName	string	No	The new name of the traffic marking policy. The name must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). It must start with a letter.	nametest
TrafficMarkingPolicyDescription	string	No	The new description of the traffic marking policy. The description must be 2 to 128 characters in length, and can contain letters, digits, underscores (_), and hyphens (-). The description must start with a letter.	desctest
AddTrafficMatchRules	array	No	The traffic classification rules to be added to the traffic marking policy. You can add at most 50 traffic classification rules in each call.
	object	No	The traffic classification rules to be added to the traffic marking policy.
MatchDscp	integer	No	The Differentiated Service Code Point (DSCP) value that is used to match packets. Valid values: 0 to 63. Requests that carry the specified DSCP value are considered a match. If you do not specify a DSCP value, packets are considered a match regardless of the DSCP value. Note The DSCP value that you specify for this parameter is the DSCP value that packets carry before they are transmitted over the inter-region connection. You can create up to 50 traffic classification rules in each call. You can specify a DSCP value for each traffic classification rule.	1
DstCidr	string	No	The destination CIDR block of packets. IPv4 and IPv6 addresses are supported. Packets whose destination IP addresses fall into the specified destination CIDR block meet the traffic classification rule. If you do not specify a destination CIDR block, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a destination CIDR block for each traffic classification rule.	172.30.0.0/24
TrafficMatchRuleDescription	string	No	The description of the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a description for each traffic classification rule. This parameter is optional. If you enter a description, it must be 1 to 256 characters in length and cannot start with http:// or https://.	test1
Protocol	string	No	The protocol that is used to match packets. Traffic classification rules support the following protocols: HTTP, HTTPS, TCP, UDP, SSH, and Telnet. For more information, log on to the CEN console. Some protocols use a fixed port. Click to view the protocols and ports. If the protocol is ICMP, set the destination port to -1. If the protocol is GRE, set the destination port to -1. If the protocol is SSH, set the destination port to 22. If the protocol is Telnet, set the destination port to 23. If the protocol is HTTP, set the destination port to 80. If the protocol is HTTPS, set the destination port to 443. If the protocol is MS SQL, set the destination port to 1443. If the protocol is Oracle, set the destination port to 1521. If the protocol is Mysql, set the destination port to 3306. If the protocol is RDP, set the destination port to 3389. If the protocol is Postgre SQL, set the destination port to 5432. If the protocol is Redis, the destination port must be 6379. You can create up to 50 traffic classification rules in each call. You can specify a protocol for each traffic classification rule.	UDP
DstPortRange	array	No	The destination port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose destination ports fall within the specified destination port range are considered a match. If you do not specify a destination port range, packets are considered a match regardless of the destination port. You can enter up to two port numbers. Take note of the following rules: If you enter only one port number, such as 1, packets whose destination port is 1 match the traffic classification rule. A value of -1 specifies all destination ports. If you enter two port numbers, such as 1 and 200, packets whose destination ports fall into 1 and 200 are considered a match. If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a destination port range for each traffic classification rule.
	integer	No	The destination port range that is used to match packets. Valid values: -1 and 1 to 65535. Packets whose destination ports fall within the specified destination port range are considered a match. If you do not specify a destination port range, packets are considered a match regardless of the destination port. You can enter up to two port numbers. Take note of the following rules: If you enter only one port number, such as 1, packets whose destination port is 1 match the traffic classification rule. If you enter two port numbers, such as 1 and 200, packets whose destination ports fall into 1 and 200 are considered a match. If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a destination port range for each traffic classification rule.	77
SrcCidr	string	No	The source CIDR block of packets. IPv4 and IPv6 addresses are supported. Packets whose source IP addresses fall into the specified source CIDR block meet the traffic classification rule. If you do not specify a source CIDR block, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a source CIDR block for each traffic classification rule.	10.128.32.0/19
SrcPortRange	array	No	The source port range that is used to match packets. Valid values: -1 and 1 to 65535. The traffic classification rule matches the packets whose source ports fall within the source port range. If you do not specify this parameter, packets are considered a match regardless of the source port. You can enter up to two port numbers. Take note of the following rules: If you enter only one port number, such as 1, packets whose source port is 1 are considered a match. A value of -1 specifies all source ports. If you enter two port numbers, such as 1 and 200, packets whose source ports fall into 1 and 200 are considered a match. If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a source port range for each traffic classification rule.
	integer	No	The source port range that is used to match packets. Valid values: -1 and 1 to 65535. The traffic classification rule matches the packets whose source ports fall within the source port range. If you do not specify this parameter, packets are considered a match regardless of the source port. You can enter up to two port numbers. Take note of the following rules: If you enter only one port number, such as 1, packets whose source port is 1 are considered a match. If you enter two port numbers, such as 1 and 200, packets whose source ports fall into 1 and 200 are considered a match. If you enter two port numbers and one of them is -1, the other port number must also be -1. In this case, all packets meet the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a source port range for each traffic classification rule.	22
TrafficMatchRuleName	string	No	The name of the traffic classification rule. You can create up to 50 traffic classification rules in each call. You can specify a name for each traffic classification rule. The name can be empty or 1 to 128 characters in length, and cannot start with http:// or https://.	Guangzhou Testing
AddressFamily	string	No	The address family. Valid values: You can set the value to IPv4 or IPv6, or leave the value empty.	IPv4
DeleteTrafficMatchRules	array	No	The traffic classification rules to be deleted from the traffic marking policy. Note Specify detailed information about the traffic classification rule, such as the source CIDR block, destination CIDR block, source port, destination port, and DSCP value. If you do not specify sufficient information, the system may fail to match the traffic classification rule that you want to delete.
	object	No	The traffic classification rules to be deleted from the traffic marking policy.
MatchDscp	integer	No	The DSCP value that is used to match packets.	3
DstCidr	string	No	The destination CIDR block of packets. IPv4 and IPv6 addresses are supported.	192.168.200.3/32
TrafficMatchRuleDescription	string	No	The description of the traffic classification rule. This parameter is optional. If you enter a description, it must be 1 to 256 characters in length and cannot start with http:// or https://.	Hangzhou-to-Qingdao CAT
Protocol	string	No	The protocol that is used to match packets. You can call the ListTrafficMarkingPolicies operation to query the details about a traffic classification rule.	TCP
DstPortRange	array	No	The destination port range that is used to match packets.
	integer	No	The destination port range that is used to match packets.	-1
SrcCidr	string	No	The source CIDR block of packets. IPv4 and IPv6 addresses are supported.	10.72.0.0/16
SrcPortRange	array	No	The source port range that is used to match packets.
	integer	No	The source port range that is used to match packets.	23
TrafficMatchRuleName	string	No	The name of the traffic classification rule. The name can be empty or 1 to 128 characters in length, and cannot start with http:// or https://.	test
AddressFamily	string	No	The address family. Valid values: You can set the value to IPv4 or IPv6, or leave the value empty.	IPv6

Response parameters

Parameter	Type	Description	Example
	object	The response.
RequestId	string	The ID of the request.	60BB11B2-7BF4-54DC-BCC9-F706E1EB02AC

Examples

Success response

JSON format

{
  "RequestId": "60BB11B2-7BF4-54DC-BCC9-F706E1EB02AC"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidTrafficMarkingPolicyId.NotFound	TrafficMarkingPolicyId is not found.	The error message returned because the specified traffic marking policy ID (TrafficMarkingPolicyId) does not exist.
400	IncorrectStatus.TrafficMarkingPolicy	The status of TrafficMarkingPolicy is incorrect.	The error message returned because the status of the traffic marking policy does not support this operation. Try again later.
400	Duplicated.AddTrafficMatchRules	The parameter AddTrafficMatchRules are duplicated.
400	Duplicated.DeleteTrafficMatchRulese	The parameter DeleteTrafficMatchRules are duplicated.
400	InstanceExist.AddTrafficMatchRules	The instance already exists.	The error message returned because the specified instance already exists.
400	Duplicated.AddTrafficMatchRulesAndDeleteTrafficMatchRules	The same rule in AddTrafficMatchRules and DeleteTrafficMatchRules is not supported..	The error message returned because the AddTrafficMatchRules and DeleteTrafficMatchRules cannot specify the same route. Delete duplicate routes and try again.
400	IllegalParam.DstPortRange	The specified DstPortRange is illegal.	The specified DstPortRange is illegal.
400	IllegalParam.SrcPortRange	The specified SrcPortRange is illegal.
400	AttrMismatching.CidrAddressFamily	Attribute SrcCidr or DstCidr of TrafficMarkRule does not match AddressFamily.	Attribute SrcCidr or DstCidr of TrafficMarkRule does not match AddressFamily.
400	IllegalParam.AddressFamily	AddressFamily is illegal.	The AddressFamily value of the request parameter is invalid. Valid values are IPv4 or IPv6.
400	AttrMismatching.SrcCidrDstCidr	Attribute SrcCidr of TrafficMarkRule does not match DstCidr.	Attribute SrcCidr of TrafficMarkRule does not match DstCidr.
400	AttrMismatching.CidrProtocol	Attribute SrcCidr or DstCidr of TrafficMarkRule does not match Protocol.	Attribute SrcCidr or DstCidr of TrafficMarkRule does not match Protocol.
400	InvalidTransitRouterMode.NeedUpgrade	TransitRouter need to upgrade.	The error message returned because the specified transit router mode is not supported.
400	OperationUnsupported.SrcPortRange	Current TR version does not support setting source port range.	Current TR version does not support setting source port range
400	OperationUnsupported.DstPortRange	Current TR version does not support setting destination port range.	Current TR version does not support setting destination port range.
400	OperationUnsupported.IPv6Cidr	The traffic marking policy for current TR type does not support IPv6 CIDR.	The flow classification rules in the flow marking policy of the basic version forwarding router do not support IPv6 network segments.
400	IllegalParam.DstCidr	DstCidr is illegal.	The error message returned because the specified destination CIDR block (DstCidr) is invalid.
400	IllegalParam.SrcCidr	SrcCidr is illegal.	The error message returned because the specified source CIDR block is invalid.
400	InvalidParameter	Invalid parameter.	The error message returned because the parameter is set to an invalid value.
400	Unauthorized	The AccessKeyId is unauthorized.	The error message returned because you do not have the permissions to perform this operation.
400	MissingParam.TrafficMarkingPolicyId	The parameter TrafficMarkingPolicyId is mandatory.
404	InvalidDeleteTrafficMatchRules.NotFound	The specified DeleteTrafficMatchRules are not found.	The error message returned because the value of the DeleteTrafficMatchRules parameter does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.