Integrate Live PingOne Data into Amazon SageMaker Canvas with RDS

Amazon SageMaker Canvas is a no-code machine learning platform that lets you generate predictions, prepare data, and build models without writing code. When paired with CData Connect AI, you get instant, cloud-to-cloud access to PingOne data for building custom machine-learning models, predicting customer churn, generating texts, building chatbots, and more. This article shows how to connect to Connect AI from Amazon SageMaker Canvas using the RDS connector and integrate live PingOne data into your ML model deployments.

CData Connect AI provides a pure SQL, cloud-to-cloud interface for PingOne, allowing you to easily integrate with live PingOne data in Amazon SageMaker Canvas — without replicating the data. CData Connect AI looks exactly like a SQL Server database to Amazon SageMaker Canvas and uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc) directly to PingOne, leveraging server-side processing to quickly return PingOne data.

Configure PingOne Connectivity for Amazon SageMaker Canvas

Connectivity to PingOne from Amazon SageMaker Canvas is made possible through CData Connect AI. To work with PingOne data from Amazon SageMaker Canvas, we start by creating and configuring a PingOne connection.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "PingOne" from the Add Connection panel

3. Enter the necessary authentication properties to connect to PingOne.

   To connect to PingOne, configure these properties:

   • Region: The region where the data for your PingOne organization is being hosted.
   • AuthScheme: The type of authentication to use when connecting to PingOne.
   • Either WorkerAppEnvironmentId (required when using the default PingOne domain) or AuthorizationServerURL, configured as described below.

   Configuring WorkerAppEnvironmentId

   WorkerAppEnvironmentId is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set WorkerAppEnvironmentId to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   AuthorizationServerURL is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set AuthScheme to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • InitiateOAuth: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the OAuthAccessToken each time you connect, use InitiateOAuth.
   • OAuthClientId: The Client ID you obtained when you created your custom OAuth application.
   • OAuthClientSecret: The Client Secret you obtained when you created your custom OAuth application.
   • CallbackURL: The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in OAuthSettingsLocation, to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add PingOne Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to PingOne data from Amazon SageMaker Canvas.

Connecting to CData Connect AI from Amazon SageMaker Canvas

With the connection in CData Connect AI configured, you are ready to integrate live PingOne data into Amazon SageMaker Canvas using its RDS connector.

1. Select a domain and user profile in Amazon SageMaker Canvas and click on "Open Canvas".
2. Once the Canvas application opens, navigate to the left panel, and select "My models".
3. Click on "Create new model" in the My models screen.
4. Specify a Model name in Create new model window and select a Problem type. Click on "Create".
5. Once the model version gets created, click on "Create dataset" in the Select dataset tab.
6. In the Create a tabular dataset window, add a "Dataset name" and click on "Create".
7. Click on the "Data Source" drop-down and search for or navigate to the RDS connector and click on " Add Connection".
8. In the Add a new RDS connection window, set the following properties:
   
   
   • Connection Name: a relevant connection name
   • Set Engine type to sqlserver-web
   • Set Port to 14333
   • Set Address as tds.cdata.com
   • Set Username to a Connect AI user (e.g. [email protected])
   • Set Password to the PAT for the above user
   • Set Database name the PingOne connection (e.g., PingOne1)
9. Click on "Create connection".

Integrating PingOne Data into Amazon SageMaker Canvas

With the connection to Connect AI configured in the RDS, you are ready to integrate live PingOne data into your Amazon SageMaker Canvas dataset.

1. In the tabular dataset created in RDS with PingOne data, search for the PingOne connection configured on Connect AI in the search bar or from the list of connections.
2. Select the table of your choice from PingOne, drag and drop it into the canvas on the right.
3. You can create workflows by joining any number of tables from the PingOne connection (as shown below). Click on "Create dataset".
4. Once the dataset is created, click on "Select dataset" to build your model.
5. Perform analysis, generate prediction, and deploy the model.

At this point, you have access to live PingOne data in Amazon SageMaker that you can utilize to build custom ML models to generate predictive business insights and grow your organization.

SQL Access to PingOne Data from Cloud Applications

Now you have a direct connection to live PingOne data from Amazon SageMaker Canvas. You can create more connections, datasets, and predictive models to drive business — all without replicating PingOne data.

To get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, see the CData Connect AI.