From 7f51dd12472a6b267ac1275547ce2da6d7154c57 Mon Sep 17 00:00:00 2001
From: Nuwan Rajika Kumarasiri <nuwan.kumarasiri@wisc.edu>
Date: Tue, 10 Mar 2020 12:32:56 -0500
Subject: [PATCH] Update `README` instructions on how to access Secure Agent's
 file system - WISCALERTS-2

---
 README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index e746170..a1dad55 100644
--- a/README.md
+++ b/README.md
@@ -170,6 +170,8 @@ and `container_memory` variables can be used to adjust these values. See [variab
 ### EFS Mounting, Accessing Secure Agent Configurations, Logs and Additional Debugging
 * Above terraform configuration creates a EFS file system that is used by the container to persist Secure Agent configurations 
 and logs files.
-* In order to access Secure Agent log files and configurations files use the instructions documented in 
-`Settings` in created EFS file system under `File system access` in AWS console.
+* One way to access Secure Agent's log files and configurations files is to mount the EFS file system use by Secure Agent. 
+EFS file system is accessible from any instance within `test` and `prod` tiers. Start an EC2 instance in `test-tier` VPC
+(or in prod VPC - `prod-tier `) and this instance can be used to mount the EFS file system (be sure to that this EC2 instance can be accessed from SSH). 
+Then use the instructions documented in `Settings` in Secure Agent's EFS file system(`iics-secure-agent`) under `File system access` in AWS console.
 * If there's a requirement to log into EC2 instance that runs the container, [AWS Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html) can be [used](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-quick-setup.html). 
\ No newline at end of file
-- 
GitLab