From a3c2224d4ef7000b4cbd0efa627acd4e88c8be68 Mon Sep 17 00:00:00 2001 From: Jared Balkman <jared.balkman@wisc.edu> Date: Wed, 21 Jun 2023 10:46:11 -0500 Subject: [PATCH] Update docs/secure-agent.md, docs/ei-secure-agent.md --- docs/ei-secure-agent.md | 8 ++++---- docs/secure-agent.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/ei-secure-agent.md b/docs/ei-secure-agent.md index 0708d41..04c3316 100644 --- a/docs/ei-secure-agent.md +++ b/docs/ei-secure-agent.md @@ -4,16 +4,16 @@ The EI Secure Agents are the specific secure agents that are used by most users ## General Information -The EI Secure Agents are the two agents named ei.secureagent.doit.wisc.edu, located in the standard Test and Prod orgs of IICS. The agents can be used by any user of the org, and is the most commonly used agent within the org. Each agent is located on a priavte EC2 instance so files can only be accessed through IICS functionality. In addition, any files hosted on the secure agent are potentially visible to any user of the secure agent. If privacy is a requirement, consider hosting any permenant files on external sources such as an Amazon S3 bucket. +The EI Secure Agents are the two agents named ei.secureagent.doit.wisc.edu, located in the standard Test and Prod orgs of IICS. The agents can be used by any user of the org, and is the most commonly used agent within the org. Each agent is located on a priavte EC2 instance so files can only be accessed through IICS functionality. In addition, any files hosted on the secure agent are potentially visible to any user of the secure agent. If privacy is a requirement, consider hosting any permanent files on external sources such as an Amazon S3 bucket. ## Technical Information -The EI Secure Agents are deployed in a docker container on two seperate AWS EC2 instances in private subnets. A gitlab repo of the dockerfiles and terraform used to deploy the agent can be found at [This Repositiory](https://git.doit.wisc.edu/interop/iics/iics_secure_agent). +The EI Secure Agents are deployed in a docker container on two separate AWS EC2 instances in private subnets. A gitlab repo of the dockerfiles and terraform used to deploy the agent can be found at [This Repositiory](https://git.doit.wisc.edu/interop/iics/iics_secure_agent). -Due to the nature of a Docker container, files on the secure agents may be volatile, and if the secure agent restarts the file may be lost. If your integration needs to have non-volatile flat files, contact the integration team at integration-platform@doit.wisc.edu +Due to the nature of a Docker container, files on the secure agents may be volatile, and if the secure agent restarts the file may be lost. If your integration needs to have non-volatile flat files, contact the Integration Team at integration-platform@doit.wisc.edu -The IP adresses of the Secure Agents (to be used for whitelisting database/server connections) are as follows: +The IP adresses of the Secure Agents (to be used for allowlisting database/server connections) are as follows: | Org | IP address | | -----------|-------------| | test | 3.230.240.5| diff --git a/docs/secure-agent.md b/docs/secure-agent.md index 830dd1b..02210a2 100644 --- a/docs/secure-agent.md +++ b/docs/secure-agent.md @@ -1,7 +1,7 @@ # Table of Contents - [Secure Agents](#secure-agents) -- [he EI Secure Agent](#the-ei-secure-agent) +- [The EI Secure Agent](#the-ei-secure-agent) - [Costs](#costs) - [Responsibilities](#responsibilities) - [Recommendations](#recommendations) -- GitLab