title:Destination Actions

plan:dest-actions

{% include content/plan-grid.md name="dest-actions" %}

The Destination Actions framework improves on classic destinations by enabling you to see and control how Segment sends the event data it receives from your sources, to actions-based destinations. Each Action in a destination lists the event data it requires, and the event data that is optional.

You can also choose which event types, event names, or event property values trigger an Action. These Triggers and mappings make it possible to send different versions of the Action, depending on the context from which it is triggered.

title:Comparing Data Lakes and Warehouses

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

As Segment builds new data storage products, each product evolves from prior products to best support the needs of customers. Segment Data Lakes is an evolution of the Warehouses product that meets the changing needs of customers.

hidden:true

title:Configure the Data Lakes AWS Environment

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

The instructions below will guide you through the process required to configure the environment required to begin loading data into your Segment Data Lake. For a more automated process, see[Set Up Segment Data Lakes](/docs/connections/storage/catalog/data-lakes).

title:Segment Data Lakes Overview

redirect_from:'/connections/destinations/catalog/data-lakes/'

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

title:Lake Formation

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

Lake Formation is a fully managed service built on top of the AWS Glue Data Catalog that provides one central set of tools to build and manage a Data Lake. These tools help import, catalog, transform, and deduplicate data, as well as provide strategies to optimize data storage and security. To learn more about Lake Formation features, see[Amazon Web Services documentation](https://aws.amazon.com/lake-formation/features/){:target="_blank"}.

The security policies in Lake Formation use two layers of permissions: each resource is protected by Lake Formation permissions (which control access to Data Catalog resources and S3 locations) and IAM permissions (which control access to Lake Formation and AWS Glue API resources). When any user or role reads or writes to a resource, that action must pass a both a Lake Formation and an IAM resource check: for example, a user trying to create a new table in the Data Catalog may have Lake Formation access to the Data Catalog, but if they don't have the correct Glue API permissions, they will be unable to create the table.

title:Data Lakes Sync History and Health

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

The Segment Data Lakes sync history and health tabs generate real-time information about data syncs so you can monitor the health and performance of your data lakes. These tools provide monitoring and debugging capabilities within the Data Lakes UI, so you can identify and proactively address data sync or data pipeline failures.

title:Data Lakes Sync Reports and Errors

plan:data-lakes

{% include content/plan-grid.md name="data-lakes" %}

Segment Data Lakes generates reports with operational metrics about each sync to your data lake so you can monitor sync performance. These sync reports are stored in your S3 bucket and Glue Data Catalog. This means you have access to the raw data, so you can query it to answer questions and set up alerting and monitoring tools.

title:Data Warehouses

redirect_from:'/connections/warehouses/'

plan:warehouses

{% include content/plan-grid.md name="warehouses" %}

{% include content/whats-a-warehouse.md %}

title:Replay

plan:replay

{% include content/plan-grid.md name="replay" %}

Replay takes an archived copy of your Segment data, and re-sends it to new or existing tools.

On the surface this doesn't sound like much, but this can grant huge benefits to mature data systems: By archiving and replaying data, you can avoid vendor lock-in, and protect your system against data loss.

title:Privacy Controls & Alerts

plan:privacy

{% include content/plan-grid.md name="privacy" %}

The Privacy Portal gives you control over whether specific data is allowed to

enter Segment.