This Guidance helps you increase customer engagement through a Product 360 framework. Product 360 is a data analytics framework that provides insights by aggregating relevant information from data sources for a comprehensive view of products. This comprehensive view enhances sales motions based on product usage patterns and guides product strategy and roadmap development. This Guidance is also combined with artificial intelligence and machine learning (AI/ML)-augmented recommendations to support data-driven decision-making for future products. 

Please note: [Disclaimer]

Architecture Diagram


Download the architecture diagram PDF 

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.

  • AWS services used in this Guidance are provisioned in the same AWS Region to reduce data transfer charges. Additionally, services such as QuickSight do not accrue any data transfer charges. Additionally, most services in this Guidance are either serverless or are available with a serverless option, such as Amazon EMR Serverless. Serverless services do not need to run for extended periods of time. You can take advantage of sustained usage through reserved instances for Amazon EMR.

    Read the Operational Excellence whitepaper 
  • Lake Formation applies central audited governance, fine-grained access controls, and data classification tagging. This helps you secure data at the object-, database-, table-, column-, and row-level.

    Read the Security whitepaper 
  • Serverless services such as AWS Glue and DynamoDB scale horizontally, automatically responding to the velocity of data ingestion and processing. This scaling enables the architecture to adapt to changes imposed upon it.

    Read the Reliability whitepaper 
  • The component-oriented architecture allows you to build independent layers using infrastructure as code (IaC). By separating the ingestion, processing, storage, unified governance, cataloging, and consumption, you can more easily test and deploy modules.

    Read the Performance Efficiency whitepaper 
  • The serverless architecture reduces the amount of underlying infrastructure that needs to be managed, allowing you to focus on differentiated work, such as onboarding new customers and building new feature enhancements.

    Read the Cost Optimization whitepaper 
  • Amazon Forecast summarizes large data sets into meaningful insights. This reduces data volumes and processing, helping ensure that you only use the minimum resources required.

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


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


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?