---
title: PostgreSQL SSL Integration Guide
slug: litmusedge-v1/how-to-guides/integration-guides/postgresql-ssl
description: Learn how to set up the PostgreSQL with SSL connector. 
docTags: 
createdAt: 2024-01-17T13:53:34.991Z
---

Review the following guide for setting up an integration between Litmus Edge and a PostgreSQL database using SSL authentication. 

# Before You Begin

You will need the following:

- Access to a PostgreSQL database that uses SSL authentication.
- The CA Certificate and any other required authentication parameters to access the database. 

Refer to the following links to learn more:

- [PostgreSQL Docker Image](https://hub.docker.com/_/postgres)
- [PostgreSQL Documentation](https://www.postgresql.org/docs/)
- [Secure TCP/IP Connections with SSL](https://www.postgresql.org/docs/16/ssl-tcp.html)

# Step 1: Add Device

Follow the steps to [Connect a Device](docId:3eyAfPpweuVmBLCEy17sq). The device will be used to store tags that will be eventually used to create outbound topics in the connector. Make sure to select the **Enable Data Store** checkbox. 

# Step 2: Add Tags

After connecting the device in Litmus Edge, you can [Add Tags](docId:8sE7z3PmRfwL1nmzcwaLX) to the device. Create tags that you want to use to create outbound topics for the connector. 

# Step 3: Add the DB - PostgreSQL SSL Connector

Follow the steps to [Add a Connector](docId\:b7eMDh8AO2-NOqDHwPD7Y) and select the **DB - PostgreSQL SSL **provider. 

Configure the following parameters. 

- **Name**: Enter a name for the connector. 
- **Hostname**: Enter the hostname for the PostgreSQL database. 
- **Port**: The PostgreSQL Server port. The default value is **5432**. 
- **SSL Mode**: Select the SSL Mode (require, verify-ca, verify-full). 
- **CA Certificate**: Paste the CA certificate associated with the database. For Litmus Edge version 3.11.0 and later, you have the option to upload the certificate. 
- **Certificate**: Paste the SSL certificate. For Litmus Edge version 3.11.0 and later, you have the option to upload the certificate. 
- **Private Key**: Enter or paste the SSL private key. 
- **Username**: Enter the appropriate username. 
- **Password**: Enter the password for the username.  
- **Database**: Enter the database name. 
- **Table**: Enter the table name.
- **Show Mapping**: If you want to send data to a custom table, select this check box and unselect *Create table*. See [Work with Tables in SQL Connectors (Create Table and Show Mapping)](docId\:Yj_sKBPP9J_TH3_qvC1Tm) to learn more. To add key/value pairs for the custom table, see [Configure Key/Value Pairs](docId\:Yj_sKBPP9J_TH3_qvC1Tm). 
- **Create table**: If you want to send data to an existing table in the default format, or you want to create a new table in the default format, select this checkbox and unselect *Show Mapping*. See [Work with Tables in SQL Connectors (Create Table and Show Mapping)](docId\:Yj_sKBPP9J_TH3_qvC1Tm) to learn more. 
- **Commit timeout**: Enter the transaction commit timeout in (ms).
- **Max transaction size**: Enter the maximum number of messages before a transaction is committed, regardless of timeout parameter. 
- **Bulk insert count**: (Available for Litmus Edge version 3.11.1 and later) To enable this option, enter the number of messages to group together and send as one bulk insert statement. Enabling this option can improve how quickly data is processed when dealing with high volumes of tags. 
- **Throttling limit**: The maximum number of messages per second to be processed. The default value is zero, which means that there is no limit. 
- **Persistent storage**: When enabled, this will cause messages to undergo a store-and-forward procedure. Messages will be stored within Litmus Edge when cloud providers are online.  
- **Queue Mode**: Select the queue mode as **lifo **(last in first out) or **fifo **(first in first out). Selecting **lifo **means that the last data entry is processed first, and selecting **fifo **means the first data entry is processed first. 

# Step 4: Enable the Connector

After adding the connector, click the toggle in the connector tile to enable it. 

::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/iMtx0yTin43zijwoyX-k0_postgressl.png" size="60" width="388" height="358" position="center" showCaption="false"}

If you see a *Failed *status, you can review the [Connector Logs](docId:5hctoRLhgaX3Ikh_lvi0A) and relevant error messages. 

# Step 5: Create Topics for Connector

You will now need to import the tags created in Step 2 as topics for the PostgreSQL connector. The topics will be created as outbound topics. 

**To create outbound topics:**

1. Click the connector tile.
   The connector *Dashboard *appears. 
2. Click the **Topics **tab. 
3. Click the **Import from DeviceHub** tags icon. 
   The *DeviceHub Import *dialog box appears.

![](https://api.archbee.com/api/optimize/xSuIWwMa6RnsbeD5Kdqd7-zaOGMDYbPZWYALvLBgotp-20250606-203859.png)

After adding all required topics, navigate to the Integration overview page and ensure the connector is not disabled and still shows a CONNECTED status. 

# Step 6: Enable Topics

Ensure the topics you imported are enabled by returning to the *Topics *tab and clicking the **Enable all topics** icon. 

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/HtkW-nbWXeAvOV8ru8B1U_image.png)

# Step 7: Make PostgreSQL Queries

You can now verify that you can view data in the PostgreSQL database. 

Update the credentials, database name, and table name to your specific configurations. 

**To make PostgreSQL queries:**

1. From the PostgreSQL terminal window, enter `psql -h locahost -U postgres`** **and press **ENTER**. If you configured a different username, replace `postgres`. 
   The *psql (9.6.5)*** **version number appears.
2. Enter `\l`** **and press **ENTER**.
   The list of databases appears in the console.
3. Enter `\c postgres`** **and press **ENTER**. 
   *You are now connected to database "db-example" as user "postgres"* appears.
4. Enter `\dt` and press **ENTER**.
   The list of relations appears showing the devicehub schema.
5. Enter `\d devicehub` and press **ENTER**.
   The *public.devicehub* table appears.
6. Enter `select * from devicehub;` and press **ENTER**.
   The data for the devicehub table appears.