Outbound IP Addresses of Cloud EPM Regions
When you setup network perimeter for an Oracle Fusion Cloud Enterprise Performance Management
environment, you permit connections only from those specific IP addresses. In this
scenario, requesting access from another Cloud EPM environment will not work
unless you add to the network perimeter the outbound IP addresses of the region where
the requesting environment is located. For example, if you are executing EPM Automate
copySnapshotFromInstance command from an environment that has network
perimeter configured, the outbound IP addresses of the region where the source
environment is located must be added to the network perimeter. The same is true for the
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 a Cloud EPM environment, you must update the IP allowlist in Fusion or NetSuite environment to include the outbound IP addresses of the region where Cloud EPM environment is located.
Outgoing IP Address for Communication within a Region
Add the CIDR 240.0.0.0/4 to the network perimeter to enable communication if both environments are in the same OCI region. For example, if an environment in us-phoenix-1 region is network perimeter-enabled, you must add 240.0.0.0/4 to the network perimeter to accept requests from other environments in the us-phoenix-1 region.
Outbound IP Addresses for Communication Between Regions
If your network perimeter-enabled environment needs to communicate with another environment in a different region, add the appropriate IP address from the following to the network perimeter to enable communication. For example, if a network perimeter-enabled environment in the us-phoenix-1 region has to accept a request from an environment in the us-ashburn-1 region, the network perimeter-enabled environment (in us-phoenix-1 region) must add 130.35.200.71 to the network perimeter.
Table 2-4 Outbound IP Addresses for Communication Between Regions
| Region | Outbound IP Address |
|---|---|
| af-johannesburg-1 | 129.149.65.8 |
| 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-singapore-2 | 217.142.162.74 |
| 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 | 192.29.193.58 |
| eu-frankfurt-1 | 138.1.45.186 |
| eu-frankfurt-1-eura | 138.1.46.106 |
| eu-frankfurt-2 | 209.196.5.62 |
| eu-madrid-1 | 155.248.138.168 |
| eu-madrid-2 | 209.196.41.3 |
| eu-marseille-1 | 129.149.98.71 |
| 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-abudhabi-2 | 84.8.180.214 |
| me-abudhabi-4 | 79.72.116.82 |
| me-dubai-1 | 129.148.210.32 |
| me-dcc-doha-1 | 213.35.68.127 |
| me-dcc-muscat-1 | 151.104.140.88 |
| me-jeddah-1 | 192.29.117.179 |
| me-riyadh-1 | 84.8.65.29 |
| sa-santiago-1 | 129.148.153.178 |
| mx-monterrey-1 | 139.177.104.208 |
| mx-queretaro-1 | 155.248.147.134 |
| sa-bogota-1 | 158.247.96.191 |
| sa-saopaulo-1 | 192.29.142.211 |
| sa-valparaiso-1 | 165.1.97.22 |
| sa-vinhedo-1 | 129.153.241.235 |
| uk-cardiff-1 | 129.148.207.125 |
| uk-london-1 | 147.154.230.60 |
| uk-gov-cardiff-1 | 81.208.185.130 |
| uk-gov-london-1 | 138.2.254.52 |
| us-ashburn-1 | 130.35.200.71 |
| us-chicago-1 | 131.186.8.162 |
| us-phoenix-1 | 130.35.2.158 |
| us-sanjose-1 | 204.216.121.98 |
| us-luke-1 | 155.248.27.160 |
| us-langley-1 | 155.248.14.132 |
| us-gov-ashburn-1 | 155.248.75.1 |
| us-gov-chicago-1 | 155.248.111.216 |
| us-gov-phoenix-1 | 155.248.95.157 |