Skip to main content

How do I whitelist Aiwyn’s static IP and use SQL Server encryption?

Christa Mason
Updated

Complete the following steps for this process:

  1. Ensure that SQL server has encryption enabled, thereby encrypting all in-transit data via TLS
  2. Whitelist Aiwyn’s static IP address
  3. SQL login setup

Configure TLS encryption in SQL server

If the SQL Server is in a ".local" network domain then you CANNOT whitelist and use TLS certificate. We cannot use a local Windows account to log into the SQL server.

To enable TLS encryption in Microsoft SQL Server, follow their instructions provided here.

  1. With a TLS certificate installed, the "ForceEncryption" setting would need to remain as "No" (or "0" if configured via a SQL script) to allow both encrypted and unencrypted connections.

A restart of the SQL Server service may be required.

 

Whitelist Aiwyn static IP

Configure Windows Firewall to allow encrypted connections

  1. If Windows Firewall is enabled, follow the instructions provided here.
  2. Allow access to the SQL Server port (default: 1433) from the Aiwyn ETL IP address of 35.245.176.176

Configure your Firewall to allow encrypted connections

Most organizations will have a separate firewall device configured to protect their infrastructure. 

  1. Allow access to the SQL Server port (default: 1433) from the Aiwyn ETL IP address of 35.245.176.176

 

SQL login setup

The creation of a read-only SQL authentication based user is required. This SQL user will be used by Aiwyn's translation engine to pull in your data to our systems. Review SQL login setup for additional details.

Related articles