Creating a Data Source and Data Set from SaaS Sources - Amazon QuickSight

Creating a Data Source and Data Set from SaaS Sources

To analyze and report on data from software as a service (SaaS) applications, you can use SaaS connectors to access your data directly from Amazon QuickSight. The SaaS connectors simplify accessing third-party application sources using OAuth, without any need to export the data to an intermediate data store.

You can use either a cloud-based or server-based instance of a SaaS application. To connect to an SaaS application that is running on your corporate network, make sure that Amazon QuickSight can access the application's Domain Name System (DNS) name over the network. If Amazon QuickSight can't access the SaaS application, it generates an unknown host error.

Here are examples of some ways that you can use SaaS data:

  • Engineering teams who use Jira to track issues and bugs can report on developer efficiency and bug burndown.

  • Marketing organizations can integrate Amazon QuickSight with Adobe Analytics to build consolidated dashboards to visualize their online and web marketing data.

  • Teams using social media can access Twitter data to analyze and understand their customers' sentiment.

Use the following procedure to create a data source and dataset by connecting to sources available through Software as a Service (SaaS). In this procedure, we use a connection to GitHub as an example. Other SaaS data sources follow the same process, although the screens—especially the SaaS screens—might look different.

To create a data source and dataset by connecting to sources through SaaS

  1. On the Amazon QuickSight start page, choose Manage data.

  2. On the Your Data Sets page, choose New data set.

  3. In the FROM NEW DATA SOURCES section of the Create a Data Set page, choose the icon that represents the SaaS source that you want to use. For example, you might choose Adobe Analytics or GitHub.

    For sources using OAuth, the connector takes you to the SaaS site to authorize the connection before you can create the data source. A screen similar to one of the following appears.

    If the SaaS data source doesn't use OAuth, the following screen appears.

  4. Choose a name for the data source, and enter that. If there are more screen prompts, enter the appropriate information. Then choose Create data source.

  5. If you are prompted to do so, enter your credentials on the SaaS login page.

  6. When prompted, authorize the connection between your SaaS data source and Amazon QuickSight.

    The following example shows the authorization for Amazon QuickSight to access the GitHub account for the Amazon QuickSight documentation.

    Note

    Amazon QuickSight documentation is now available on GitHub. If you want to make changes to this user guide, you can use GitHub to edit it directly.

    (Optional) If your SaaS account is part of an organizational account, you might be asked to request organization access as part of authorizing Amazon QuickSight. If you want to do this, follow the prompts on your SaaS screen, then choose to authorize Amazon QuickSight.

  7. After authorization is complete, choose a table or object to connect to. Then choose Select.

  8. On the Finish data set creation screen, choose one of these options:

    • To save the data source and dataset, choose Edit/Preview data. Then choose Save from the top menu bar.

    • To create a dataset and an analysis using the data as-is, choose Visualize. This option automatically saves the data source and the dataset.

      You can also choose Edit/Preview data to prepare the data before creating an analysis. This opens the data preparation screen. For more information about data preparation, see Preparing Datasets.

The following constraints apply:

  • The SaaS source must support REST API operations for Amazon QuickSight to connect to it.

  • If you are connecting to Jira, the URL must be public address.

  • If you are connecting to Twitter, the Twitter standard search API returns data for the previous seven days only. In other words, no tweets are found for a date older than one week.

  • If you don't have enough SPICE capacity, choose Edit/Preview data. In the data preparation screen, you can remove fields from the dataset to decrease its size or apply a filter that reduces the number of rows returned. For more information about data preparation, see Preparing Datasets.