dcloud iam access-keys createCreate an access key and return its secret once
The secret is in the response and nowhere else. The key signs Deutsche Cloud API calls (`Authorization: EWS-ACCESS-KEY id:secret`) and S3 requests (SigV4: id as the access key id, secret as the secret access key). Every key expires: `expiresAt` is in the response. With `scopePolicy` the key can do only what both the principal and the scope allow.
Synopsis
dcloud iam access-keys create [flags]Flags
--iam-user-idOptionalstring
The ID of the IAM user the key signs in as; omitted: yourself
Constraints: uuid
--expires-in-daysOptionalnumber
Days until the key expires; default the organization’s default (90), at most its maximum (365)
Constraints: integer, 1-3650
--descriptionOptionalstring
What the key is for
Constraints: max 256 chars
--scope-policyOptionalstring
A policy document (JSON text) that caps the key: a request needs the principal’s policies AND this document to allow it. E.g. S3 on one bucket: {"Version":"2024-01-01","Statement":[{"Effect":"Allow","Action":["s3:ListObjects","s3:GetObject"],"Resource":["rn:ews::<org>:s3:bucket/<name>","rn:ews::<org>:s3:bucket/<name>/object/*"]}]}
Constraints: max 10240 chars
--act-as-memberOptionalboolean (--act-as-member / --no-act-as-member)
Must be true when iamUserId is another person’s own IAM user: everything done with the key is recorded as that person, and the audit entry names both
Example
dcloud iam access-keys createGenerated from the API description, the same one the API checks requests against and the CLI is built from.