Lesson 5 of 7 · About 4 minutes

Give applications their own identity

Learn the concept.

An application may need cloud access even when no person is signing in. A workload identity gives that application its own permissions instead of borrowing a developer’s credentials.

Separate the actors

Use an identity for the service so its permissions and activity can be managed independently of a person’s account.

Prefer temporary credentials

Where supported, use roles or workload identity mechanisms that issue short-lived credentials. Avoid embedding a personal access key in a deployment.

Limit both trust and permissions

Specify which workload may use the identity, and what that identity may do. Temporary credentials can still be too powerful if their permissions are broad.

Field example05 / A

Put it in context

A fictional nightly report job needs to read one storage location and write one output. The team assigns a narrowly scoped role to the job. When a developer leaves, the job does not depend on that developer’s personal key. Its access can be reviewed separately.

SEE THE IDEA

Give the job its own access

Fictional nightly reporting workload.

  1. Approved workload

    Trust policy or equivalent identifies which job may use the role.

  2. Workload role

    Issues scoped, temporary credentials where supported.

  3. Required resources

    Read one input location and write one output.

The developer’s personal key is not part of this design. Identity trust and resource permissions both matter.
Read the visualWhat if the credentials expire quickly but can administer everything?

The permissions are still too broad. Limit the workload’s allowed actions and resources.

Make a decision.

Use what you just learned. A correct answer lets you save this lesson to your progress.

Take this with you.

Give the workload an identity, a limited job, and a limited permission set.

YOUR LEARNING SPACE