Skip to content
Snippets Groups Projects
Commit 3bdbdc92 authored by SAM CARPENTER's avatar SAM CARPENTER
Browse files

Merge branch 'ei-secure-agent-branch' into 'master'

EI Secure Agent Documentation First Pass

See merge request !64
parents 309cf503 a3c2224d
No related branches found
No related tags found
1 merge request!64EI Secure Agent Documentation First Pass
...@@ -13,6 +13,7 @@ ...@@ -13,6 +13,7 @@
* [Best Practices And Recommendations](./docs/best-practices/README.md) * [Best Practices And Recommendations](./docs/best-practices/README.md)
* [Integration Tutorials](./docs/tutorials/README.md) * [Integration Tutorials](./docs/tutorials/README.md)
* [Secure Agents](./docs/secure-agent.md) * [Secure Agents](./docs/secure-agent.md)
* [EI Secure Agent](./docs/ei-secure-agent.md)
* [Shared Orgs and Sub Orgs](./docs/shared-org-vs-sub-org.md) * [Shared Orgs and Sub Orgs](./docs/shared-org-vs-sub-org.md)
* [Get Help](./get-help.md) * [Get Help](./get-help.md)
......
# EI Secure Agents
The EI Secure Agents are the specific secure agents that are used by most users of the UW Madison ecosystem. For more generalized information about secure agents and their standard implementation, please refer to [This Page](docs/secure-agent.md).
## 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 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 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
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|
| prod | 3.19.12.147|
# Table of Contents # Table of Contents
- [Secure Agents](#secure-agents) - [Secure Agents](#secure-agents)
- [The EI Secure Agent](#the-ei-secure-agent)
- [Costs](#costs) - [Costs](#costs)
- [Responsibilities](#responsibilities) - [Responsibilities](#responsibilities)
- [Recommendations](#recommendations) - [Recommendations](#recommendations)
...@@ -13,6 +14,10 @@ ...@@ -13,6 +14,10 @@
A Secure Agent is a Java program that runs integration tasks and enables secure communication across the firewall between our organization and A Secure Agent is a Java program that runs integration tasks and enables secure communication across the firewall between our organization and
IICS. More details can be found [here](https://docs.informatica.com/integration-cloud/cloud-platform/current-version/runtime-environments/secure-agents.html). IICS. More details can be found [here](https://docs.informatica.com/integration-cloud/cloud-platform/current-version/runtime-environments/secure-agents.html).
## The EI Secure Agent
UW Madison hosts Secure Agents for each of their orgs which are available to use. More Information about them can be found [At This Page](docs/ei-secure-agent.md).
## Costs ## Costs
Secure Agents are licensed at a per-Secure-Agent rate. Secure Agents are licensed at a per-Secure-Agent rate.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment