Connecting to Oracle Cloud Infrastructure (OCI)

The majority of Oracle Cloud deployments require connectivity to existing on-premises systems, applications, components and resources.

Usually, the purpose of the connection is to extend an existing on-premises network so that cloud resources can be reached and network traffic successfully routed.

The connectivity must be private, secure, resilient and meet both bandwidth and latency requirements.

In Oracle Cloud, there are two ways of delivering this connection;

This topic will highlight best practices associated with each of these methods.

What We Typically See

VPN connections are often used when customers are moving one or two non-critical workloads to OCI. This is usually part of a longer-term migration strategy. We recommend that these pilot applications are self-contained with limited integration points back to their on-premises environments.

Over some time, as confidence in the migration plan increases, a tipping point is often reached whereby moving to a dedicated connection is preferable. This is usually because the level of integration between cloud-based and on-premises based applications is high from a frequency, volume, or latency-sensitive perspective. The migration plan can heavily influence the time when this point is reached. In particular, the ability to migrate data-dependent applications together can have a significant bearing on when the tipping point is reached.

Take a look at the Migration Patterns topics for more information.

A dedicated connection may also be adopted early when a migration candidate is considered a critical application, particularly when consistent wide area network performance is a vital requirement.