Skip to main content

AWS Solutions Library

Guidance for Research Data Monetization on AWS

Capture measurable business value leveraging data-driven insights

Overview

This Guidance demonstrates two ways that you can generate measurable value from research data, also known as data monetization. The first option guides you through a way to make data available to other AWS Cloud customers. With the second option, you can make your data available to customers who use other cloud providers or on-premises services. By monetizing data on AWS, either by a pay-per-use or a subscription model, you can diversify your revenue streams so that you don’t have to depend on someone else to sustainably share your research data. You can also set up this solution so that publishers or other stakeholders can set rules for content pricing based on your own parameters. 

Architecture Diagram

Research Data Monetization

This architecture diagram shows how you can improve data monetization with other AWS customers.

Download the architecture diagram PDF
Architecture diagram illustrating the AWS research data monetization workflow, showing data ingestion, transformation, storage, exchange, and monitoring services including Amazon S3, AWS Glue, AWS Data Exchange, Amazon Redshift, Amazon DynamoDB, and cross-service utilities for monitoring and compliance within publisher and subscriber accounts.

Research Data Monetization on Premises

This architecture diagram shows how you can improve data monetization with customers that use either cloud providers other than AWS or on-premises servers.

Download the architecture diagram PDF
Architecture diagram illustrating a data monetization workflow using AWS services, including data ingestion, transformation, exposure, authentication, access control, monitoring, and billing. Key AWS services shown are Amazon S3, Redshift, DynamoDB, RDS, API Gateway, Lake Formation, Glue, ElastiCache, Cognito, Lambda, Cost Explorer, CloudWatch, CloudTrail, Config, and integration with a corporate data center.

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.

This Guidance uses CloudWatch, CloudTrail, and AWS Config to improve monitoring, helping provide the information and alerts you need to respond quickly to events and facilitate compliance with strict requirements. 

Read the Operational Excellence whitepaper

This Guidance uses AWS Data Exchange to make sure that all data listed on the exchange is handled securely. Additionally, API Gateway and Amazon Cognito confirm authentication and authorization for data access.

Read the Security whitepaper

This Guidance uses AWS services that are all fully managed and serverless, reducing your operational burden to reliably maintain a data product. For example, Lambda maintains high availability by using multiple Availability Zones.

Read the Reliability whitepaper

This Guidance uses AWS services that are fully managed and serverless, automatically scaling up and down as needed to maintain performance. This offloads much of the burden of management from small tech teams while helping nonprofits achieve strict compliance requirements.

Read the Performance Efficiency whitepaper

 This Guidance uses serverless AWS services, so you only pay for what you use rather than provisioning resources that incur costs while idle. And because they are fully managed, you reduce the total cost of ownership. Additionally, you can use AWS Cost Explorer to track your resource usage and costs so that you can make adjustments as needed to stay within your budget. 

Read the Cost Optimization whitepaper

This Guidance uses serverless AWS services, which scale up and down to meet demand. This reduces energy usage because these services run more efficiently, and you don’t need to provision unnecessary resources that would consume energy while idle.

Read the Sustainability whitepaper

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.