Skip to content
Snippets Groups Projects

Update `README` instructions on how to access Secure Agent's file system - WISCALERTS-2

Merged Nuwan Rajika Kumarasiri requested to merge docs into master
1 file
+ 4
2
Compare changes
  • Side-by-side
  • Inline
+ 4
2
@@ -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
Loading