AWS devopsagent documentation change
Summary
Corrected terminology from 'auto roll creation' to 'automatic role creation'
Security assessment
Typo fix clarifies IAM role automation without changing security meaning. No evidence of vulnerability remediation or new security guidance.
Diff
diff --git a/devopsagent/latest/userguide/about-aws-devops-agent-what-are-devops-agent-spaces.md b/devopsagent/latest/userguide/about-aws-devops-agent-what-are-devops-agent-spaces.md index cf4fe97f1..dee2152e2 100644 --- a//devopsagent/latest/userguide/about-aws-devops-agent-what-are-devops-agent-spaces.md +++ b//devopsagent/latest/userguide/about-aws-devops-agent-what-are-devops-agent-spaces.md @@ -49 +49 @@ Consider creating multiple Agent Spaces to support different organizational need - __When creating multiple Agent Spaces, you can use a dedicated AWS account as the primary account for an Agent Space and connect distinct application accounts as secondary accounts. This approach allows you to maintain granular access controls while ensuring that each Agent Space can access only the resources specific to its intended scope, even when using auto roll creation. + __When creating multiple Agent Spaces, you can use a dedicated AWS account as the primary account for an Agent Space and connect distinct application accounts as secondary accounts. This approach allows you to maintain granular access controls while ensuring that each Agent Space can access only the resources specific to its intended scope, even when using automatic role creation.