Whitelisting IP Address

Whitelist with Oracle any public IP addresses that you want to expose. You can advertise public or private IP addresses over the connection based on whether you establish a public or private peering session. Whitelisting is required for some Oracle Cloud services or services that support instances. You can add your own Internet Protocol (IP) whitelist and blacklist rules, and activate the firewall for Oracle Cloud services.

Perform the following tasks depending on the type of connection and NATing provided by the selected connection type.
  • If you are connecting using Direct Cross Connects, whitelist any IP addresses that you want to advertise over the connection.

  • If you are connecting through an Oracle FastConnect Partner, complete the following:

    • If your Oracle FastConnect Partner is NATing your IP addresses, whitelist the single, permanent /32 address or NAT pool prefix allocated to you by the partner. For more information, contact your FastConnect partner account manager.

    • If you are source NATing your IP addresses, whitelist the public IP addresses that you will be advertising to Oracle. This includes the IP prefixes you’ll use to NAT your private IP addresses.

    • Whitelist any IP addresses you want your FastConnect partner to advertise to Oracle so that you can initiate connections from Oracle towards your network.

  • Ensure that you update the relevant Oracle Cloud service firewalls to permit traffic from the IP addresses that will be the source IP for the traffic.

To whitelist the IP addresses, follow the procedure that you use to whitelist an IP address for your Oracle Cloud services. See Managing Internet Protocol Whitelist and Blacklist Rules in Managing and Monitoring Oracle Cloud.

Note:

If the Firewall tile is not visible in Infrastructure Classic Console, file a service request with My Oracle Support and specify the IP address that you want to whitelist.

Before using the connection for the first time, you must verify that data packets are being routed correctly. See Testing Your Connection.