ModifySecurityGroupEgressRule

Description

call ModifySecurityGroupEgressRule to modify the description information of the security group exit direction rule. This interface can only modify the description information. If you need to modify the policy, port range, authorization object and other information of the security group rule, please modify it in the ECS management console.

Request Method

POST

Request Path

/apsara/route/Ecs/ModifySecurityGroupEgressRule

Request Parameters Common Parameters

Name	Location	Type	Required	Sample value	Description
Policy	BODY	string	No	accept	access rights. Value range: accept: Accept access. drop: deny access and do not send back a deny message. default value: accept.
Description	BODY	string	No	Thisisanewsecuritygrouprule	description information of security group rules. The length is 1~512 characters.
SourcePortRange	BODY	string	No	80/80	the port range related to the transport layer protocol open by the source security group. Value range: TCP/UDP protocol: the value range is 1~65535. Use a slash (/) to separate the start and end ports. Correct demonstration: 1/200; Error demonstration: 200/1. ICMP protocol:-1/-1. GRE protocol:-1/-1. all:-1/-1.
Priority	BODY	string	No	1	security group rule priority. Value range: 1~100 default value: 1.
SecurityGroupId	BODY	string	Yes	sg-bp67acfmxazb4ph***	source security group ID.
Ipv6SourceCidrIp	BODY	string	No	2001:db8:1234:1a00::***	source IP address range. Supports IP address ranges in CIDR format and IPv6 format. default value: 0.0.0.0/0.
NicType	BODY	string	No	internet	the network card type of the classic network type security group rule. Value range: internet: public network card. intranet: intranet network card. VPC type security group rules do not need to set the network card type. The default value is intranet and can only be intranet. When setting mutual access between security groups, that is, DestGroupId is specified and DestCidrIp, only for intranet. default value: internet.
DestGroupId	BODY	string	No	sg-bp67acfmxazb4pi***	destination security group ID.
version	BODY	string	No	2016-01-01	version of api
PortRange	BODY	string	Yes	80/80	the port range related to the transport layer protocol open by the source security group. Value range: TCP/UDP protocol: the value range is 1~65535. Use a forward slash (/) to separate the start and end ports. Correct demonstration: 1/200; Error demonstration: 200/1. ICMP protocol:-1/-1. GRE protocol:-1/-1. all:-1/-1.
DestGroupOwnerAccount	BODY	string	No	EcsforCloud@Alibaba.com	the account ID of the destination security group, that is, the UID.
regionId	BODY	string	Yes	No sample value for this parameter.	region id
SourceCidrIp	BODY	string	No	10.0.0.0/8	source IP address range. CIDR format and IPv4 format are supported for IP address ranges. default value: 0.0.0.0/0.
DestGroupOwnerId	BODY	long	No	155780923770	the logon name of the account to which the destination security group belongs.
IpProtocol	BODY	string	Yes	tcp	transport layer protocol. Case insensitive. Value range: icmp icmpv6 gre tcp udp all: supports all protocols
DestCidrIp	BODY	string	No	10.0.0.0/8	destination IP address range. CIDR format and IPv4 format are supported for IP address ranges. default value: 0.0.0.0/0.
RegionId	BODY	string	Yes	cn-qingdao-env17-d01	the region ID of the source security group. You can call the DescribeRegions to view the latest Alibaba Cloud region list.
Ipv6DestCidrIp	BODY	string	No	2001:db8:1233:1a00::***	destination IP address range. Supports IP address ranges in CIDR format and IPv6 format. default value: 0.0.0.0/0.
ClientToken	BODY	string	No	123e4567-e89b-12d3-a456-426655440000	Ensure request idempotence. Generate a parameter value from your client to ensure that the parameter value is unique between different requests. ClientToken only supports ASCII characters and cannot exceed 64 characters. For more details, please refer to the section on how to ensure idempotence in the cloud server ECS development guide.

Return data

Name	Type	Sample value	Description
RequestID	string	1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC	Request id

Example

Successful Response example

{
 "RequestID":"1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC"
}

Failed Response example

{
 "errorSample":
 {
  "resultCode":-1,
  "resultMsg":"system error",
  "result":null
 }

}