AWS securityagent documentation change
Summary
Added note clarifying cross-account penetration testing support limitations for shared VPC resources and authentication credential requirements.
Security assessment
Documents security constraints for cross-account testing scenarios, specifically regarding resource sharing boundaries and credential management. Enhances security feature documentation.
Diff
diff --git a/securityagent/latest/userguide/connect-agent-vpc.md b/securityagent/latest/userguide/connect-agent-vpc.md index 4fbbd2c8e..7e5cdeb7f 100644 --- a//securityagent/latest/userguide/connect-agent-vpc.md +++ b//securityagent/latest/userguide/connect-agent-vpc.md @@ -56,0 +57,4 @@ You can add up to 5 VPCs. +###### Note + +Cross-account penetration testing is currently supported for VPC resources (subnets and security groups) shared using AWS Resource Access Manager. Secrets Manager secrets and Lambda functions used for authentication credentials must be configured in the same AWS account as your AWS Security Agent setup. +