vpc · 2017-03-12

CreateSecurityGroupPolicies

POST

Create security group policies (`SecurityGroupPolicy`).

Wire call

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

Request parameters

Field	Type	Required	Description
SecurityGroupId	string	Yes	The security group instance ID, such as `sg-33ocnj9n`. This can be obtained through DescribeSecurityGroups.
SecurityGroupPolicySet	SecurityGroupPolicySet	Yes	Security group policy set.

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
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": {
    // action-specific fields,
    "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 · CreateSecurityGroupPolicies

{
  "SecurityGroupId": "<SecurityGroupId>",
  "SecurityGroupPolicySet": "<SecurityGroupPolicySet>"
}

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

Recorded example response — captured 2026-09-16

{
  "Response": {
    "RequestId": "899067b0-ad44-a314-3cb8-8f35bc14acf9"
  }
}

What failure looks like

Example error responses for this action. Match on Code.

Recorded error 1

{
  "Response": {
    "Error": {
      "Code": "InvalidParameter.Coexist",
      "Message": "请求中不支持同时传入参数 `Egress and Ingress`。"
    },
    "RequestId": "e57d40eb-9dba-368f-0027-c7d3cd825def"
  }
}

Behaviour

Ingress and Egress cannot be supplied in the same call; a request containing both returns InvalidParameter.Coexist.