vpc · 2017-03-12

CreateSecurityGroup

POST

Create a security group (SecurityGroup).

Wire call

Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /vpc/CreateSecurityGroup 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: CreateSecurityGroup' \
  -H 'X-TC-Version: 2017-03-12' \
  -H 'X-TC-Timestamp: <unix-seconds>' \
  -H 'X-TC-Region: luzon' \
  -d '{"GroupName":"<GroupName>"}'

Request parameters

Field	Type	Required	Description
GroupName	string	Yes	Security group can be named freely, but cannot exceed 60 characters.
GroupDescription	string	Yes	The remarks for the security group. The maximum length is 100 characters.
ProjectId	string	No	Project ID. The default is 0. You can query it on the project management page of the Qcloud console.
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
SecurityGroup	SecurityGroup	Security group object.
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": {
    "SecurityGroup": …,
    "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 · CreateSecurityGroup

{
  "GroupName": "<GroupName>"
}

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

Recorded example response — captured 2026-09-16

{
  "Response": {
    "SecurityGroup": {
      "SecurityGroupId": "sg-4e74nn5y",
      "SecurityGroupName": "example-network",
      "SecurityGroupDesc": "example discovery — delete me",
      "ProjectId": "0",
      "CreatedTime": "2026-09-16 19:44:34",
      "UpdateTime": "2026-09-16 19:44:34",
      "Region": "luzon",
      "TagSet": []
    },
    "RequestId": "3510fc17-8796-f212-32f3-39df931a027d"
  }
}

Behaviour

A new security group contains no ingress and no egress rules.