iam.policies.createCreate a customer-managed policy
`document` is a JSON string, validated by validatePolicyDocument before it is stored.
Request syntax
POST /iam/api/policies
{
"name": "string",
"description": "string",
"document": "string"
}Request body
nameRequiredstring
The policy’s name
Constraints: 1-128 chars
descriptionOptionalstring
What the policy is for
Constraints: max 512 chars
documentRequiredstring
The policy document as JSON text: {"Version":"2024-01-01","Statement":[{"Effect":"Allow","Action":[…],"Resource":[…]}]}; checked before it is stored
Constraints: min 1 chars
Response
201 with the new policy (type custom): id, name, description, document, createdAt, updatedAt. An invalid document is answered 400 with the reason.
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 iam:CreatePolicy 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 iam policies create --name example --document examplecurl -X POST "https://console.platform-development.deutschecloud.app/iam/api/policies" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"example","document":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_policies_create.