Oracle Cloud Infrastructure Documentation

Creating a Private Endpoint

Oracle Cloud Infrastructure lets you create private endpoints within a service so that you can access resources that are only available using private IPs. In the Anomaly Detection service, create a private endpoint to configure the private network where data source is hosted.

Before you create a private endpoint in Anomaly Detection, you must have the following details:

  • The name of the Virtual Cloud Network (VCN) used to access your data source.
  • The name of the subnet in the VCN.
  • The list of DNS zones used to resolve the FQDNs or private IPs of the data sources that you want to harvest.
    Important

    If the data sources in your private network are accessed with FQDNs and private IPs, you only need the list of all the FQDNs when you create the private endpoint.

    If all the data sources in your private network are accessed with private IPs, then while creating a private endpoint you must specify at least one resolvable FQDN or DNS.

    For private autonomous databases, use the FQDN of the database as the DNS zone. For custom data sources running on OCI compute Virtual Machines (VMs), you can specify the FQDN of the VM, or the domain name of the subnet in which the VM is provisioned, or the domain name of the VCN.

    1. Open the navigation menu and click Analytics & AI. Under AI Services, click Anomaly Detection.
    2. Under Details, click Private endpoints.
    3. Click Create Private Endpoint.
    4. Select the compartment where you want to create the private endpoint. You can create the private endpoint in a different compartment than the compartment where you're creating the private endpoint.
    5. Enter a name to identify the private endpoint.
    6. Select the VCN that's created to provide private access to the data source.
    7. Select the Subnet that has the private endpoint to access the data source.
    8. Enter the DNS zones to resolve. The DNS zone can be a DNS domain name or a FQDN. You can enter up to 30 DNS zones.
      Example: Consider a database with FQDN ad.dbsubnet.dbvcn.oraclevcn.com installed on a machine. The permitted domain name entries can be: dbvcn.oraclevcn.com (VCN DNS), dbsubnet.dbvcn.oraclevcn.com (subnet DNS), or dcat.dbsubnet.dbvcn.com (FQDN). The private IP of the machine can't be specified.
      Important

      If the data sources in your private network are accessed with FQDNs and private IPs, you only need to enter the list of all the FQDNs.

      If all the data sources in your private network are accessed with private IPs, then enter at least one resolvable FQDN.

    9. (Optional) Click Show advanced options to assign tags to the resource. Tags help you to easily find and track resources by selecting a tag namespace, and then entering the key and value.

      To add more than one tag, click Add tag.

      Tagging describes the various tags that you can use organize and find resources including cost-tracking tags.

    10. Click Create.
    The private endpoint is created. The create process can take a couple of minutes. When the private endpoint is created successfully, the private endpoint is in an ACTIVE status.

  • Use the oci anomaly-detection pe create command and required parameters to create a private endpoint:

    oci anomaly-detection pe create ----compartment-id <compartment-id>, -c [<name>] ... [OPTIONS]

    For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

  • Run the CreateAiPrivateEndpoint operation to create a private endpoint.