This Guidance demonstrates an automatically configured data lake on AWS using an event-driven, serverless, and scalable architecture. It leverages AWS managed services to ingest, store, process, and analyze data, offering a secure, flexible, and cost-effective design with proper data governance. This approach provides greater agility, flexibility, and reliability compared to traditional data management systems. The entire solution is built as a codified application using infrastructure-as-code (IaC) and a continuous integration, continuous delivery (CI/CD) pipeline.

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Get Started

Deploy this Guidance

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • Amazon CloudWatch provides comprehensive insights into the performance and health through operational logging from every architectural component. Use Amazon S3 server access logging to track detailed records of requests made to your data lake, empowering you to conduct security and access audits, as well as understand your Amazon S3 billing. DynamoDB meticulously tracks the status of your data lake pipeline jobs, enabling you to swiftly identify and resolve any errors that may arise.

    Read the Operational Excellence whitepaper 

  • AWS Key Management Service (AWS KMS) safeguards your data lake by encrypting all data at rest using customer-managed keys. Protect data in transit with robust TLS 1.2 encryption. AWS Identity and Access Management (IAM) enables you to manage identities and access to your AWS services and resources with precision, through the principle of least privilege.

    Read the Security whitepaper 

  • Amazon S3 serves as the highly durable and available storage layer. Data pipelines are triggered through EventBridge, which sends messages to Amazon SQS to initiate pipeline jobs. Errors are handled by moving messages to a dead letter queue for debugging and reprocessing. The Guidance can be redeployed to another AWS Region or account in case of regional failure, ensuring flexibility and resilience.

    Read the Reliability whitepaper 

  • This solution optimizes performance by using Lambda for lightweight tasks and AWS Glue for heavy data transformations. AWS Glue, a serverless data integration service, simplifies and accelerates data preparation while reducing costs. It leverages Apache Spark for scalable execution of transformation jobs. Step Functions orchestrates AWS Glue jobs, providing distributed processing capabilities to enhance the data pipeline's performance.

    Read the Performance Efficiency whitepaper 

  • This Guidance uses serverless AWS services, reducing total ownership costs and enabling scalability based on demand. Amazon S3 serves as the storage layer, offering various cost-efficient storage classes with automated lifecycle management for diverse data access patterns. By shifting infrastructure management to AWS, the serverless approach allows developers to focus on code, further lowering costs and improving efficiency.

    Read the Cost Optimization whitepaper 

  • Serverless services in this Guidance scale based on demand, maximizing energy efficiency and minimizing compute resources. Amazon S3 implements data lifecycle policies and stores ingested data in Parquet format. This compressed format reduces data scans per query, further decreasing compute resources needed for the workload. The combination of serverless architecture and efficient data storage optimizes overall performance and resource utilization.

    Read the Sustainability whitepaper 

Related Content

[Content Type]

[Title]

This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?

 Feedback