---
title: "Create a test database for a connector function"
slug: "create-a-test-database-for-a-connector-function"
updated: 2022-11-17T18:16:19Z
published: 2022-11-17T18:16:20Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a test database for a connector function

## Overview

*Create a free database on Amazon Web Services (AWS) to try out Connectors immediately.*

Tulip automatically runs a Cloud Connector Host for you. No setup is required on your part. It allows you to connect to any database, API or server that is accessible from the cloud.

However, cloud connector hosts cannot talk to services that are blocked by a firewall, which is common in many corporate IT environments.

You can still test out Connectors immediately by making a database for free on AWS.

## How to Create A Test Database for A Connector Function

Here's how to set up your free test database:

1. Create a free database on AWS. [Follow these instructions](https://aws.amazon.com/getting-started/tutorials/create-connect-postgresql-db/) to set up a free PostgreSQL database.
2. You need to change security info.

Go to your DB Instance on AWS and click **Connectivity & Security** to edit security.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Create%20A%20Test%20Database%20for%20A%20Connector%20Function_121598424.png)

1. You will see this view where you can select **Edit Inbound Rules**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Create%20A%20Test%20Database%20for%20A%20Connector%20Function_121597919.png)

1. Edit the rules to look like the following. One will need to be added for a total of 2.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Create%20A%20Test%20Database%20for%20A%20Connector%20Function_121598021.png)

- "PostgreSQL" "TCP" "5432" "Custom" "0.0.0.0/0"
- "PostgreSQL" "TCP" "5432" "Custom" "::/0"

1. Then [try to connect again](https://support.tulip.co/docs/how-to-write-a-sql-connector-function) using the credentials in the Connector on your Tulip account.

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Connectors**

**Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions.

- **HTTP Connectors** utilize HTTP API endpoints.
- **SQL Connectors** can enable connectivity with certain SQL databases.
- **MQTT Connectors** can connect to MQTT brokers for machine monitoring.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif)

**Connector Host**

Tulip **Connector Hosts**are designed to allow your Tulip Apps to interface with external systems such as databases, APIs, and machines. **On-Prem Connector Hosts**sit within your network and allow Tulip to interface with SQL databases and APIs that aren't accessible to the cloud.

**Connector Function**

**Connector Functions** are individual operations to interact with an HTTP or SQL Datasources. Connector Functions can have inputs and outputs, and can be called from: Triggers, Functions, Automations, and AI Agents.

Once pulled, data can be used throughout your applications.

**Tulip Instance**

A Tulip customer account. Your instance can be found at https://[your-instance].tulip.co

When *your instance*is referenced, we are just talking about your Tulip account on an organization-level, not user-level.