Skip to content

Access keys

An application, a script or a CI job reaches Deployport with a key rather than a browser sign-in. An access key does not expire on its own. A temporary key comes from assuming a role and expires by itself.

Access keys are long-term credentials for programmatic access to the Deployport APIs. They consist of an Access Key ID and Secret Access Key pair.

Generate an access key for a user:

Terminal window
deployport iam users access-keys generate --username <username>

Example:

Terminal window
deployport iam users access-keys generate --username build-runner

The command prints the Access Key ID and the Secret Access Key.

Verify. The key is live when a command signed with it answers. Give it a profile of its own, then run something the user is allowed to do:

Terminal window
deployport configure --profile build-runner -i <ACCESS_KEY_ID> -k <SECRET_ACCESS_KEY> -r <region>
deployport iam users list --profile build-runner

A refusal means the user has no policy that allows the action yet, which is Access denied’s first entry.

Temporary keys are short-lived credentials that expire on their own. They come from assuming a role.

Terminal window
deployport iam roles assume <role-name>

Example:

Terminal window
deployport iam roles assume r1

Set the duration the temporary credentials last for:

Terminal window
deployport iam roles assume <role-name> --duration <duration>

Example:

Terminal window
# Assume role for 15 minutes
deployport iam roles assume r1 --duration 15m
  • Access keys: use for long-running applications that need consistent access
  • Temporary keys: prefer for short-term access, CI/CD pipelines, and human users
  • Principle of least privilege: grant only the permissions the caller needs
  • Monitor usage: keep logs of credential usage and access patterns
  • Never store in code: use environment variables or a secure credential store