ChatDiagram
Experimente grátis
AWS · data lake · analytics

AWS Data Lake Analytics

This AWS data lake analytics diagram collects application databases and clickstream logs through Kinesis and Glue before storing them in an S3 data lake. The lake supports a Glue Data Catalog, Athena queries, a Redshift warehouse and SageMaker models. Athena and Redshift both feed QuickSight dashboards. It gives a clear service-level view of data movement and consumption without defining table formats, data-retention policies or individual pipeline schedules.

Tipo Diagrama de blocosNorma Ogata / standard controls textbook conventionMecanismo schematex-blockdiagramAtualizado 24/09/2026
AWS Data Lake Analytics
Drawing preview
A solicitação

“Create an AWS data lake analytics diagram with application databases, clickstream logs, Kinesis and Glue, an S3 data lake, Glue Data Catalog, Athena, Redshift, QuickSight, and SageMaker.”

Depois, tenteAdd an AWS Lake Formation governance layer for the S3 data lake.Add an Amazon EMR transformation job after the data lake.
O que há neste desenho

Entenda as decisões por trás dele.

01Ingestion

Collect application and clickstream data with Kinesis and Glue.

02Central storage

Land the data in S3.

03Query choices

Support Athena and Redshift consumers.

04Business output

Feed QuickSight dashboards and SageMaker models.

Use it for a service-level overview of AWS analytics architecture.

Ver todos os modelos de diagrama de blocos →

Perguntas frequentes

Dúvidas comuns

Why use S3 as a data lake?

S3 provides durable object storage that many AWS analytics services can read from or write to.

What is the Glue Data Catalog?

It stores metadata that helps AWS analytics services discover data assets.

When would a team use Athena and Redshift?

Athena suits queries directly on data in S3, while Redshift supports warehouse-oriented analytical workloads.