Available in VPC
Add an inbound rule to an ACG.
Syntax
The addAccessControlGroupInboundRule syntax is as follows:
./ncloud vserver addAccessControlGroupInboundRule \
--vpcNo <vpc-no> \
--accessControlGroupNo <acg-no> \
--accessControlGroupRuleList <rule-config> \
[--regionCode <KR|SGN|JPN>] \
[--output <json|xml>]
Options
This section describes the options available when running addAccessControlGroupInboundRule.
Required options
The following options are required for addAccessControlGroupInboundRule.
| Options | Type | Required | Description |
|---|---|---|---|
--vpcNo |
String | Required | VPC number
|
--accessControlGroupNo |
String | Required | ACG number |
--accessControlGroupRuleList |
List | Required | List of ACG inbound rules
|
Common options
For information about the options common to all vserver subcommands, see Server (VPC) options.
Examples
If the request to add an inbound rule to an ACG is successful, the protocol information and access source for each rule are returned.
Command
The command example is as follows:
./ncloud vserver addAccessControlGroupInboundRule \
--vpcNo 12345678 \
--accessControlGroupNo 67890123 \
--accessControlGroupRuleList "protocolTypeCode='TCP', ipBlock='192.0.2.0/24', portRange='22', accessControlGroupRuleDescription='SSH from office'" \
--regionCode KR \
--output json
Output
The output example is as follows:
{
"addAccessControlGroupInboundRuleResponse": {
"totalRows": 1,
"accessControlGroupRuleList": [
{
"accessControlGroupNo": "67890123",
"protocolType": {
"code": "TCP",
"codeName": "tcp",
"number": 6
},
"ipBlock": "192.0.2.0/24",
"accessControlGroupSequence": "",
"portRange": "22",
"accessControlGroupRuleType": {
"code": "INBND",
"codeName": "Inbound"
},
"accessControlGroupRuleDescription": "SSH from office"
}
],
"requestId": "c3d4e5f6-7890-1234-cdef-345678901234",
"returnCode": "0",
"returnMessage": "success"
}
}