ModifySecurityGroupPolicies
Reset the `Egress` and `Ingress` rules (SecurityGroupPolicy) of a security group.
Wire call
Converge Cloud is RPC over HTTP. There is one path — / — and the action travels in the X-TC-Action header. The /vpc/ModifySecurityGroupPolicies path used in the OpenAPI document is a documentation convenience so each action is addressable; it is not a route on the server.
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: ModifySecurityGroupPolicies' \
-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 | The security group policy set. SecurityGroupPolicySet object must specify new egress and ingress policies at the same time. SecurityGroupPolicy object does not support custom index (PolicyIndex). |
| SortPolicys | boolean | No | Whether the security group rule is sorted. Default value: False. If it is set to `True`, security group rules will be strictly sorted according to the sequence specified in the `SecurityGroupPolicySet` parameter. Manual entry may cause omission, so we recommend sorting security group rules in the console. |
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. |
{
"Response": {
// action-specific fields,
"RequestId": "…"
}
}{
"Response": {
"Error": { "Code": "…", "Message": "…" },
"RequestId": "…"
}
}Try it
Recorded example response — captured 2026-09-16
{
"Response": {
"RequestId": "4c8f1146-8d71-f71b-254e-7b73eafcae3d"
}
}Behaviour
Replaces the rules for each direction supplied. Sending only Ingress removes every existing ingress rule and leaves egress unchanged, so read the current rules for that direction and resend them with the change applied.