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. 

Please note: [Disclaimer]

Architecture Diagram

  • Research Data Monetization
  • This architecture diagram shows how you can improve data monetization with other AWS customers.

    Download the architecture diagram PDF 
  • 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 

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.

  • 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 

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?