ÃÛ¶¹ÊÓƵ

DocumentationAnalyticsExport Guide

Configure a report destination for a Data Warehouse request

Last update: Thu Sep 19 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User
  • Admin

There are various configuration options available when creating a Data Warehouse request. The following information describes how to configure a report destination for the request.

For information about how to begin creating a request, as well as links to other important configuration options, see Create a Data Warehouse request.

NOTE
Consider the following when configuring a report destination:

  • We recommend using a cloud account or email for your report destination. Legacy FTP and SFTP accounts are available but are not recommended.

  • Any cloud accounts that you previously configured are available to use for Data Warehouse. You can configure cloud accounts in any of the following ways:

  • Cloud accounts are associated with your ÃÛ¶¹ÊÓƵ Analytics user account. Other users cannot use or view cloud accounts that you configure.

  • You can edit any locations that you create from the Locations manager in Components > Locations

To configure the destination where Data Warehouse reports are sent:

  1. If you haven’t already, begin creating a request in ÃÛ¶¹ÊÓƵ Analytics by selecting Tools > Data Warehouse > Add.

    For additional details, see Create a Data Warehouse request.

  2. On the New Data Warehouse request page, select the Report destination tab.

    Report destination tab

  3. (Conditional) If a cloud account (and a destination on that account) has already been configured in ÃÛ¶¹ÊÓƵ Analytics, you can use it as your report destination:

    note note
    NOTE
    Accounts are available to you only if you configured them or if they were shared with an organization you are a part of.
    If you are a system administrator, the Show all destinations option is available. Enable this option if you want to have access to all accounts and locations that were created by any user in the organization.

    1. Select the account from the Account drop-down menu.

      Any cloud accounts that you configured in any of the following areas of ÃÛ¶¹ÊÓƵ Analytics are available to use:

    2. Select the destination associated with the account from the Select destination drop-down menu.

  4. (Conditional) If you don’t have access to a cloud account that is already configured in ÃÛ¶¹ÊÓƵ Analytics, you can configure one:

    1. Select the Account drop-down menu, then select Add account.

    2. On the Add account dialog box, specify the following information:

      table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
      Field Function
      Location account name The name of the location account. This name appears when creating a location
      Location account description Provide a short description of the account to help differentiate it from other accounts of the same account type.
      Make account available to all users in your organization

      Enable this option to allow other users in your organization to use the account.

      Consider the following when sharing accounts:

      • Accounts that you share cannot be unshared.
      • Shared accounts can be edited only by the owner of the account.
      • Anyone can create a location for the shared account.
      Account type

      Select your cloud account type. We recommend having a single account for each account type, with multiple locations as needed within that account.

      System administrators can limit the account types that users can create, as described in Configure whether users can create accounts. If you can’t create accounts as described in this section, contact your system administrator.

    3. In the Account properties section, specify information specific to the account type that you selected.

      For configuration instructions, expand the section below that corresponds to the Account type that you selected. (Additional legacy account types are also available, but are not recommended.)

      Account types

      accordion
      Amazon S3 Role ARN

      To configure an Amazon S3 Role ARN account, specify the following information:

      table 0-row-2 1-row-2 layout-auto
      Field Function
      Role ARN You must provide a Role ARN (Amazon Resource Name) that ÃÛ¶¹ÊÓƵ can use to gain access to the Amazon S3 account. To do this, you create an IAM permission policy for the source account, attach the policy to a user, and then create a role for the destination account. For specific information, see .
      accordion
      Google Cloud Platform

      To configure a Google Cloud Platform account, specify the following information:

      table 0-row-2 1-row-2 layout-auto
      Field Function
      Project ID Your Google Cloud project ID. See the .
      accordion
      Azure SAS

      To configure an Azure SAS account, specify the following information:

      table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 layout-auto
      Field Function
      Application ID Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the .
      Tenant ID Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the .
      Key vault URI

      The path to the SAS token in Azure Key Vault. To configure Azure SAS, you must store an SAS token as a secret using Azure Key Vault. For information, see the .

      After the key vault URI is created, add an access policy on the Key Vault to grant permission to the Azure application that you created. For information, see the .

      Or

      If you want to grant an access role directly without creating an access policy, see the . This adds the role assignment for the application ID to access the key vault URI.
      Key vault secret name The secret name that you created when adding the secret to Azure Key Vault. In Microsoft Azure, this information is located in the Key Vault you created, on the Key Vault settings page. For information, see the .
      Location account secret Copy the secret from the Azure application that you created. In Microsoft Azure, this information is located on the Certificates & secrets tab within your application. For more information, see the .
      accordion
      Azure RBAC

      To configure an Azure RBAC account, specify the following information:

      table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto
      Field Function
      Application ID Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the .
      Tenant ID Copy this ID from the Azure application that you created. In Microsoft Azure, this information is located on the Overview tab within your application. For more information, see the .
      Location account secret Copy the secret from the Azure application that you created. In Microsoft Azure, this information is located on the Certificates & secrets tab within your application. For more information, see the .
      accordion
      Email
      note note
      NOTE
      Email accounts can be used only with Data Feeds. (Email accounts are not supported with Data Warehouse or Classification sets).

      To configure an Azure RBAC account, specify the following information:

      table 0-row-2 1-row-2 layout-auto
      Field Function
      Recipients Email notifications can be sent to specific users when the report is sent. Specify a single email address or a comma-separated list of email addresses.

  5. Continue configuring your Data Warehouse request on the Report options tab. For more information, see Configure report options for a Data Warehouse request.

Legacy account types

IMPORTANT
The destinations described in this section are legacy, and are not recommended. Instead, use one of the following destinations when creating a data warehouse destination: Amazon S3, Google Cloud Platform, Azure RBAC, Azure SAS, or Email. See the information above for details about each of these recommended destinations.

The following information provides configuration information for each of the legacy destinations:

FTP

Data warehouse data can be delivered to an ÃÛ¶¹ÊÓƵ or customer-hosted FTP location. Requires an FTP host, username, and password. Use the path field to place feed files in a folder. Folders must already exist; feeds throw an error if the specified path does not exist.

Use the following information when completing the available fields:

Account fields

  • Account name: The name of the FTP account.

  • Account description: A description of the FTP account.

  • Hostname: Enter the desired FTP destination URL. For example, ftp.company.com.

    note note
    NOTE
    Do not include ftp:// at the beginning of the URL.

  • Username: Enter the username to log in to the FTP site.

  • Password and confirm password: Enter the password to log in to the FTP site.

Location fields

  • Location name: The name of the location on the FTP account where you want files sent.

  • Location description: A description of the location on the FTP account.

  • Directory path: The path to the location on the FTP account.

SFTP

SFTP support for data warehouse is available. Requires an SFTP host, username, and the destination site to contain a valid RSA or DSA public key. You can download the appropriate public key when creating the data warehouse destination.

Use the following information when completing the available fields:

Account fields

  • Account name: The name of the FTP account.

  • Account description: A description of the FTP account.

  • Hostname: Enter the desired SFTP destination URL. For example, sftp.company.com.

    note note
    NOTE
    Do not include sftp:// at the beginning of the URL.

  • Username: Enter the username to log in to the SFTP site.

  • Use temporary file extensions during upload: When enabled, the .part file extension is used during the upload process. Keep this option enabled unless your SFTP server restricts file names from being changed after the upload completes.

  • Public keys: Download the appropriate public key when creating the data warehouse destination.

Location fields

  • Location name: The name of the location on the SFTP account where you want files sent.

  • Location description: A description of the location on the SFTP account.

  • Directory path: The path to the location on the SFTP account.

For additional information about SFTP configuration, see Send Data Warehouse requests to SFTP servers.

S3

You can send warehouse data directly to Amazon S3 buckets. This destination type requires a Bucket name, an Access Key ID, and a Secret Key. See within the Amazon S3 docs for more information.

The user you provide for uploading data warehouse data must have the following :

  • s3:GetObject
  • s3:PutObject
  • s3:PutObjectAcl

The following 16 standard AWS regions are supported (using the appropriate signature algorithm where necessary):

  • us-east-2
  • us-east-1
  • us-west-1
  • us-west-2
  • ap-south-1
  • ap-northeast-2
  • ap-southeast-1
  • ap-southeast-2
  • ap-northeast-1
  • ca-central-1
  • eu-central-1
  • eu-west-1
  • eu-west-2
  • eu-west-3
  • eu-north-1
  • sa-east-1
NOTE
The cn-north-1 region is not supported.

Azure Blob

Data warehouse support Azure Blob destinations. Requires a container, account, and a key. Amazon automatically encrypts the data at rest. When you download the data, it gets decrypted automatically. See within the Microsoft Azure docs for more information.

NOTE
You must implement your own process to manage disk space on the data warehouse destination. ÃÛ¶¹ÊÓƵ does not delete any data from the server.
recommendation-more-help
6b7d49d5-f5fe-4b7f-91ae-5b0745755ed2