Creating a Security Group Rule
Function
A security group has inbound and outbound rules to control traffic that is allowed to reach or leave the instances associated with the security group.
Calling Method
For details, see Calling APIs.
URI
POST /v3/{project_id}/vpc/security-group-rules
Parameter | Mandatory | Type | Description |
|---|---|---|---|
project_id | Yes | String |
|
Request Parameters
Parameter | Mandatory | Type | Description |
|---|---|---|---|
dry_run | No | Boolean |
|
security_group_rule | Yes |
|
Parameter | Mandatory | Type | Description |
|---|---|---|---|
security_group_id | Yes | String |
|
description | No | String |
|
direction | Yes | String |
|
ethertype | No | String |
|
protocol | No | String |
|
multiport | No | String |
|
remote_ip_prefix | No | String |
|
remote_group_id | No | String |
|
remote_address_group_id | No | String |
|
action | No | String |
|
priority | No | String |
|
enabled | No | Boolean |
|
Response Parameters
Status code: 201
Parameter | Type | Description |
|---|---|---|
request_id | String |
|
security_group_rule | SecurityGroupRule object |
|
Parameter | Type | Description |
|---|---|---|
id | String |
|
description | String |
|
security_group_id | String |
|
direction | String |
|
protocol | String |
|
ethertype | String |
|
multiport | String |
|
action | String |
|
priority | Integer |
|
remote_group_id | String |
|
remote_ip_prefix | String |
|
remote_address_group_id | String |
|
created_at | String |
|
updated_at | String |
|
project_id | String |
|
enabled | Boolean |
|
Status code: 202
Parameter | Type | Description |
|---|---|---|
request_id | String |
|
error_msg | String |
|
error_code | String |
|
Example Requests
Create an inbound rule in the security group whose ID is 0552091e-b83a-49dd-88a7-4a5c86fd9ec3.
POST https://{Endpoint}/v3/{project_id}/vpc/security-group-rules
{
"security_group_rule" : {
"security_group_id" : "0552091e-b83a-49dd-88a7-4a5c86fd9ec3",
"direction" : "ingress",
"protocol" : "tcp",
"description" : "security group rule description",
"action" : "allow",
"priority" : 1,
"multiport" : "33",
"remote_ip_prefix" : "10.10.0.0/16"
}
} Example Responses
Status code: 201
Normal response to the POST operation. For more status codes, see Status Codes.
{
"request_id" : "1666b2708aaf849337572d6846dce781",
"security_group_rule" : {
"id" : "f626eb24-d8bd-4d26-ae0b-c16bb65730cb",
"project_id" : "060576782980d5762f9ec014dd2f1148",
"security_group_id" : "0552091e-b83a-49dd-88a7-4a5c86fd9ec3",
"direction" : "ingress",
"protocol" : "tcp",
"description" : "security group rule description",
"created_at" : "2020-08-13T07:12:36.000+00:00",
"updated_at" : "2020-08-13T07:12:36.000+00:00",
"ethertype" : "IPv4",
"remote_ip_prefix" : "10.10.0.0/16",
"multiport" : 33,
"action" : "allow",
"priority" : 1,
"remote_group_id" : null,
"remote_address_group_id" : null,
"enabled" : true
}
} Status code: 202
Normal response for the specified pre-check request of API V3. For more status codes, see Status Code.
{
"error_msg" : "Request validation has been passed with dry run...",
"error_code" : "SYS.0202",
"request_id" : "cfd81aea3f59eac7128dba4b36d516c8"
} Status Codes
Status Code | Description |
|---|---|
201 | Normal response to the POST operation. For more status codes, see Status Codes. |
202 | Normal response for the specified pre-check request of API V3. For more status codes, see Status Code. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.

