diff --git a/README.md b/README.md
index 28a4e003354b24c068ce80490867a2d18177868a..1e9eb3da7ae58970b5a193bce4898a24f4570771 100644
--- a/README.md
+++ b/README.md
@@ -13,6 +13,7 @@
 * [Best Practices And Recommendations](./docs/best-practices/README.md)
 * [Integration Tutorials](./docs/tutorials/README.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)
 * [Get Help](./get-help.md)
 
diff --git a/docs/ei-secure-agent.md b/docs/ei-secure-agent.md
new file mode 100644
index 0000000000000000000000000000000000000000..0708d41b32f61df1454d39101809fb29985c0ce7
--- /dev/null
+++ b/docs/ei-secure-agent.md
@@ -0,0 +1,20 @@
+# 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 permenant 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).
+
+
+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:
+| Org        | IP address |
+| -----------|-------------|
+| test      | 3.230.240.5|
+| prod      | 3.19.12.147|
diff --git a/docs/secure-agent.md b/docs/secure-agent.md
index b723b9dc8130e8444fc984116872a7c6486174da..830dd1bdf40ccb275c9ee370bfc2af38e834c470 100644
--- a/docs/secure-agent.md
+++ b/docs/secure-agent.md
@@ -1,6 +1,7 @@
 # Table of Contents
 
 - [Secure Agents](#secure-agents)
+- [he EI Secure Agent](#the-ei-secure-agent)
 - [Costs](#costs)
 - [Responsibilities](#responsibilities)
 - [Recommendations](#recommendations)
@@ -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 
 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
 
 Secure Agents are licensed at a per-Secure-Agent rate.