Creates a network access control list (ACL).
debugging
debuggingAuthorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| vpc:CreateNetworkAcl | Write |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| VpcId | string | Yes | The ID of the virtual private cloud (VPC) to which the network ACL belongs. If the VPC contains Elastic Compute Service (ECS) instances of the following instance families, you must upgrade the ECS instances or release the ECS instances. Otherwise, you cannot create a network ACL for the VPC. ecs.c1, ecs.c2, ecs.c4, ecs.c5, ecs.ce4, ecs.cm4, ecs.d1, ecs.e3, ecs.e4, ecs.ga1, ecs.gn4, ecs.gn5, ecs.i1, ecs.m1, ecs.m2, ecs.mn4, ecs.n1, ecs.n2, ecs.n4, ecs.s1, ecs.s2, ecs.s3, ecs.se1, ecs.sn1, ecs.sn2, ecs.t1, and ecs.xn4.
Note
If your VPC contains ECS instances of the preceding instance families and you create a network ACL for the VPC, you must upgrade the ECS instances. Otherwise, the network ACL cannot work as expected.
| vpc-dsfd34356vdf**** |
| NetworkAclName | string | No | The name of the network ACL. The name must be 1 to 128 characters in length and cannot start with | acl-1 |
| Description | string | No | The description of the network ACL. The description must be 1 to 256 characters in length and cannot start with | This is my NetworkAcl. |
| RegionId | string | Yes | The region ID of the network ACL. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
| 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. Note
If you do not specify this parameter, the system uses RequestId as ClientToken. RequestId may be different for each API request.
| 0c593ea1-3bea-11e9-b96b-88e9fe637760 |
Response parameters
Examples
Sample success responses
JSONformat
{
"NetworkAclId": "nacl-a2do9e413e0spzasx****",
"RequestId": "0ED8D006-F706-4D23-88ED-E11ED28DCAC0",
"NetworkAclAttribute": {
"Status": "Modifying",
"VpcId": "vpc-a2d33rfpl72k5xsscd****",
"CreationTime": "2021-12-25 11:33:27",
"Description": "This is my NetworkAcl.",
"NetworkAclName": "acl-1\t",
"NetworkAclId": "nacl-a2do9e413e0spdefr****",
"RegionId": "cn-hangzhou\t",
"IngressAclEntries": {
"IngressAclEntry": [
{
"NetworkAclEntryId": "nae-a2dk86arlydmexscd****",
"NetworkAclEntryName": "acl-3\t",
"Policy": "accept",
"Description": "This is IngressAclEntries.\t",
"SourceCidrIp": "10.0.0.0/24\t",
"Protocol": "all",
"Port": "-1/-1"
}
]
},
"EgressAclEntries": {
"EgressAclEntry": [
{
"NetworkAclEntryId": "nae-a2d447uw4tillxsdc****",
"NetworkAclEntryName": "acl-2",
"Policy": "accept",
"Description": "This is EgressAclEntries.",
"Protocol": "all",
"DestinationCidrIp": "10.0.0.0/24",
"Port": "-1/-1\t"
}
]
},
"Resources": {
"Resource": [
{
"Status": "BINDED",
"ResourceType": "VSwitch",
"ResourceId": "vsw-bp1de348lntdwgthy****"
}
]
}
}
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | ParameterMissing.AliUid | ParameterMissing.AliUid | - |
| 400 | ParameterMissing.Bid | ParameterMissing.Bid | - |
| 400 | ParameterMissing.RegionId | ParameterMissing.RegionId | - |
| 400 | ParameterEmpty.RegionId | ParameterEmpty.RegionId | - |
| 400 | ParameterMissing.VpcId | ParameterMissing.VpcId | - |
| 400 | ParameterLengthIllegal.Name | ParameterLengthIllegal.Name | The length of the rule name is invalid. |
| 400 | ParameterIllegal.Name | ParameterIllegal.Name | The name of the entry is invalid. |
| 400 | ParameterLengthIllegal.Description | ParameterLengthIllegal.Description | - |
| 400 | ParameterIllegal.Description | ParameterIllegal.Description | - |
| 400 | ParameterEmpty.VpcId | ParameterEmpty.VpcId | - |
| 400 | InvalidVpcId.NotFound | The vpc is not exist. | - |
| 400 | QuotaExceed.NetworkAcl | Network acl is over limit. | - |
| 400 | NotSupport.NetworkAcl | Network acl is not support now. | - |
| 500 | InternalError | The request processing has failed due to some unknown error. | An unknown error occurred. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2023-11-24 | The error codes of the API operation change.,The input parameters of the API operation change. | see changesets | ||||||||||
| ||||||||||||
| 2023-07-05 | The error codes of the API operation change.,The input parameters of the API operation change. | see changesets | ||||||||||
| ||||||||||||
| 2023-05-09 | API Description Update,The error codes of the API operation change. | see changesets | ||||||||||
|