AWS Security ChangesHomeSearch

AWS solutions documentation change

Service: solutions · 2025-06-28 · Documentation low

File: solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/deployment-overview.md

Summary

Formatting changes including hyphen normalization, code indentation fixes, command syntax corrections, and step numbering adjustments. Updated git clone URL format and removed underscores around account parameters in CDK commands.

Security assessment

Changes are primarily formatting improvements and documentation clarity updates. No security vulnerabilities or security feature additions are mentioned. Modifications to CDK command parameters appear to be syntax corrections rather than security-related changes.

Diff

diff --git a/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/deployment-overview.md b/solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/deployment-overview.md
index f09ef2fd3..78ce11df8 100644
--- a//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/deployment-overview.md
+++ b//solutions/latest/automated-forensics-orchestrator-for-amazon-ec2/deployment-overview.md
@@ -13 +13 @@ The Guidance is deployed in the following three AWS accounts:
-  1. Forensic AWS account – Core Guidance components to perform forensics orchestration 
+  1. Forensic AWS account - Core Guidance components to perform forensics orchestration
@@ -15 +15 @@ The Guidance is deployed in the following three AWS accounts:
-  2. Security Hub AWS account – Configure events and custom actions to trigger forensic orchestration flow 
+  2. Security Hub AWS account - Configure events and custom actions to trigger forensic orchestration flow
@@ -17 +17 @@ The Guidance is deployed in the following three AWS accounts:
-  3. Application AWS account – IAM roles needed to establish trust between Forensic AWS account and Application AWS account 
+  3. Application AWS account - IAM roles needed to establish trust between Forensic AWS account and Application AWS account
@@ -41 +41 @@ The following steps deploy the Forensics Orchestrator AWS Step Functions, AWS La
-  1. In your terminal, clone the Guidance's source code from the [GitHub repository](https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2). 
+  1. In your terminal, clone the Guidance’s source code from the [GitHub repository](https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2).
@@ -43 +43 @@ The following steps deploy the Forensics Orchestrator AWS Step Functions, AWS La
-        git clone https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2.git
+        git clone link:https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2.git
@@ -54,4 +54,4 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-                "isExistingVPC": true,
-                "vpcID": "vpc-1234567890"
-                "enableVPCEndpoints": false,
-                "enableVpcFlowLog": false
+                "isExistingVPC": true,
+                "vpcID": "vpc-1234567890"
+                "enableVPCEndpoints": false,
+                "enableVpcFlowLog": false
@@ -68 +72,0 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-        export AWS_REGION=<Your Region – us-east-1>
@@ -70 +74,3 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  4. Install the required NPM libraries. 
+    export AWS_REGION=<Your Region - us-east-1>
+
+  1. Install the required NPM libraries.
@@ -74 +80 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  5. Compile and build AWS Lambda functions. 
+  2. Compile and build AWS Lambda functions.
@@ -78 +84 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  6. Build the forensics AWS CloudFormation stack to be deployed in the forensic AWS account. 
+  3. Build the forensics AWS CloudFormation stack to be deployed in the forensic AWS account.
@@ -80 +86 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-        cdk synth -c account=<Forensic AWS Account Number> -c region=<Region> -c sechubaccount=<Security Hub Aggregator Account Number> -c STACK_BUILD_TARGET_ACCT=forensicAccount
+        cdk synth -c account=<Forensic AWS Account Number> -c region=<Region> -c sechubaccount=<Security Hub Aggregator Account Number> -c STACK_BUILD_TARGET_ACCT=forensicAccount
@@ -86 +92 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  7. Deploy the forensics stack in the forensic AWS account.
+  4. Deploy the forensics stack in the forensic AWS account.
@@ -88 +94 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-        cdk deploy --all -c account=_< Forensic AWS Account Number>_ -c region=<Region> --require-approval=never -c sechubaccount=_< Security Hub Aggregator AWS Account Number>_ -c STACK_BUILD_TARGET_ACCT=forensicAccount 
+        cdk deploy --all -c account=<Forensic AWS Account Number> -c region=<Region> --require-approval=never -c sechubaccount=<Security Hub Aggregator AWS Account Number> -c STACK_BUILD_TARGET_ACCT=forensicAccount
@@ -107 +113 @@ If you are reusing the existing downloaded code delete the `cdk.out` folder.
-        git clone https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2.git
+        git clone link:https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2.git
@@ -120,4 +126,4 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-                "isExistingVPC": true,
-                "vpcID": "vpc-1234567890"
-                "enableVPCEndpoints": false,
-                "enableVpcFlowLog": false
+                "isExistingVPC": true,
+                "vpcID": "vpc-1234567890"
+                "enableVPCEndpoints": false,
+                "enableVpcFlowLog": false
@@ -134 +144,0 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-        export AWS_REGION=<Your Region –us-east-1>
@@ -136 +146,3 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  5. Install the required NPM libraries. 
+    export AWS_REGION=<Your Region -us-east-1>
+
+  1. Install the required NPM libraries.
@@ -140 +152 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  6. Compile and build AWS Lambda functions. 
+  2. Compile and build AWS Lambda functions.
@@ -144 +156 @@ To deploy into existing VPC update `cdk.json` to configure **isExistingVPC** to
-  7. Build the forensics Security Hub AWS CloudFormation stack to be deployed in Security Hub aggregator account. 
+  3. Build the forensics Security Hub AWS CloudFormation stack to be deployed in Security Hub aggregator account.
@@ -152 +164 @@ Example:
-  8. Deploy the forensics Security Hub stack in the Security Hub aggregator account. 
+  4. Deploy the forensics Security Hub stack in the Security Hub aggregator account.
@@ -165 +177 @@ Example:
-  1. Download the [`cross-account-role.yml`](https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2/blob/main/source/deployment-prerequisties/cross-account-role.yml) file to your local hard drive. 
+  1. Download the [cross-account-role.yml](https://github.com/aws-solutions-library-samples/automated-forensic-orchestrator-for-amazon-ec2/blob/main/source/deployment-prerequisties/cross-account-role.yml) file to your local hard drive.
@@ -182 +194 @@ Prerequisites
-Support for Red Hat Enterprise Linux (RHEL) 8.6 and above
+Support for Red Hat Enterprise Linux (RHEL 8.6 and above)