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
Section titled “Access keys”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 access keys
Section titled “Generate access keys”Generate an access key for a user:
deployport iam users access-keys generate --username <username>Example:
deployport iam users access-keys generate --username build-runnerThe 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:
deployport configure --profile build-runner -i <ACCESS_KEY_ID> -k <SECRET_ACCESS_KEY> -r <region>deployport iam users list --profile build-runnerA refusal means the user has no policy that allows the action yet, which is Access denied’s first entry.
Temporary keys
Section titled “Temporary keys”Temporary keys are short-lived credentials that expire on their own. They come from assuming a role.
Assume a role
Section titled “Assume a role”deployport iam roles assume <role-name>Example:
deployport iam roles assume r1Set a custom duration
Section titled “Set a custom duration”Set the duration the temporary credentials last for:
deployport iam roles assume <role-name> --duration <duration>Example:
# Assume role for 15 minutesdeployport iam roles assume r1 --duration 15mBest practices
Section titled “Best practices”When to use each method
Section titled “When to use each method”- Access keys: use for long-running applications that need consistent access
- Temporary keys: prefer for short-term access, CI/CD pipelines, and human users
Security considerations
Section titled “Security considerations”- 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