vpc · 2017-03-12

CreateNetworkAcl

POST

Create a network ACL .

Wire call

Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /vpc/CreateNetworkAcl path used in the OpenAPI document is a documentation convenience so each action is addressable; it is not a route on the server.

curl

curl -sS https://vpc.api3.convergecloud.com/ \
  -H 'Authorization: TC3-HMAC-SHA256 Credential=<SecretId>/<YYYY-MM-DD>/vpc/tc3_request, SignedHeaders=content-type;host;x-tc-action, Signature=<sig>' \
  -H 'Content-Type: application/json; charset=utf-8' \
  -H 'Host: vpc.api3.convergecloud.com' \
  -H 'X-TC-Action: CreateNetworkAcl' \
  -H 'X-TC-Version: 2017-03-12' \
  -H 'X-TC-Timestamp: <unix-seconds>' \
  -H 'X-TC-Region: luzon' \
  -d '{"VpcId":"<VpcId>","NetworkAclName":"<NetworkAclName>"}'

Request parameters

Field	Type	Required	Description
VpcId	string	Yes	VPC instance ID, which can be obtained from the `VpcId` field in the response of the `DescribeVpcs` API.
NetworkAclName	string	Yes	Network ACL name, which can contain up to 60 bytes.
NetworkAclType	string	No	Network ACL type. Valid values: `TRIPLE` and `QUINTUPLE`.
Tags	Tag[]	No	Bound tags, such as [{"Key": "city", "Value": "shanghai"}].

Response

Fields are returned inside the Response envelope. Converge Cloud answers HTTP 200 for errors as well as successes, so read Response.Error rather than the status code — and test for the presence of that object, because Code is occasionally the empty string.

Field	Type	Description
NetworkAcl	NetworkAcl	Network ACL instance
RequestId	string	The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

Success

{
  "Response": {
    "NetworkAcl": …,
    "RequestId": "…"
  }
}

Error

{
  "Response": {
    "Error": { "Code": "…", "Message": "…" },
    "RequestId": "…"
  }
}

Try it

CredentialThe key never leaves this tab — it signs the request here. The signed request goes to /api-relay/vpc.

SecretIdSecretKey

Request bodyvalid JSONPOST vpc.api3.convergecloud.com · CreateNetworkAcl

{
  "VpcId": "<VpcId>",
  "NetworkAclName": "<NetworkAclName>"
}

This action changes resources in my own account and may create a charge. I understand.

Recorded example response — captured 2026-09-16

{
  "Response": {
    "NetworkAcl": {
      "VpcId": "vpc-gnozlhfn",
      "NetworkAclId": "acl-55ide9oi",
      "NetworkAclName": "example-network",
      "NetworkAclType": "TRIPLE",
      "CreateTime": "0000-00-00 00:00:00",
      "CreatedTime": "0000-00-00 00:00:00",
      "TagSet": []
    },
    "RequestId": "24b1175f-4a33-8946-6f2f-6d9de7944ffa"
  }
}

Behaviour

A new network ACL permits all IPv6 traffic in both directions while denying all IPv4. Write IPv6 entries explicitly if the default is not intended.