diff --git a/en/aws/ec2/vpc-flow-logs-enabled.md b/en/aws/ec2/vpc-flow-logs-enabled.md
index 7e8312802..87112655f 100644
--- a/en/aws/ec2/vpc-flow-logs-enabled.md
+++ b/en/aws/ec2/vpc-flow-logs-enabled.md
@@ -15,16 +15,15 @@
 | **Recommended Action** | Enable VPC flow logs for each VPC |
 
 ## Detailed Remediation Steps
-1. Log into the AWS Management Console.
+1. Log in to the AWS Management Console.
 2. Select the "Services" option and search for VPC. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step2.png"/>
-3. Scroll down the left navigation panel and choose "Your VPC" under "VPC Dashboard". </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step3.png"/>
+3. Scroll down the left navigation panel and choose "Your VPCs" under "Virtual Private Cloud". </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step3.png"/>
 4. Select the "VPC" that needs to be verified for "VPC Flow Logs". </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step4.png"/>
-5. Scroll down the bottom dashboard panel and choose "Flow Logs" tab. If there are no flow logs then "You do not have any Flow Logs in this region" message will be displayed. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step5.png"/>
-6. Repeat steps number 2 - 6 to verify "Flow Logs" are enabled or not in other VPCs in the region. </br>
-7. Navigate to "VPC Dashboard" and choose "Your VPC" and click on the "Flow Logs" tab in the bottom dashboard panel.</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step7.png"/>
+5. Scroll down the bottom dashboard panel and choose "Flow Logs" tab. If there are no flow logs then "No flow logs found in this Region" message will be displayed. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step5.png"/>
+6. Repeat steps number 2 - 6 to verify whether "Flow Logs" are enabled or not for other VPCs in the remaining regions. </br>
+7. Navigate to "Your VPCs" in the left navigation panel, select the VPC and click on the "Flow Logs" tab in the bottom dashboard panel.</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step7.png"/>
 8. Click on the "Create flow log" button to create the "VPC Flow Logs". </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step8.png"/>
-9. In the "Create flow log" dialog box select the "Filter" from the dropdown menu that describes the type of traffic to be logged.</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step9.png"/>
-10. Select the destination to which the flow log data is to be published from the options.If the "S3 bucket" is selected for the log data to be published than provide the "S3 Bucket ARN" which is the ARN of the Amazon S3 bucket to which the flow log is published and click on the "Create" button at the bottom. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step10.png"/>
-11. If destination for the "flow log data" is selected as "Send to CloudWatch Logs" then enter the log destination in "Destination Group" which is the name of the "Amazon CloudWatch Logs" log group to which the flow log is published.</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step11.png"/>
-12. Select the "IAM role" that has permission to publish to the "Amazon CloudWatch Logs" log group and click on the "Create" button to make the necessary changes. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step12.png"/>
-13. Repeat steps number 7 - 12 to enable VPC flow logs for other "VPCs" in the region.</br>
+9. In the "Create flow log" dialog box select the "Filter" that describes the type of traffic to be logged and select the "Maximum aggregation interval".</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step9.png"/>
+10. Select the destination to which the flow log data is to be published from the options. If the "S3 bucket" is selected then provide the "S3 Bucket ARN" in which the flow log is to be published. Also select the "Log Record Format" & "Log File Format" along with the "Partition logs by time" and click on the "Create flow log" button at the bottom. </br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step10.png"/>
+11. If destination for the "flow log data" is selected as "Send to CloudWatch Logs" then enter the log destination in "Destination log group" which is the name of the "Amazon CloudWatch Logs" log group to which the flow log is published. Select the "IAM role" that has permission to publish to the "Amazon CloudWatch Logs" log group and specify the "Log record format". Then click on the "Create flow log" button to make the necessary changes.</br> <img src="/resources/aws/ec2/vpc-flow-logs-enabled/step11.png"/>
+12. Repeat steps number 7 - 11 to enable VPC flow logs for other "VPCs" in the region.</br>
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step10.png b/resources/aws/ec2/vpc-flow-logs-enabled/step10.png
index fa4462c95..5c5c07a74 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step10.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step10.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step11.png b/resources/aws/ec2/vpc-flow-logs-enabled/step11.png
index 37d7d68ea..a13315234 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step11.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step11.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step2.png b/resources/aws/ec2/vpc-flow-logs-enabled/step2.png
index 206fb5a22..62eafc16c 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step2.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step2.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step3.png b/resources/aws/ec2/vpc-flow-logs-enabled/step3.png
index 6216215f9..2031a1942 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step3.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step3.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step4.png b/resources/aws/ec2/vpc-flow-logs-enabled/step4.png
index a1a618d05..2bbe202be 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step4.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step4.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step5.png b/resources/aws/ec2/vpc-flow-logs-enabled/step5.png
index 8446d35bb..3dccd2177 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step5.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step5.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step7.png b/resources/aws/ec2/vpc-flow-logs-enabled/step7.png
index 2b5c2126e..4d87030ba 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step7.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step7.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step8.png b/resources/aws/ec2/vpc-flow-logs-enabled/step8.png
index 30ab58469..d4b702ef9 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step8.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step8.png differ
diff --git a/resources/aws/ec2/vpc-flow-logs-enabled/step9.png b/resources/aws/ec2/vpc-flow-logs-enabled/step9.png
index 12ef84b8d..8d8e8b4dd 100644
Binary files a/resources/aws/ec2/vpc-flow-logs-enabled/step9.png and b/resources/aws/ec2/vpc-flow-logs-enabled/step9.png differ