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.

Context: Official docs (Tigris): access keys are created with permission levels such as Editor, and guides call for ReadWrite permissions scoped to the bucket in use. Agents that mint one admin-level key and share it across every service lose the ability to revoke per workload. Create a named key per app with only the permissions it needs.

## Matched source
Source: Published skill
Original query: "Tigris access keys carry permission levels; scope them per workload"
Key terms: access, carry, keys, levels, permission, scope, them, tigris, workload
