Connect to Oracle NoSQL

Learn to create a connection to Oracle NoSQL to use as a target for OCI GoldenGate.

Before you begin

If you want to use resource principals to authenticate and connect to an OCI resource, ensure that you:

• Create a dynamic group for your deployment. You can choose to authorize a single deployment or all deployment in a compartment or tenancy. See Writing matching rules to define dynamic groups.

• Add the required policies for the dynamic group

• Configure the required policies to enable secure Vault and Secrets access, such as use secrets, use vaults, and read secret-bundles. For more information, see Minimum recommended policies.

Create the connection

To create an Oracle NoSQL connection:

1. From the OCI GoldenGate Overview page, select Connections.

   You can also select Create Connection under the Get started section and skip to step 3.

2. On the Connections page, select Create Connection.

3. On the Create Connection page, complete the fields as follows:

   1. For Name, enter a name for the connection.

   2. (Optional) For Description, enter a description that helps you distinguish this connection from others.

   3. (For GoldenGate on Multicloud only) Select your Subscription, and then complete the following fields.

      1. From the Compartment dropdown, select the compartment in which the Resource Anchor resides.

      2. Select the Multicloud partner region.

      3. Select your Partner availability zone. The available options populate based on the selected Multicloud partner region.

   4. For Compartment, select the compartment in which to create the connection.

   5. For Type, select Oracle NoSQL.

   6. For Region, select the Oracle Object Storage region.

   7. For User, select one of the following options:

      • Use current tenancy and user, and then enter the following information:

        1. Select the Private key secret. If located in a different compartment, use the dropdown to change compartments.

        2. Select the Private key passphrase secret. If located in a different compartment, use the dropdown to change compartments.

        3. For Private key passphrase, enter the corresponding public key fingerprint.

      • Use resource principal, to authenticate and access other OCI resources.

      • Specify another tenancy and user, and then enter the following information:

        1. Enter the Tenancy OCID.

        2. Enter the User OCID.

        3. Select the Private key secret. If located in a different compartment, use the dropdown to change compartments.

        4. Select the Private key passphrase secret. If located in a different compartment, use the dropdown to change compartments.

        5. For Public key fingerprint, enter the corresponding public key fingerprint.

      Note:

      • Secrets are credentials such as passwords, certificates, SSH keys, or authentication tokens that you use with OCI services. To create a secret, see Creating a secret. Ensure that you:

        • Select Manual secret generation.

        • Paste the credentials into Secret contents.

      • If you prefer not to use password secrets, ensure that you deselect Use secrets in vault in the Security section under Advanced Options, located at the bottom of this form.

      • When you need to update the Secret content, ensure that you:

        • Create a new Secret version using the Plain-Text template and provide the updated content. For more information, see Updating a Secret’s Content.

        • Refresh the connection to clear cached Secret content.

   8. Expand Show advanced options. You can configure the following options:

      • Security

        • Deselect Use vault secrets you prefer not to use password secrets for this connection. If not selected:

          • Select Use Oracle-managed encryption key to leave all encryption key management to Oracle.

          • Select Use customer-managed encryption key to select a specific encryption key stored in your OCI Vault to encrypt your connection credentials.

      • Network connectivity

        • Shared endpoint, to share an endpoint with the assigned deployment. You must allow connectivity from the deployment's ingress IP.

        • Dedicated endpoint, for network traffic through a dedicated endpoint in the assigned subnet in your VCN. You must allow connectivity from this connection's ingress IPs.

          Note:

          • If a dedicated connection remains unassigned for seven days, then the service converts it to a shared connection.
          • Learn more about Oracle GoldenGate connectivity.

      • Security attributes: Add security attributes to control access to this connection using Zero Trust Packet Routing (ZPR).

      • Tags: Add tags to organize your resources.

4. Select Create.

After the connection is created, it appears in the Connections list. Ensure that you assign the connection to a deployment to use it as a source or target in a replication.

Next steps

• Assign a connection to a deployment
• Manage connections