Outbound IP Addresses of EPM Cloud Data Centers and Regions
When you setup IP allowlist for an Oracle Enterprise Performance Management Cloud environment, you permit connections only from those specific IP addresses. In this scenario, requesting access from another EPM Cloud environment will not work unless you add to the IP allowlist the outbound IP addresses of the data center or region where the requesting environment is located. For example, if you are executing EPM Automate copySnapshotFromInstance command from an environment that has IP allowlist configured, the outbound IP addresses of the data center or region where the source environment is located must be added to the allowlist. The same is true for Copy Application Snapshot REST API, Clone Environment screen in Migration, cloneEnvironment EPM Automate command and REST API, and Navigation Flows.
Similarly, if you setup IP allowlist on a Fusion or NetSuite environment and want to establish connections from an EPM Cloud environment, you must update the IP allowlist in Fusion or NetSuite environment to include the outbound IP addresses of the data center or region where EPM Cloud environment is located.
Outboud IP Addresses of Classic Data Centers
Add the appropriate CIDR from the following table to the allowlist of the environment that receives the connections if the source environment is in a Classic data center:
Table 2-4 Outboud IP Addresses of Classic Data Centers
| Data Center | Outbound IP Address |
|---|---|
| Chessington (EM007/UK-Gov DR) | 141.145.79.48/29 |
| Chicago (US8/US-Gov) | 129.152.95.48/29 |
| Slough (EM006/UK-Gov) | 141.145.63.48/29 |
| Sterling (US009/US-Gov DR) | 129.157.31.48/29 |
Outgoing IP Address of OCI Regions for Communication within a Region
Add the CIDR 240.0.0.0/4 to the allowlist to enable communication if both environments are in the same OCI region. For example, if an environment in us-phoenix-1 region is IP allowlist-enabled, you must add 240.0.0.0/4 to the allowlist to accept requests from other environments in the us-phoenix-1 region.
Outbound IP Addresses of OCI (Gen 2) Regions for Communication Between Regions
If your allowlist-enabled environment needs to communicate with another environment in a different region, add the appropriate IP address from the following to the allowlist to enable communication. For example, if an allowlist-enabled environment in the us-phoenix-1 region has to accept a request from an environment in the us-ashburn-1 region, the allowlist-enabled environment (in us-phoenix-1 region) must add 130.35.200.71 to the IP allowlist.
Table 2-5 Outbound IP Addresses of OCI (Gen 2) Regions for Communication Between Regions
| Region | Outbound IP Address |
|---|---|
| ap-hyderabad-1 | 129.148.134.207 |
| ap-mumbai-1 | 192.29.168.100 |
| ap-melbourne-1 | 192.29.211.116 |
| ap-sydney-1 | 192.29.144.23 |
| ap-osaka-1 | 192.29.248.174 |
| ap-tokyo-1 | 192.29.39.186 |
| ap-singapore-1 | 129.148.184.87 |
| ap-seoul-1 | 192.29.22.211 |
| ca-montreal-1 | 192.29.89.100 |
| ca-toronto-1 | 192.29.14.16 |
| eu-amsterdam-1 | 192.29.192.117 |
| eu-amsterdam-1 (EURA EU001) | 192.29.193.58 |
| eu-frankfurt-1 | 138.1.45.186 |
| eu-frankfurt-1 (EURA EU001) | 138.1.46.106 |
| eu-madrid-1 | 155.248.138.168 |
| eu-milan-1 | 129.149.115.202 |
| eu-paris-1 | 155.248.132.129 |
| eu-stockholm-1 | 129.149.83.6 |
| eu-zurich-1 | 192.29.181.180 |
| me-abudhabi-1 | 129.149.51.122 |
| me-dubai-1 | 129.148.210.32 |
| me-jeddah-1 | 192.29.117.179 |
| sa-santiago-1 | 129.148.153.178 |
| mx-queretaro-1 | 155.248.147.134 |
| sa-saopaulo-1 | 192.29.142.211 |
| sa-vinhedo-1 | 129.153.241.235 |
| uk-london-1 | 147.154.230.60 |
| uk-cardiff-1 | 129.148.207.125 |
| us-ashburn-1 | 130.35.200.71 |
| us-phoenix-1 | 130.35.2.158 |
| us-sanjose-1 | 204.216.121.98 |