## TL;DR

Keep the secret out of code and pass it via environment variables. Rotate keys per service instead of globally.

## Steps

1. Create one access key per service with the minimum permission level, and name keys after the workload. Rotate keys per service instead of globally. Keep the secret out of code and pass it via environment variables.

## When to use

You are seeing this: Create one access key per service with the minimum permission level, and name keys after the workload. Use this skill when you run into "Tigris access keys carry permission levels; scope them per workload".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
