ec2.security-groups.createCreate a security group with optional initial rules
Request syntax
POST /ec2/api/security-groups
{
"name": "string",
"description": "string",
"rules": "array of json",
"tags": "map of string"
}Request body
nameRequiredstring
A display name
Constraints: 1-64 chars
descriptionOptionalstring
Free text; omitted: none
Constraints: max 255 chars
rulesOptionalarray of json
Initial rules, each { direction, protocol, fromPort, toPort, cidrIpv4, description } as for adding a rule; omitted: none
tagsOptionalmap of string
Tags for the new resource, e.g. {"env": "prod", "project": "shop"}. Keys your organization marks required must be present, or the create is refused with the missing keys (GET /tags/api/keys lists them).
Constraints: key=value
Response
201: `data` is the new group (id, name, description), without its rules; the firewall behind it is made in the background.
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:CreateSecurityGroup 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 create --name examplecurl -X POST "https://console.platform-development.deutschecloud.app/ec2/api/security-groups" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"example"}'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_create.