ec2.security-groups.revoke-ruleRemove a rule from a security group
DELETE /ec2/api/security-groups/{id}/rules/{ruleId}IAM ec2:RevokeSecurityGroupIngressChanges stateDestructive
The route reads the rule direction from the stored row, so which of the two Revoke actions it checks is not visible from the request.
Depending on the resource, the call checks ec2:RevokeSecurityGroupEgress instead; hold all of them to be sure it is allowed.
Request syntax
DELETE /ec2/api/security-groups/{id}/rules/{ruleId}Path parameters
idRequiredstring
Constraints: uuid
ruleIdRequiredstring
Constraints: uuid
Response
200: `data` is `{ id }` of the removed rule.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ec2:RevokeSecurityGroupIngress on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ec2 security-groups revoke-rule id ruleIdcurl -X DELETE "https://console.platform-development.deutschecloud.app/ec2/api/security-groups/id/rules/ruleId" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ec2_security-groups_revoke-rule.