Why This Matters

Prior to this update, OCM created a temporary Virtual Cloud Network (VCN) and subnet in your tenancy to perform replication. While effective for many workloads, this approach did not satisfy the needs of customers who operate in tightly controlled or highly regulated environments. These customers often require that:

  • Outbound internet access be restricted
  • New subnets or network segments be centrally approved
  • All incoming and outgoing traffic flow through trusted, private routes
  • Migration tooling integrate cleanly with existing security controls

The new private network option removes these limitations and allows replication to occur entirely over your approved and monitored network paths.

What Customers Can Expect

With this update, OCM gives you greater control over how replication traffic moves from your AWS environment into OCI. Instead of relying on OCM to automatically create temporary networking resources, you can now use your existing private network pathways during the replication process.

This is especially helpful for customers who need:

  • 🔒 Consistent enforcement of internal security and networking policies
  • 🔗 End to end control over the network path between AWS and OCI
  • 📜 Compliance with regulatory or industry requirements
  • 🔌 Integration with existing private connectivity options such as FastConnect and IPSec VPN

In short, you bring your own network and OCM works within it, allowing replication traffic to follow the same secure patterns already established in your environment.

Use Your Existing Private Network Resources

With this enhancement, OCM now supports running AWS to OCI replication through your own network topology. This includes support for:

  • Existing OCI VCNs and subnets
  • FastConnect for high bandwidth private connectivity
  • IPSec VPN for encrypted paths from on premises or AWS environments
  • Custom route tables and network security groups
  • Private VCN configurations with restricted or controlled egress

All replication traffic stays within your chosen private route, not on an automatically created or internet accessible segment.

This provides a simpler, more secure, and more controlled replication experience for customers handling sensitive systems, regulated workloads, or environments where replication traffic must remain private at all times.

Adoption and Feedback

Our customers who participated during Limited Availability successfully used this feature and saw improvements in managing their security and networking rules, with the added flexibility to switch between public HTTPS replication and private subnet-based replication based on migration workload needs.

We look forward to seeing more customers use this capability as part of their AWS to OCI migration workflows. If you have questions or feedback as you get started, please reach out through your usual Oracle support or account channels.