Skip to main content
Telnyx IAM uses the same ideas as AWS IAM, so most of its vocabulary maps one to one. The deliberate difference is the role. A Telnyx role is a set of permissions a principal holds, never an identity anyone assumes.

Vocabulary

No Assuming Roles

An AWS principal assumes a role to work with that role’s permissions for a while. A Telnyx principal holds its roles all the time, through grants, and every request is decided on them. The jobs that assuming a role does in AWS have their own tools.
  • Preview A workload outside Telnyx, such as a CI job, trades its own token for a one-hour token of a service account.
  • Preview A person who works in a customer’s organization does it as themselves, through a delegation that names them with a role.
  • Preview An API key that needs less than its user holds carries a scope. A job that needs less gets a service account of its own.

Evaluation

Requests are decided the way AWS decides them. Nothing is allowed by default, an allow in any granted role is enough, and an explicit deny wins over any allow. Preview An API key’s scope and the organization’s guardrails narrow the result the way session policies, permission boundaries, and service control policies do. See Evaluation Sequence.