This Guidance demonstrates how to drive insights for media planning, activation, and measurement from AWS Clean Rooms. With sample AWS Clean Rooms queries, you can learn how to use such queries in Amazon Athena and Amazon QuickSight to drive insights for media planning, activation, and measurement.
AWS Glue is used to produce a Data Catalog for data provided in account B.
AWS Clean Rooms is configured to provide data from account B to the collaboration.
Results of a collaboration within AWS Clean Rooms are stored in an Amazon Simple Storage Service (Amazon S3) bucket within account A.
AWS Glue is used to create a Data Catalog of the query results from AWS Clean Rooms collaboration. Amazon Athena is configured to query results data stored on Amazon S3.
Amazon QuickSight is used to design and share dashboards by utilizing the query results developed in Athena.
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.
This solution is built using a multi-tier architecture, where every tier is independently scalable, deployable, and testable. The facets of this multi-tier architecture, which are decoupled from each other, are compute, storage, data management (catalog), and orchestration.
Observability is built in. Every service publishes metrics to Amazon CloudWatch, where dashboards and alarms can be configured.
Data at rest is encrypted using SSE-S3 encryption. Data in transit from external system into Amazon S3 is encrypted and transferred over HTTPS. AWS Identity and Access Management (IAM) policies are created using the least privilege access, so every policy is restrictive to the specific resource and operation.
Every service or technology chosen for each architecture layer is serverless and fully managed by AWS, making the overall architecture elastic, highly available, and fault tolerant.
Using serverless technologies, you only provision the exact resources you use. The serverless architecture reduces the amount of underlying infrastructure you need to manage, allowing you to focus on solving your business needs.
The services in this guidance are entirely serverless. Using serverless technologies, you only pay for the resources you consume. As the data ingestion velocity increases and decreases, the costs will align with usage.
When AWS Glue is performing data transformations or crawling your data, you only pay for infrastructure during the time the processing is occurring. Similarly, when Athena is querying data, you only pay for the run time for each query and any related storage costs for the results on Amazon S3.
By extensively using serverless services, you maximize overall resource use because compute is only used as needed. The efficient use of serverless resources reduces the overall energy required to operate the workload. You can also use the AWS Billing console carbon footprint tool to calculate and track the environmental impact of the workload over time at the account, region, and service level.
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; 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.