ec2.vpcs.createCreate a VPC
Request syntax
POST /ec2/api/vpcs
{
"regionId": "string",
"name": "string",
"cidrBlock": "string",
"tags": "map of string"
}Request body
regionIdRequiredstring
The region to create it in, e.g. de1
Constraints: min 1 chars
nameOptionalstring
A display name; omitted: none
Constraints: max 64 chars
cidrBlockOptionalstring
Private IPv4 range (RFC 1918), /8 to /24, starting on its boundary
Default:
"10.0.0.0/16"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 VPC (id, name, regionId, cidrBlock, isDefault, status); its provider network 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:CreateVpc 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 vpcs create --region-id examplecurl -X POST "https://console.platform-development.deutschecloud.app/ec2/api/vpcs" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"regionId":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ec2_vpcs_create.