Tailer Documentation
  • What is Tailer Platform?
  • Getting Started
    • Prepare your local environment for Tailer
    • Install Tailer SDK
    • Set up Google Cloud Platform
    • Encrypt your credentials
  • [Tutorial] Create a first data pipeline
    • Introduction
    • Prepare the demonstration environment
    • Copy files from one bucket to another
    • Load files into BigQuery tables
    • Prepare data
    • Build predictions
    • Export data
    • Congratulations!
    • [Video] Automatic Script
      • SQL script file
      • DDL script file
      • Tables to Tables script file
      • Launch configuration and furthermore
  • Data Pipeline Operations
    • Overview
    • Set constants with Context
      • Context configuration file
    • Move files with Storage to Storage
      • Storage to Storage configuration file
    • Load data with Storage to Tables
      • Storage to Tables configuration file
      • Storage to Tables DDL files
    • Stream incoming data with API To Storage
      • API To Storage configuration file
      • API To Storage usage examples
    • Transform data with Tables to Tables
      • Tables to Tables configuration file
      • Table to Table SQL and DDL files
    • Export data with Tables to Storage
      • [V3] Table to Storage configuration file
      • Table to Storage SQL file
      • [V1-V2: deprecated] Table to Storage configuration file
    • Orchestrate processings with Workflow
      • [V2] Workflow configuration file
      • [V1: deprecated] Workflow configuration file
    • Convert XML to CSV
      • Convert XML to CSV configuration file
    • Use advanced features with VM Launcher
      • Process code with VM Launcher
        • VM Launcher configuration file for code processing
      • Encrypt/Decrypt data with VM Launcher
        • VM Launcher configuration file for data encryption
        • VM Launcher configuration file for data decryption
    • Monitoring and Alerting
      • Monitoring and alerting parameters
    • Asserting Data quality with Expectations
      • List of Expectations
    • Modify files with File Utilities
      • Encrypt/Decrypt data with File Utilities
        • Configuration file for data encryption
        • Configuration file for data decryption
    • Transfer data with GBQ to Firestore
      • Table to Storage: configuration file
      • Table to Storage: SQL file
      • VM Launcher: configuration file
      • File-to-firestore python file
  • Tailer Studio
    • Overview
    • Check data operations' details
    • Monitor data operations' status
    • Execute data operations
    • Reset Workflow data operations
    • Archive data operations
    • Add notes to data operations and runs
    • View your data catalog
    • Time your data with freshness
  • Tailer API
    • Overview
    • Getting started
    • API features
  • Release Notes
    • Tailer SDK Stable Releases
    • Tailer Beta Releases
      • Beta features
      • Beta configuration
      • Tailer SDK API
    • Tailer Status
Powered by GitBook
On this page
  • Create a project
  • Enable APIs
  • Grant roles to the App Engine default account
  • Add the App Engine default account to the appropriate groups
  • Create a generic service account
  • Generate JSON credentials

Was this helpful?

Edit on GitHub
  1. Getting Started

Set up Google Cloud Platform

Some features of Tailer Platform rely on Google Cloud Platform's resources, or allow you to manipulate them. Some steps need to be performed as preparation.

PreviousInstall Tailer SDKNextEncrypt your credentials

Last updated 3 years ago

Was this helpful?

Create a project

Create a dedicated Google Cloud Platform project to use with Tailer Platform. Billing needs to be enabled.

To create a new project:

  1. Go to the page in the Cloud Console.

  2. In the organization drop-down list at the top of the page, select the organization in which you want to create a project.

  3. Click Create Project.

  4. In the New Project window that appears, enter a project name and select a billing account as applicable.

  5. If you want to add the project to a folder, enter the folder name in the Location box.

  6. When you're finished entering new project details, click Create.

Enable APIs

The following Google Cloud APIs need to be enabled for the project you have created:

  • Cloud Functions

  • Identity and Access Management (IAM)

  • Cloud Resource Manager

To enable an API:

  1. Click the Enable APIs and Services button.

  2. Click the API you want to enable. If you need help finding the API, use the search field.

  3. In the page that displays information about the API, click Enable.

When you enable the Cloud Functions API, a service account is automatically created for your project. It should be named as follows:

YOUR-PROJECT-ID@appspot.gserviceaccount.com

You need to grant roles to this service account so that it has permission to complete specific actions on some resources in your Cloud Platform project.

To grant roles to the service account:

  1. Add the Project > Editor and Service Account > Service Account Token Creator roles.

  2. Click Save to apply the roles to the service account.

The App Engine default account will need to access the following elements of Tailer Platform:

  • Composer (Airflow): to trigger DAGs

  • Firestore: to retrieve data operations

  • Source Repositories: to retrieve Cloud Functions source code

The GCP project hosting the Composer and Firestore instances should already have groups with the appropriate permissions. You have to add the App Engine default account to these groups.

This generic service account will be used among other things for:

  • Deploying configurations on behalf of an authorized user

  • Moving files from one bucket to another

You will need a dedicated service account for each GCP project you will use Tailer with (for example if they contain a source or destination bucket used in a transfer operation). We recommend you only create one service account per project to avoid right administration becoming too complex.

To create the service account:

  1. Click Select a project, choose your project, and click Open.

  2. Click Create Service Account.

  3. You can use YOUR-PROJECT-ID as a name for the service account.

  4. Click Save.

You should now have a new service account named as follows:

YOUR-PROJECT-ID@YOUR-PROJECT-ID.iam.gserviceaccount.com

To generate JSON credentials:

  1. Select JSON as Key type and click Create.

When you create a key, your new public/private key pair is generated and downloaded to your machine. It serves as the only copy of the private key. You are responsible for storing the private key securely.

These credentials will need to be encrypted, so you can use them later in a data operation JSON configuration file.

Open the page for your project in the Cloud Console.

Grant roles to the App Engine default account

Open the page for your project in the Cloud Console.

Click the Edit button corresponding to YOUR-PROJECT-ID@appspot.gserviceaccount.com.

Add the App Engine default account to the appropriate groups

Create a generic service account

Open the page in the Cloud Console.

Generate JSON credentials

In the page of the Cloud Console, find the row of the YOUR-PROJECT-ID@YOUR-PROJECT-ID.iam.gserviceaccount.com service account that you've just created.

In that row, click the More button, and then click Create key.

🔓
👥
🆕
🔐
🗄️
🔑
Manage resources
APIs & services
IAM & Admin
Service Accounts
Service Accounts