Then, select the project containing the dataset that you want to use.
Next, click CREATE SERVICE ACCOUNT.
Fill in the details as shown below and click CREATE.
Then, select the previously created role and click CONTINUE.
Finally, click DONE.
Creating and downloading the JSON key
Click the three dots under Actions in the service account that you just created and select Manage keys:
Click ADD KEY, followed by Create new key:
In the resulting pop-up, select JSON and click CREATE.
Finally, download this JSON file. This file is required while setting up the GCS data lake destination in RudderStack.
Configuring GCS data lake destination in RudderStack
To send event data to GCS data lake, you first need to add it as a destination in RudderStack and connect it to your data source. Once the destination is enabled, events will automatically start flowing to GCS data lake via RudderStack.
To configure GCS data lake as a destination in RudderStack, follow these steps:
In your RudderStack dashboard, set up the data source. Then, select Google Cloud Storage Data Lake from the list of destinations.
Assign a name to your destination and then click Next.
GCS Storage Bucket Name: The name of the GCS bucket used to store data before loading it into the GCS data lake.
Prefix: If specified, RudderStack will create a folder in the bucket with this prefix and push all data within that folder. For example, https://storage.googleapis.com/<bucketName>/<prefix>/.
Namespace: If specified, all data for the destination will be pushed to https://storage.googleapis.com/<bucketName>/<prefix>/rudder-datalake/<namespace>. If you don’t specify a namespace in the settings, RudderStack sets it to the source name, by default.
Table Suffix: This optional setting lets you define a custom path under which your table data is stored. For example, if you set this field to rs, your data will be pushed to https://storage.googleapis.com/<bucketName>/<prefix>/rudder-datalake/<namespace>/<table-name>/rs.
Choose time window layout: This option lets you set the timestamp-defined layout structure under which the table data will be stored.
For example, if you choose the option Upto Hour (year=YYYY/month=MM/day=DD/hour=HH) and an event called Product Clicked is received at 2022-08-06T17:30:00.000T, then the data will be stored in the following location:
The default value for this setting is YYYY/MM/DD/HH.
Credentials: Enter the content of the downloaded credentials JSON file in this field.
Sync Frequency: Specify how often RudderStack should sync the data to your GCS data lake.
Sync Starting At: This optional setting lets you specify the particular time of the day (in UTC) when you want RudderStack to sync the data to the data lake.
Finding your data in the GCS data lake
RudderStack converts your events into Parquet files and dumps them into the configured GCS bucket. Before dumping the events, RudderStack groups the files by the event name based on the time (in UTC) they were received.
The folder structure is similar to the following format:
To enable network access to RudderStack, allowlist the following RudderStack IPs depending on your region and RudderStack Cloud plan:
Free, Starter, and Growth
All the outbound traffic is routed through these RudderStack IPs.
What are the files written in the location <namespace>/rudder-warehouse-staging-logs/?
RudderStack collects all unprocessed data flowing to the warehouse destinations as staging files. It stores these files in the object storage at the location https://storage.googleapis.com/rudder-warehouse-staging-logs/.
Once the staging files are processed, RudderStack separates them by the event name and sends them to the specified destination in the following format:
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.