BMS Documentation
  • đź‘‹Welcome to BMS
  • Overview
    • ✨Our Features
  • Solutions
    • Creating a Branding Campaign
    • Creating a Retargeting Campaign
  • Product documentation
    • Accounts
      • Account Billing
    • Ad Server
      • Creatives
      • Creative Groups
      • Ads
        • Ad Exchange Review
          • Google Authorized Buyers
          • Xandr
      • Creative Builder
        • Blueprints
        • Builds
      • Ad Server Metrics
      • Ad Server Billing
      • Page Load Tracking Tag
    • Demand Side Platform (DSP)
      • Overview
      • Managing Campaigns
      • Managing Budgets
      • Managing Targets
      • Managing Ads
      • Real Time Tab
      • DSP Metrics
      • Campaign Billing
      • Check URL Classification
    • Data Management Platform (DMP)
      • Cookie Pools
      • Trackers
        • Install Instructions
      • Identifier Pools
      • DMP Metrics
      • DMP Billing
    • Catalog Storage Service (CS2)
      • Catalogs
      • Products
      • Import Channels
      • Recommendation Models
      • CS2 Metrics
      • CS2 Billing
    • Identity Access Management (IAM)
      • Users
      • Groups
      • API Keys
    • Media
      • Media Metrics
      • Media Billing
    • Metrics
    • Monitoring
      • Looker Studio
      • Event Stores
      • Event Pipes
      • Monitoring Metrics
      • Monitoring Billing
    • Billing
    • Tag Container
      • Tag Container Metrics
  • Third-Party Integrations
    • Webhook Tool (Zapier)
    • Google Tag Manager
    • Voluum
    • External Data Lake Sync (AWS)
Powered by GitBook
On this page
  • Deploying Infrastructure with AWS CloudFormation
  • Template with VPC
  • Template without VPC
  • Additional Information

Was this helpful?

Edit on GitHub
Export as PDF
  1. Third-Party Integrations

External Data Lake Sync (AWS)

Last updated 1 month ago

Was this helpful?

The integration between Event Stores and AWS allows the seamless transfer of event data to an S3 bucket, ensuring efficient data archiving, backup, and accessibility. Exporting your data to an external data lake brings you more control over your data, leading you to valuable insights.

Before starting, ensure you have AWS Management Console access with permissions to manage Virtual Private Clouds(VPC), Security Groups, Lambda functions, and IAM roles. Also, consider that this procedure may incur additional costs in your AWS account due to the creation and usage of new resources.

Deploying Infrastructure with AWS CloudFormation

Two templates have been developed using CloudFormation to streamline the integration setup and provide the minimum required infrastructure. Depending on your technical knowledge, you can customize these templates after their initial setup to fit your business needs.

To proceed you need an API Key created with read-only permissions for event stores. You can learn to create and retrieve an API Key in this .

Template with VPC

Use this template if a Virtual Private Cloud (VPC) is already configured in your AWS account. Access the template .

After accessing the template, fill in the details:

  • Stack Name: This field is automatically filled, but you can use it to customize the stack name.

  • S3 Bucket Name: Inform or create a name for your S3 Bucket.

  • Create S3 Bucket: Choose 'true' to create a new S3 Bucket, or 'false' to use an existing one.

  • Account ID: Inform your BMS Account ID.

  • API Key: Inform a BMS API Key with the "MON -Event Stores - Read Only" policy of access.

After filling out all the fields, at the end of the page, you must acknowledge that AWS CloudFormation might create IAM resources for this template. Then, click on 'Create Stack' to proceed with the stack creation.

Template without VPC

After accessing the template, fill in the details:

  • Stack Name: This field is automatically filled, but you can use it to customize the stack name.

  • S3 Bucket Name: Inform or create a name of your S3 Bucket.

  • Create S3 Bucket: Choose 'true' to create a new S3 Bucket, or 'false' to use an existing one.

  • Account ID: Inform your BMS Account ID.

  • API Key: Inform a BMS API Key with the "MON -Event Stores - Read Only" policy of access.

  • Subnet IDs: Select a subnet ID for the Lambda function from the drop-down list.

  • Security Group IDs: Select a security group ID for the Lambda function from the drop-down list.

After filling out all the fields, at the end of the page, you must acknowledge that AWS CloudFormation might create IAM resources for this template. Then, click on 'Create Stack' to proceed with the stack creation.

Additional Information

Now you have integrated your BMS Event Stores with AWS and your data will start to be sent as soon as the stack creation is completed, you can follow this process at your stacks dashboard. Check these articles to learn more about related BMS Features and AWS products:

Event Store ID: Inform the Event Store ID, you can find it by clicking on at the same row as the event store you wish to import.

If your AWS account does not have a Virtual Private Cloud (VPC) configured, use this template, which can be accessed .

Event Store ID: Inform the Event Store ID, you can find it by clicking on at the same row as the event store you wish to import.

here
Event Pipes
Event Stores
API Keys
AWS CloudFormation
article
here
Template with VPC
Template without VPC