> 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-postgresql/db-services/readme-postgresql/homepage-postgresql/overview-postgresql.md). # Overview The Overview tab is the primary connection hub for your PostgreSQL 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** | Username for connecting to the database. Click copy to copy. | | **Password** | Set or reset the password here. Click the eye icon to reveal the current password (encrypted by default). | | **Port** | Database listener port. Default is **5432**. Click copy to copy. | | **Connection Pool Port** | Port on which PgBouncer listens for pooled connections. Default is **6432**. Applications that want to use connection pooling connect to this port instead of the standard PostgreSQL port. | | **Service URL** | Full connection URL. Each instance, database, and connection pooler gets its own URL. | > **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. *** ## 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. 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. **Publicly accessible** is disabled by default (Yes/No). To enable or disable it: 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. For HA services, the private link automatically routes to the current primary instance during switchovers. ### 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** to appear. Copy it. 5. In the AWS console, navigate to **VPC** → **Endpoints** → **Create endpoint**. 6. Choose **Other endpoint services**, paste the service endpoint noted above, and click **Verify service**. 7. Select the VPC and subnets, choose **IPv4** for IP address type, and click **Save**. 8. Once the endpoint status is **Available**, note the DNS name from the VPC Details tab (the one without a region name). 9. Use this DNS name to connect to your database service. *** ## 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, and select a region. 6. On the **Resource** tab: select **Connect to an Azure resource by resource ID or alias**, and specify the service endpoint from the Tessell portal. 7. On the **Virtual Network** tab: select your virtual network and subnet. 8. Leave **DNS** as default → optionally add tags → click **Create**. 9. After Tessell approves the connection request, the connection state changes to **Approved**. 10. Note the private IP of the private endpoint and use it as the hostname in your service URL. *** ## 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. *** ## 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.

Figure 1 — Overview tab

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/overview-postgresql.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.