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 Amazon Kinesis connection:
From the OCI GoldenGate Overview page, click
Connections.
You can also click Create Connection under the
Get started section and skip to step 3.
On the Connections page, click Create Connection.
On the Create Connection page, complete the fields as follows:
For Name, enter a name for the connection.
(Optional) For Description, enter a description that helps
you distinguish this connection from others.
For Compartment, select the compartment in which to create
the connection.
From the Type dropdown, select Amazon Kinesis
for Access key ID, enter the Amazon Web Services
(AWS) user's Access key ID.
Note:
The Access key id
must only contain alphnumeric characters and underscore and be
16-128 characters in length.
Select the Secret access key secret. If located
in a different compartment, use the dropdown to change
compartments.
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.
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.
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.