Connecting to NPSaaS

You can connect command-line interfaces, IBM, or third-party applications and tools or apps that you create to your IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service instance by using private or public endpoints.

For Azure, you can provision NPSaaS with a private endpoint only or both public and private endpoints.

For AWS, you can provision NPSaaS with a private or a public endpoint.

Each endpoint type provides a set of hostnames or IP addresses that you can use to log in to NPSaaS by using the following components:

NPSaaS web console
The web interface, which you can use to manage and monitor your instance by using a standard HTTPS port 443.
NPSaaS software clients
The command-line interface clients, which you can use to manage and monitor your instance by connecting to the database on port 5480 and the API server on a standard HTTPS port 443.
- To connect to the database, download and install the ODBC/JDBC/nzsql client packages.
- To connect to the API server to manage your instance, download the nz tool.

Connecting to NPSaaS by using public endpoints

A public endpoint can be accessed over the public network or internet.
To connect to your application by using your public hostname details if you are on Azure or AWS, follow the steps.

Retrieve hostname details that are assigned to your instance:
1. Log in to your IBM Cloud account.
2. Go to Resource list > Services and Software > Databases.
3. Click your NPSaaS instance.
  You are now on the Service instance details page. In the Public Endpoints section, you can find information (URL details) about endpoints for accessing the web console, the API server, and the database.
  
  Access to your data is protected by strong authentication, vast NPSaaS authorization options and access controls, and encryption over the wire by using SSL and at rest. You can further restrict access to your instance by setting network policies.
Connect to NPSaaS with the credentials from Generating credentials by using one of the components:
- The NPSaaS web console as described in Getting started with the web console.
- The NPSaaS software clients: the nzsql command or the ODBC or JDBC drivers.

Connecting to NPSaaS by using private endpoints

A private endpoint offers you a way to connect over the cloud platform internal network and is not accessible from public networks.

For Azure, NPSaaS supports private connectivity through Azure Privatelink.

For AWS, NPSaaS supports private connectivity through AWS PrivateLink.

To connect to your application by using your private hostname details if you are on Azure or AWS, follow the steps.

Ensure that you set up your private link endpoint as desribed in Configuring private endpoints.
Connect to NPSaaS with the IP address or hostname that were assigned to your private link endpoint.
- The NPSaaS web console as described in Getting started with the web console.
- The NPSaaS software clients: the nzsql command or the ODBC or JDBC drivers.

You can also connect to your NPSaaS instance private endpoint from on-prem with your Azure or AWS cloud account.

For Azure, set up a VPN or Express Route from your on-prem network to the VNET in your Azure subscription.

For AWS, set up a VPN or Direct Connect from your on-prem network to the VPC in your AWS account. For more information, see Amazon Virtual Private Cloud Connectivity Options.