Run agents in their own account, project or subscription
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 23 of 30: Run agents in their own account, project or subscription. Agents placed beside production workloads share their blast radius, quotas and admin rights. A dedicated container lets you apply stricter policy and limits and remove it cleanly.
The whole checklist ยท The map
Why it matters
Agents placed beside production workloads share their blast radius, quotas and admin rights. A dedicated container lets you apply stricter policy and limits and remove it cleanly.
How, in each cloud
- AWS
- Use separate AWS accounts to isolate workloads.
- Google Cloud
- Use a separate project, grouped under folders in the resource hierarchy.
- Azure
- Use a separate subscription, grouped under management groups.
What the documentation says
- "Using multiple AWS accounts to help isolate and manage your business" (source)
- "projects. Structuring your resources this way helps you centralize asset" (source)
- "Subscriptions are a unit of management, billing, and scale within Azure." (source)
- Previous: Decide for each tool whether the action runs with the agent's authority or the signed-in user's
- Next: Tag every agent resource with an owner and environment, and enforce the tags
Related pages
- Tag every agent resource with an owner and environment, and enforce the tags: the check, and how in AWS, Google Cloud and Azure
- 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
Sources
- docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizin, read 10 Nov 2026
- cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/desi, read 10 Nov 2026
Last reviewed 16 Nov 2026.