> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/overview.md). # Overview The Overview tab is the primary connection hub for your Oracle database service. It displays everything needed to connect client applications, manage network access, configure private links, and control public accessibility. *** ## How do I get the connection details for my database service? | Field | Description | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Host** | Hostname in the format `-.`. For HA services, Tessell keeps this DNS pointing to the current primary — applications should always use this hostname. Click the edit icon to rename the DNS (single-instance only); click copy to copy it. | | **Connect to** | Indicates connections go to the Database. | | **Database** | Database name for connection strings. Click copy to copy it. | | **Username** | Default master username chosen during provisioning. Click copy to copy. Tessell manages only this user — additional schema users created during migration remain valid but are not managed by Tessell. | | **Password** | Set or reset the master password here. Click the eye icon to reveal the current password. The password must be at least 9 characters long and may include alphanumeric characters and: `!`, `#`, `$`, `%`, `^`, `&`, `*`. | | **Port** | Database listener port. Click copy to copy. | | **Service URL** | Full connection URL. Each instance, database, and connection pooler gets its own URL. | > **Note:** For CDB/PDB services, the username and password shown here are for the CDB user — not the PDB. To reset a PDB master user password, raise a Tessell support ticket. > **Note:** Tessell supports DNS names without the suffix (format: `.`). Contact Tessell support to enable this. *** ## How do I enable SSL/TLS for my database connection? The **CA certificate** section appears when SSL was enabled at provisioning. It lets you view, download, or copy the certificate. SSL connections use TLS 1.2 to encrypt data in transit between clients and database instances. For more information, see [Database connections using SSL/TLS](/tessell/database-engines/tessell-for-oracle/database-connections-using-ssl-tls.md). *** ## How do I get SSH access to the database VM? VM access is granted through a bastion host that must be deployed in the same network as the database service (or a network with access to the database subnet). Access is time-limited and request-based. ### Steps to request VM access 1. Click **Request** in the **VM access** section. 2. Select the instances to grant access to: * **All computes at service level** — includes the controller node. * **Default primary node** — primary instance only. 3. Choose a duration (in hours) from the dropdown. 4. Specify the reason for access. 5. Enter the allowed IP address (private IP of your bastion host). 6. Click **Request**. 7. After the request is approved, click **Connect** and download the access key. 8. Use the key and instructions in the downloaded folder to SSH into the VM. *** ## How do I control which IP addresses can connect to my database? The **Allowed IP addresses** section lists the client IPs from which connection requests are accepted (database port only). 1. Click the edit icon next to **Allowed IP addresses**. 2. In the **Update Connectivity** window, add or remove IP addresses. The dialog shows your current client IP. 3. Click **+ Add current client IP** to add your own IP automatically. 4. You can also add CIDR blocks to allow a range of addresses. 5. Click **Update** to apply. To enable or disable **public access**: click the edit icon next to **Publicly accessible** → toggle the value → click **Update**. Public access cannot be enabled if the VPC/VNet is configured for private access only. *** ## How do I configure AWS PrivateLink for my database service? AWS PrivateLink provides a private connection from your AWS VPC to the Tessell database service without traversing the public internet. For HA services, the private link automatically routes to the current primary instance during switchovers. A dedicated private link is required for DR/RR instances. ### Steps to configure AWS PrivateLink 1. Click the edit icon next to **AWS Private Link** → the **Private Link** window opens. 2. Enter the ARN(s) of allowed AWS principals. Accepted formats: * AWS account: `arn:aws:iam:::root` * Specific IAM user: `arn:aws:iam:::user/` * Specific IAM role: `arn:aws:iam:::role/` 3. Click **Create**. The status changes to **Updating**. 4. Wait for the **service endpoint name** to appear (e.g., `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc`). Copy it. 5. In the AWS console, navigate to **VPC** → **Endpoints** → **Create endpoint**. 6. Choose **Other endpoint services**, paste the service endpoint name, and click **Verify service**. 7. Select the VPC and subnets where your client machine resides. 8. Select **IPv4** for IP address type → click **Save**. 9. Once the endpoint status is **Available**, note the DNS name without the region suffix (first in the DNS list). 10. Use this DNS name as the host in your connection string. *** ## How do I configure Azure Private Link for my database service? Azure Private Link provides a private connection from your Azure VNet to the Tessell database service. For HA services, it automatically routes to the current primary during switchovers. A dedicated private link is required for DR/RR instances. ### Steps to configure Azure Private Link 1. Click the edit icon next to **Azure Private Link** → the **Private Link** window opens. 2. Enter the allowed Azure subscription ID and press **Enter**. 3. Click **Create**. Wait for the service endpoint to appear and copy it. 4. In the Azure portal, navigate to **Private endpoints** → **+ Create**. 5. On the **Basics** tab: choose a resource group, enter a name, optionally set a network interface name, and select a region. 6. On the **Resource** tab: select **Connect to an Azure resource by resource ID or alias**, paste the Tessell service endpoint. 7. On the **Virtual Network** tab: select your virtual network and subnet. 8. Leave **DNS** as default → add optional tags → click **Create**. 9. After Tessell approves the connection request, the endpoint status changes to **Approved**. 10. Note the private IP of the private endpoint and use it as the hostname in your connection string. *** ## What are Tags on the Overview tab? The **Tags** section displays key-value pair tags assigned to the database service. A unique tag is assigned at provisioning time. Editing tags post-provisioning is not propagated to underlying cloud resources (planned feature). *** ## What does the Refresh History section show? The **Refresh History** section is displayed only for cloned services. It shows the last refreshed date and time for the clone. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.