Tag every agent resource with an owner and environment, and enforce the tags
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 24 of 30: Tag every agent resource with an owner and environment, and enforce the tags. Untagged agent resources cannot be traced to an owner when something goes wrong. Tags also let policy and cost controls target agent resources specifically.
The whole checklist ยท The map
Why it matters
Untagged agent resources cannot be traced to an owner when something goes wrong. Tags also let policy and cost controls target agent resources specifically.
How, in each cloud
- AWS
- Attach tags to IAM entities and resources; AWS documents tags as the attributes for attribute-based access control.
- Google Cloud
- Attach tags, which are key-value pairs, to resources.
- Azure
- Use Azure Policy to govern tags.
What the documentation says
- "based on attributes. AWS calls these attributes tags . You" (source)
- "Tags are key-value pairs that you can attach to your" (source)
- "tags can be the basis for applying your business policies with Azure Policy" (source)
- Previous: Run agents in their own account, project or subscription
- Next: Test permission and policy changes in a dry run before enforcing them
Related pages
- Test permission and policy changes in a dry run before enforcing them: the check, and how in AWS, Google Cloud and Azure
- Remove the agent's identity and access when the agent is retired: the check, and how in AWS, Google Cloud and Azure
- Turn on organization-wide audit logging of control-plane actions: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-con, read 10 Nov 2026
- cloud.google.com/resource-manager/docs/tags/tags-overview, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/governance/policy/tutorials/govern-tags, read 10 Nov 2026
Last reviewed 16 Nov 2026.