You can use Oracle Cloud Infrastructure Console to configure a private access channel for your Oracle Analytics Cloud instance.

1. In Oracle Cloud Infrastructure Console, click in the top left corner.
2. Click Analytics & AI. Under Analytics, click Analytics Cloud.
3. Select the compartment that contains the Oracle Analytics Cloud instance you're looking for.
4. Click the name of the instance you want to configure a private access channel for.

   The instance must be deployed with Enterprise Edition.

5. On the Instance Details page, navigate to the Resources section, click Private Access Channel, and then click Configure Private Access Channel.
   
6. For Name, enter any name to identify the private access channel.
7. If your Oracle Analytics Cloud instance has a public endpoint:
   1. Select the Virtual Cloud Network and the Subnet that you want Oracle Analytics Cloud to use to access private data sources.
   2. Optional: If you want to restrict outgoing traffic to the private data source using egress rules in predefined network security groups, select Configure Access Control and then click Another Network Security Group to select one or more network security groups.

   Click Change Compartment to select resources from a different compartment. If you can't see the VCN, subnet, or network security group you want, check you have the required permissions.

   If your Oracle Analytics Cloud instance has a private endpoint, the private access channel automatically uses the same VCN, subnet, and network security groups as the private endpoint. See Create Oracle Analytics Cloud with a Private Endpoint.

8. Enable access to at least one private data source:
   1. Optional. To add the domain name associated with the selected VCN as a private source, select Virtual Cloud Network's Domain Name as DNS Zone.
   2. In DNS Zone, enter the name of a domain you want to give access to.

      For example: companyabc.com

      • Private data source in a corporate network peered to an Oracle Cloud Infrastructure VCN

        Register a DNS zone in the format: <domain name>

        For example:

        • If the data source FQDN hostname is data-source-ds01.companyabc.com, add the DNS Zone as companyabc.com.
        • If the data source FQDN hostname is db01.dbdomain.companyabc.com, add the DNS Zone as dbdomain.companyabc.com to only give Oracle Analytics Cloud access to hosts under dbdomain.companyabc.com.

      • Private data source in an Oracle Cloud Infrastructure VCN

        Register a DNS zone in the format: <VCN DNS label>.oraclevcn.com

        For example: companyabc.oraclevcn.com

        Tip: If you want to connect to a private source on the same VCN as the private access channel, select the checkbox Virtual Cloud Network's Domain Name as DNS Zone on the Configure Private Access Channel page to auto-fill the domain name value.

      • Private Oracle Autonomous Data Warehouse or Oracle Autonomous Transaction Processing in an Oracle Cloud Infrastructure VCN

        Register a DNS zone in the format: adb.<region>.<realm public domain>

        For example:

        • adb.ap-sydney-1.oraclecloud.com
        • adb.uk-gov-cardiff-1.oraclegovcloud.uk
   3. In SCAN Hosts, enter the name of a SCAN host and the SCAN port you want to give access to.

      For example, SCAN host names such as db01-scan.corp.example.com or prd-db01-scan.mycompany.com might use port 1521.

   4. Enter a useful description for the DNS zone or SCAN host.
   5. To add additional private sources, click Another DNS Zone or Another SCAN host.
9. Click Configure.

   On the Analytics Instances page, the status changes to Active when the configuration process is complete.

10. To test that the private access channel is working, connect Oracle Analytics Cloud to one of the private data sources you configured and verify you can access the data in Oracle Analytics Cloud.
    1. Sign-in to Oracle Analytics Cloud.
    2. Create a connection to the private data source.

       For example, if you registered the domain companyabc.com as a private source, set up a connection that includes this domain name.

       The way you create the connection depends on how you plan to use the data source, that is, whether you want to build a visualization, analysis, pixel-perfect report, or semantic model.

       • Connect to Data for Visualizations and Analyses

       • Manage Database Connections for Semantic Models

       • Connect to Data for Pixel-Perfect Reports
    3. Create a visualization, analysis, pixel-perfect report, or semantic model that uses the connection and verify you can access to the data.