vpc — Virtual Private Cloud
vpc · 2017-03-12

DeleteSecurityGroup

POST

Delete security groups (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/DeleteSecurityGroup 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: DeleteSecurityGroup' \
  -H 'X-TC-Version: 2017-03-12' \
  -H 'X-TC-Timestamp: <unix-seconds>' \
  -H 'X-TC-Region: luzon' \
  -d '{"SecurityGroupId":"<SecurityGroupId>"}'

Request parameters

FieldTypeRequiredDescription
SecurityGroupIdstringYesThe security group instance ID, such as `sg-33ocnj9n`. This can be obtained through DescribeSecurityGroups.

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.

FieldTypeDescription
RequestIdstringThe 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.
Request bodyvalid JSONPOST vpc.api3.convergecloud.com · DeleteSecurityGroup
Recorded example response — captured 2026-09-16
{
  "Response": {
    "RequestId": "d1858444-0e5c-7751-d59b-378efe0ced1a"
  }
}

What failure looks like

Example error responses for this action. Match on Code.

Recorded error 1
{
  "Response": {
    "Error": {
      "Code": "ResourceInUse",
      "Message": "指定资源 `sg-7timlyva` 已经在使用中。"
    },
    "RequestId": "10cf0ea4-9c4a-1aa8-2ad5-6c7e9a192371"
  }
}

Behaviour

Returns ResourceInUse for a short period after an attached instance is terminated. A deleted group reads back as ResourceNotFound.