API Guide Link: http://postgrest.org/en/v5.2/api.html
Link to authentication page: http://postgrest.org/en/v5.2/auth.html
- Name: Required: Name the connection.
- Connection type: Required: The form will automatically select PostgreSQL. Note that the type will be listed as “rdbms” in your list of connections.
- Mode: Required: Select Cloud if you are connecting to an application on the cloud, and it is publicly accessible (for example, Salesforce or NetSuite). Select On-Premises if you are connecting to a server that is publicly inaccessible and has the integrator.io agent installed on it (for example, Production, AWS, VPC, or MySQL server).
- Host: Required:
- Database Name: Required: The database name is set up while creating the account.
- Username: Required: The username is set up while creating the account.
- Password: Required: The password is set up while creating the account.
- Port: Required:
- Use SSL: Required: Check this checkbox if you want to establish a secure connection to the database. This ensures that data in transit is encrypted.
- Certificate Authority: Optional: This is an optional field if the database uses a certificate that doesn't match or chain to one of the known CAs. Use the CA option to provide a CA certificate that the peer's certificate can match or chain to. For self-signed certificates, the certificate is its own CA and therefore must be provided.
- Key: Optional: Provide the optional private key in PEM format. This is necessary only if database server is using client certificate authentication.
- Certificate: Optional: Provide optional cert chain in PEM format. This is necessary only if the database server is using client certificate authentication.
- Passphrase: Optional: Provide an optional passphrase. This is used to decrypt the Key field. This is necessary only if database server is using client certificate authentication.
- Configure Properties: Optional: By default, all data flowing through a connection record will get submitted to the respective endpoint application at the concurrency level configured for that connection record. Some use cases require multiple connections to share the same concurrency level, and this field allows you to specify that a connection should borrow concurrency from another connection such that the data flowing through both connections will get submitted to the endpoint application together via a shared concurrency model. For example, you might have three separate NetSuite connection records in your integrator.io account (for the purpose of isolating different permissions for different integrations), but you only want to provision one concurrent request for all three NetSuite connection records to share. To implement this use case, you would set up one of the three connections with a concurrency level 1, then set up the other two NetSuite connections to borrow concurrency from the other.