dcloud iam access-keys create

Create an access key and return its secret once

IAM iam:CreateAccessKeyChanges state

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. What it may do is its account’s policies: give a script its own service account with exactly the policy it needs. For a credential narrower than an account, use temporary credentials.

Synopsis

dcloud iam access-keys create [flags]

Flags

  • --iam-user-idOptional

    string

    The ID of the IAM user the key signs in as; omitted: yourself

    Constraints: uuid

  • --expires-in-daysOptional

    number

    Days until the key expires; default the organization’s default (90), at most its maximum (365)

    Constraints: integer, 1-3650

  • --descriptionOptional

    string

    What the key is for

    Constraints: max 256 chars

  • --scope-policyOptional

    string

    Deprecated: a limit on the key (JSON policy document) that only narrows what the account may do and grants nothing. Still enforced when given. Instead: temporary credentials (s3 buckets temporary-key) for a narrower credential, or a service account with exactly the policy it needs (s3 buckets create-access-key)

    Constraints: max 10240 chars

  • --act-as-memberOptional

    boolean (--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 create

Generated from the API description, the same one the API checks requests against and the CLI is built from.