AWS solutions documentation change
Summary
Updated 'solution' to 'Guidance' terminology in performance context
Security assessment
Purely terminological changes in performance considerations section. No security implications or documentation additions related to security features.
Diff
diff --git a/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/performance-considerations.md b/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/performance-considerations.md index 163265afa..2201d3f6a 100644 --- a//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/performance-considerations.md +++ b//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/performance-considerations.md @@ -20 +20 @@ For memory acquisition, memory investigation, and disk investigation SSM documen -The investigation instance mount volume must always be greater than the memory of the compromised instance. This ensures that memory loaded into investigation instance does not error out. The solution uses `M5.2Xlarge` Amazon EC2 instance type by default. +The investigation instance mount volume must always be greater than the memory of the compromised instance. This ensures that memory loaded into investigation instance does not error out. The Guidance uses `M5.2Xlarge` Amazon EC2 instance type by default. @@ -30 +30 @@ Sample AppSync API to query forensic details -AWS services used in this solution +AWS services used in this Guidance