Access Google Translate Data from MySQL in Amazon QuickSight

Amazon QuickSight gives you a way to quickly build visualizations, perform analytics, and get insights from AWS data sources, uploaded files, and other databases in the cloud. When paired with the CData SQL Gateway, you get the same functionality with access to hundreds of Big Data, NoSQL, and SaaS sources, both on-premises and in the cloud. In this article, we use the SQL Gateway with the CData ODBC Driver for Google Translate to access Google Translate data through a MySQL connection in Amazon QuickSight, either in real time using direct queries, or by importing the data into SPICE.

Connect to Google Translate Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

Authentication

Google Cloud Translation API requires OAuth 2.0 authentication to ensure secure access to translation services, datasets, glossaries, and adaptive MT resources. This authentication method allows you to securely connect to your Google Cloud project and manage translation resources with proper authorization.

OAuth 2.0 Setup and Configuration

Step 1: Create Google Cloud Project and Enable API

To set up OAuth authentication:

1. Visit the Google Cloud Console
2. Create a new project or select an existing project
3. Note down your Project ID (required for all API calls)
4. Navigate to "APIs & Services" > "Library"
5. Search for and enable the "Cloud Translation API"
6. Go to "APIs & Services" > "Credentials"
7. Click "Create Credentials" and select "OAuth Client ID"
8. Configure the OAuth consent screen if prompted
9. Select "Desktop application" or "Web application" as appropriate
10. Set the authorized redirect URI (CallbackURL)
11. Copy the Client ID and Client Secret for use in your connection

Required Connection Properties

• AuthScheme: Set this to OAuth (required)
• OAuthClientId: Client ID from Google Cloud Console (required)
• OAuthClientSecret: Client secret from Google Cloud Console (required)
• CallbackURL: Redirect URI specified in your OAuth application (required)
• InitiateOAuth: Set to GETANDREFRESH for automatic token management (recommended)
• ProjectId: Your Google Cloud project ID or project number (required for queries)

Required OAuth Scopes

The Google Cloud Translation API Profile requires the following OAuth scope:

• https://www.googleapis.com/auth/cloud-translation - Full access to Cloud Translation API resources including translation, datasets, glossaries, and adaptive MT

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to Google Translate data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

To connect to the SQL Gateway from QuickSight, you will need to run the SQL Gateway on a web-facing machine. After configuring the SQL Gateway, make note of the following information:

• The IP address or domain name of the machine hosting the SQL Gateway
• The data source name (likely CData API Sys) of the MySQL service
• The port number of the MySQL service
• The credentials of a SQL Gateway user with access to the service

Configure Remote Access

If your ODBC Driver and the remoting service are installed on-premise (and not accessible from Amazon QuickSight), you can use the reverse SSH tunneling feature to enable remote access. For detailed instructions, read our Knowledge Base article: SQL Gateway SSH Tunneling Capabilities.

Connect to Google Translate in QuickSight

Once you have a MySQL Service configured for the Google Translate ODBC Driver, you are ready to connect to the data in QuickSight. Start by logging in to your QuickSight console. From there, click Manage Data, then click New Data Set and choose MySQL as the data source.

Configure the data set using the values for the MySQL service for Google Translate you configured in SQL Gateway (be sure to use the DSN for the database name). Validate your connection and click Create Data Source.

Visualize Google Translate Data in QuickSight

For this article, we will use a custom SQL query for our data visualization. To do so, click Edit/Preview Data and in the resulting Data Prep screen follow the steps below:

1. Name your data set (for example, SupportedLanguages).
2. If you wish to import your data into QuickSight SPICE, click the SPICE option, otherwise QuickSight will query the data directly.
3. Under the Tables menu, click Switch to Custom SQL Tool.
   • Give your SQL query a name.
   • Enter your custom SQL query. For example:
     SELECT LanguageCode, DisplayName FROM SupportedLanguages
   • Click Finish.
4. Click Save & Visualize.

After you have saved the data set, you can configure the visualization. Select the columns you wish to visualize and choose a visual type. Your visualization can be customized, from its name to the way that data is aggregated.

With the CData ODBC Driver for Google Translate and SQL Gateway, you are able to easily build data visualizations and perform analytics on Google Translate data in Amazon QuickSight. If you have any questions, such as needing to access your on-premises data from AWS QuickSight, let our Support Team know.