dbname
”).stripe
.USAGE
and CREATE
permissions to it:
54.245.7.80
35.155.134.189
us-west-2
, you’ll need to allow inbound connections from the IP addresses of that proxy region:
Provider | Region | Proxy Host | IP Addresses |
---|---|---|---|
AWS | us-west-2 (Oregon) | us-west-2.aws.sequindb.io | Same as Sequin’s sync workers |
AWS | us-east-1 (Virginia) | us-east-1.aws.sequindb.io | 18.215.20.21754.210.150.114 |
AWS | eu-west-1 (Ireland) | eu-west-1.aws.sequindb.io | 54.194.222.634.247.185.111 |
AWS | ap-southeast-1 (Singapore) | ap-southeast-1.aws.sequindb.io | 52.74.34.8152.74.82.226 |
id_rsa_sequin_tunnel.pub
public key file shown in the setup modal:
id_rsa_sequin_tunnel.pub
in the home directory of the SSH tunnel user in the ~/.ssh/authorized_keys
file:
id_rsa_sequin_tunnel.pub
file into the authorized_keys file. Save the file and exit the text editor.
Make sure the authorized_keys file is secure. Run the following command:
disable
. See this table for more information.
CONNECT
to your database) and what actions they can take (like SELECT
and CREATE
). These permissions can be defined at the database, schema, table, and view level.
A role is a set of permissions. A user is a role that has login permissions (includes a password that someone can use to login to the database).
sequin
): This is the user Sequin uses to connect to your database. This user only has permission to connect to your database and create the schemas, tables, and views associated to your sync. This user will need owner privileges on any table or view related to your sync.sequin_read
): This role has the privilege to read Sequin tables and views in your database. Any user in your database that needs to read synced data should be granted the sequin_read
role. It is provided for convenience and is not used by the Sequin sync process.sequin_
and sequin_read_
, but include a random alphanumeric appendix. The names are provided during the provisioning process of your database and available on the console at any time.sequin
user creates and updates the data we are syncing for you. When syncing to your database we first create the Sequin user:
sequin_read
role is provided for your convenience. The role has permission to read all the Sequin data in your database. You can give or revoke the read role permission to your database users at any time.
You can manually create this read role during the database setup. If we detect a role named sequin_read
, we’ll grant that role the appropriate permissions. The sequin
user needs to be admin
of the sequin_read
role. The following command will grant the sequin
user admin
options of the role during creation:
admin
option like so:
sequin_read
+ “tab.”ngrok http 5432
(assuming Postgres is running on port 5432
). The Forwarding
property in the ngrok UI in your terminal is the url you’ll use with Sequin’s host field. Ngrok’s detailed instructions for this step can be found here.nc
will “hang open” if it’s able to connect, otherwise it will crash:
invalid_authorization_specification
typically occurs when there is a problem with the way you’re specifying authentication information while trying to connect to a PostgreSQL database. The most common way this happens while using Sequin is when there is a mismatch between the authentication method specified by the database and how Sequin is trying to connect. If you encounter this error, either ensure you’re using a password authentication method, or you have Use SSL selected.