Cross-cloud data access lets you unify data across Amazon Web Services (AWS),
Google Cloud, and
[AlloyDB for PostgreSQL](https://docs.cloud.google.com/alloydb/docs/overview.md.txt) without complex ETL
pipelines. In this codelab, you use
[borderless Lakehouse](https://docs.cloud.google.com/lakehouse/docs/introduction.md.txt) for analytics,
AlloyDB as an operational source, and
[Managed Service for Apache Spark](https://docs.cloud.google.com/managed-spark/docs/serverless-overview.md.txt) for vectorized
processing, and then analyze the data with Gemini.

## Scenario

In this scenario, you have data across the following sources:

- Transactional data (users, orders, order items) in an operational AlloyDB database.
- Product data in an AWS S3 bucket.
- Clickstream event logs in Cloud Storage.

You join these datasets to identify target demographics for your next marketing
campaign and generate personalized outreach emails.

## What you learn

In this codelab, you perform the following tasks:

- Set up and configure Lakehouse catalog endpoints to unify data silos across AWS S3, Cloud Storage, and AlloyDB.
- Run high-performance vectorized query processing using Managed Service for Apache Spark.
- Join transactional, product, and clickstream datasets without data movement or complex ETL pipelines.
- Use Gemini to derive business insights and generate personalized marketing outreach from your lakehouse.

## Take the codelab

Launch the step-by-step codelab:


[Start the borderless Lakehouse codelab](https://codelabs.developers.google.com/next26/multicloud-lakehouse)

## What's next

- Learn more about [Lakehouse
  concepts](https://docs.cloud.google.com/lakehouse/docs/about-cross-cloud-data-access).
- Learn how to [query remote data](https://docs.cloud.google.com/lakehouse/docs/query-remote-data.md.txt).
- Check [supported regions and
  capabilities](https://docs.cloud.google.com/lakehouse/docs/regions-capabilities-cross-cloud-connections).