X

Best Practices from Oracle Development's A‑Team

Enabling Oracle Analytics Cloud Private Access Channel

Validated May 17, 2021 with OAC 6.0

Introduction

Oracle Analytics Cloud (OAC) instances may now be enabled with a private access channel (PAC) to reach private data sources.

Private Access Channel compliments and provides an alternative to Remote Data Gateway (RDG) for the private data sources it supports. Both PAC and RDG may be used within the same instance of OAC. There may be sources that PAC supports and RDG does not and vice-versa.

This post is a step-by-step guide for enabling PAC within a public or private OAC instance. This is one of the post listed in the OAC Private End Point Series.

Validations

Validated May 17, 2021 with OAC 6.0

Topics

Before You Begin

Deploying Required Networking Components

Configuring the Private Access Channel

Viewing the Enabled Private Access Channel

 Before You Begin and Assumptions

All names and addresses used in this post are for examples only. 

Privileges

User accounts in OCI tenancies for managing Analytics components.

OAC

An OAC instance is provisioned. Refer here for provisioning a private OAC. Refer here for provisioning a public OAC.

Private OAC Initial State

OAC is provisioned with a private endpoint.

Public OAC Initial State

OAC is provisioned with a public endpoint.

  Deploying Required Networking Components

For a public OAC, the following table lists additional networking components that may be required with links for reference.

COMPONENT USE REFERENCE
VCN Contains the subnet hosting PAC link
SUBNET Hosts the PAC endpoints link

 

The following tables lists the additional components with example values.

VCN

Create or use an existing VCN in the same region as OAC

NAME CIDR Use DNS hostnames in this VCN
VCN1 10.10.10.0/23 Yes

SUBNET

Create or use an existing subnet in the PAC VCN

VCN NAME CIDR Use DNS hostnames in this SUBNET ROUTE TABLE SECURITY LIST DHCP OPTIONS
VCN1 VCN1-OAC-SN 10.10.10.0/27 Yes Default Default Default

 

  Configuring the Private Access Channel

Note: Configuring PAC places OAC in an updating state for approximately 30 minutes. During this time OAC is not available.

In the OCI Console, navigate to Analytics > Analytics Cloud. 

Select the Compartment and Region containing a private OAC or the compartment containing the VCN created for a public OAC. 
Click the OAC Instance Name to be configured.
Under Resources click Private Access Channel
Click Configure Private Access Channel

Complete the PAC dialog

Enter a Name
For a public OAC choose the Compartment and VCN for the PAC. For a private OAC this defaults to the VCN hosting OAC.
For a public OAC choose the Subnet for the PAC. For a private OAC this defaults to the subnet hosting OAC.
For the DNS Zone select Virtual Cloud Network's domain name as DNS zone. Click X to close the additional zone dialog
Click Configure

Note: Adding DNS zones for additional data sources, along with any associated DNS and gateway scenarios are described in companion posts.

Private OAC PAC Enabled

Public OAC PAC Enabled

 Viewing the Enabled Private Access Channel

Once OAC is available again, view the PAC details. Note the two private egress IP addresses.

 Summary

This post provided a step-by-step guide for enabling PAC within a public or private OAC instance.

For other posts relating to analytics and data integration visit http://www.ateam-oracle.com/dayne-carley