Identities
An account has two kinds of identity, and neither is how a person joins it. A user is a name minted inside the account, for a program or a shared runner. A role groups permissions and is assumed for temporary credentials. A person joins by invitation, which Give a teammate access covers.
Manage users
Section titled “Manage users”Create a user
Section titled “Create a user”A user has no address and no sign-in, so it is the right identity for a build runner or another program and the wrong one for a person:
deployport iam users create <username>Example:
deployport iam users create build-runnerThe user appears in deployport iam users list.
Manage roles
Section titled “Manage roles”A role is a collection of permissions that can be assumed by users or services to perform specific tasks. Unlike users, roles are not permanent identities - they provide temporary access to resources based on the policies attached to them. This makes roles ideal for applications, cross-service access, and situations where you need to grant specific permissions without sharing long-term credentials.
Create a role
Section titled “Create a role”Create a new role for grouping permissions:
deployport iam roles create <rolename>Example:
deployport iam roles create developer-accessThe role appears in deployport iam roles list.
Assume a role
Section titled “Assume a role”Role assumption allows users to temporarily gain the permissions of a role, providing secure access to resources without permanent credential assignment.
To assume a role and get temporary credentials with that role’s permissions:
deployport iam roles assume <role-name>Example:
deployport iam roles assume r1This will output a temporary Access Key ID and Secret Access Key that inherit the permissions of the assumed role. You can use these credentials in a terminal, from an app, or in SDKs.
apiVersion: deployport.com/v1kind: AssumedRoleContextmetadata: name: r1spec: accessKeyID: "<example>" secretAccessKey: "<example>" region: us-east-1I have role assumption credentials, how can I test or use them?
The quickest way is to use a separate profile in your local computer to test the credentials.
Say we want to name such profile temp-role, you could assume the role and configure it in another profile with a single command by piping deployport iam roles assume and deployport configure assume:
deployport iam roles assume r1 | deployport configure --profile=temp-role assumeThe temp-role profile on your machine now has the credentials assumed for the role.
export DEPLOYPORT_PROFILE=temp-role$env:DEPLOYPORT_PROFILE="temp-role"Now you can run any other deployport command and it will use your role credentials.
Best practices
Section titled “Best practices”- Invite people: a person joins by invitation, so what they may do is decided before they arrive
- Mint users for programs: a build runner or a shared tool gets a name inside the account
- Roles for temporary access: assume a role rather than handing out a long-lived key
- Meaningful names: use descriptive names that say what the identity is for
- Regular review: check what is still needed, and check what each policy is attached to