AWS securityagent documentation change
Summary
Updated IAM Identity Center region requirements from requiring US East (N. Virginia) to allowing any region where the Agent Space is created
Security assessment
This change removes the hard requirement for IAM Identity Center to be enabled in us-east-1 and allows it to be in the same region as the Agent Space. This appears to be a flexibility improvement rather than a security fix. There is no evidence of a security vulnerability being addressed.
Diff
diff --git a/securityagent/latest/userguide/setup-security-agent.md b/securityagent/latest/userguide/setup-security-agent.md index 1c3fff978..f68c38a27 100644 --- a//securityagent/latest/userguide/setup-security-agent.md +++ b//securityagent/latest/userguide/setup-security-agent.md @@ -120 +120 @@ Complete these steps only if you selected IAM Identity Center (SSO) as your acce -Your application must be configured in the same Region where you enable IAM Identity Center. The displayed Region is where your Agent Space will be created. IAM Identity Center must be enabled in US East (N. Virginia) `us-east-1`. +Your application must be configured in the same Region where you enable IAM Identity Center. The displayed Region is where your Agent Space will be created. IAM Identity Center must be enabled in the same Region where you create your Agent Space. @@ -126 +126 @@ Your application must be configured in the same Region where you enable IAM Iden - * If an organization instance already exists in US East (N. Virginia) `us-east-1`, AWS Security Agent will automatically connect to it + * If an organization instance already exists in the same Region, AWS Security Agent will automatically connect to it