Overview
This Guidance demonstrates how to configure a self-service data analytics environment that is simple to launch and access for data engineers and data scientists. The integrated development environment (IDE) is based on Jupyter Notebooks, providing an interactive interface for easy data exploration, and includes all the necessary tools to debug, build, and schedule near real-time data pipelines. The environment supports secure team collaboration with workload isolation, and allows administrators to self-provision, scale, and de-provision resources from a single interface without exposing the complexities of the underlying infrastructure or compromising security, governance, and costs. Administrators can independently manage cluster configurations and continuously optimize for cost, security, reliability, and performance.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Deploy with confidence
Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.
Well-Architected Pillars
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.
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.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages