Add assignment to IP ACL
- Print
- PDF
Add assignment to IP ACL
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
Add an assignment to an IP ACL.
Request
- POST /ip-acls/{ipAclId}/assignments
Request path
Parameter | Required | Type | Description | Restrictions |
---|---|---|---|---|
ipAclId | Y | String | IP ACL ID |
Request body
{
"consoleAccessAssignmentIds": ["string"],
"apiAccessAssignmentIds": ["string"]
}
Parameter | Required | Type | Description | Restrictions |
---|---|---|---|---|
consoleAccessAssignmentIds | N | Array | List of assignment IDs restricted from console access | |
apiAccessAssignmentIds | N | Array | List of assignment IDs restricted from API access |
Response
Response body
{
"id": "String",
"nrn": "String",
"success" : "boolean",
"message": "String"
}
Parameter | Type | Description |
---|---|---|
id | String | IP ACL ID |
nrn | String | Created IP ACL nrn |
success | Boolean | Success status |
message | String | Error message upon failure |
Error
Errors that may occur while using this action are listed below. For error response format, see ErrorResponse.
For more information about common errors, see NAVER Cloud Platform API.
HTTP status code | Error code | Error message |
---|---|---|
400 | 400 | Invalid request |
400 | 9100 | IP ACL that doesn't exist |
400 | 9101 | IP ACL target can't be empty |
400 | 9102 | Assignment - IP ACL mapping already exists |
400 | 9080 | Assignment that doesn't exist |
400 | 9106 | Assignment with incorrect access control settings |
Was this article helpful?