> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staging.metronome.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Postgres AWS

## Prerequisites

* If your Postgres database is protected by security groups or other firewall settings, you will need to have the data-syncing service's static IP available to complete Step 1.

## Step 1: Allow access

Allow write access to a portion of your RDS or Aurora PostgreSQL database.

### Configure the Security Group

1. In your **Amazon RDS** > **Databases** list, click the PostgreSQL instance you want to send data to.
2. In the database page, in the **Connectivity & security** tab, make note of the **Endpoint** and the **Port** number.

![](https://storage.googleapis.com/prequel_docs/images/postgres-endpoint.png "endpoint + port.png")

3. In the **Security** section, ensure that set the **Publicly accessible** setting is set to **Yes** to ensure that the destination is accessible from outside your VPC. Note that it is still only accessible through whitelisted IPs at this point.

![](https://storage.googleapis.com/prequel_docs/images/postgres-publicly-accessible.png "publicly accessible.png")

4. Click one of the VPC security groups (usually `default`). Note: VPC groups are permissive (vs. restrictive) and for instances with multiple VPC security groups, only one needs to be configured with the new inbound rule.

![](https://storage.googleapis.com/prequel_docs/images/postgres-vpc-security-groups.png "vsg.png")

5. In the **Security Groups** section, select the **Inbound rules** tab.
6. Click **Edit inbound rules** and then click **Add rule**.
7. Edit the newly created rule of type **Custom TCP** with the **Port range** noted in the first step (usually `5432`) and a `Custom` **Source** value that includes all of the service IPs. Note: you will need to add `/32` to the end of each IP (CIDR notation).
8. Click **Save rules**.

![](https://storage.googleapis.com/prequel_docs/images/postgres-add-rule.png "add rule.png")

### Configure network ACLs (access control list)

For database instances in a VCP

1. In your RDS dashboard, select the PostgreSQL instance.
2. Click the link to the instance's VPC.
3. Click the **VPC ID**.

![](https://storage.googleapis.com/prequel_docs/images/postgres-vpc-id.png "vpc id.png")

4. In the **Details** section, click on the link under **Main network ACL**.

![](https://storage.googleapis.com/prequel_docs/images/postgres-main-network-acl-id.png "network acl id.png")

5. Click on the network ACL ID.

![](https://storage.googleapis.com/prequel_docs/images/postgres-network-acl-id.png "network acl id.png")

#### Edit the inbound rules

6. Click on the **Inbound rules** tab, and check if there is an existing rule with a Source of `0.0.0.0/0` set to `Allow`. (This is a default rule created by AWS. If this rule already exists, skip to **Edit outbound rules**.)

![](https://storage.googleapis.com/prequel_docs/images/postgres-inbound-rules.png "inbound rules.png")

7. Create the inbound rule (if it doesn't exist). Click **Edit inbound rules** and either **Add new rule** or edit an existing rule to allow access to the **port number** of your database instance (usually `5432`) from the Prequel static IP. Click **Save changes**.

#### Edit the outbound rules

8. In the ACL menu, select the **Outbound rules** tab, and check if there is an existing rule with a Destination of `0.0.0.0/0` set to `Allow`. (This is a default rule created by AWS. If this rule already exists, skip to the next step.)

![](https://storage.googleapis.com/prequel_docs/images/postgres-outbound-rules.png "outbound rules.png")

9. Create the outbound rule (if it doesn't exist). Click **Edit outbound rules** and edit the rules to allow outbound traffic to ports 1024-65535 for **Destination** `0.0.0.0/0`.

## Step 2: Create writer user

Create a database user to perform the writing of the source data.

1. Open a connection to your Amazon RDS PostgreSQL database.
2. Create a user for the data transfer by executing the following SQL command.

```sql theme={null}
CREATE USER <username> PASSWORD '<some-password>';
```

3. Grant user `create` and `temporary` privileges on the database. `create` allows the service to create new schemas and `temporary` allows the service to create temporary tables.

```sql theme={null}
GRANT CREATE, TEMPORARY ON DATABASE <database> TO <username>;
```

> 🚧 If the `schema` already exists:
>
> By default, the service creates a new schema based on the destination configuration (in the next step). If you prefer to create the schema yourself before connecting the destination, you must ensure that the writer user has the proper permissions on the schema, using `GRANT ALL ON schema <schema> TO <username>;`

## Step 3: Add your destination

Securely share your **host name**, **database name**, **port**, your chosen **schema name**, **username**, and **password** with us to complete the connection.