This Guidance helps customers scale product carbon footprint (PCF) tracking, reduce the manual effort involved with data collection and calculation, and provide transparent and auditable PCFs for reporting. The architecture pairs Internet of Things (IoT) sensor data from a manufacturing facility with product information and emission factors. An interactive dashboard uses this data to track product-level energy and carbon footprint in addition to benchmarking environmental performance across equipment and sites. With this Guidance, customers can identify hotspots and best practices to lower their PCF and manufacturing costs.

Please note: This solution by itself will not make a customer compliant with any product carbon footprint frameworks, standards, or regulations. It provides the foundational infrastructure from which additional complementary solutions can be integrated.

Architecture Diagram

Download the architecture diagram PDF 
  • Overview
  • Please note: This is an overview architecture. For diagrams highlighting different aspects of this architecture, open the other tabs.

  • Data Sources and Ingestion
  • Storage and Processing
  • Consumption and Dashboard

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.

  • CloudWatch provides centralized logging with metrics and alarms across all deployed services. These metrics and alarms can raise alerts for operational anomalies.

    Read the Operational Excellence whitepaper 
  • Resources are protected using AWS Identity and Access Management (IAM) policies and principles. Use least privilege access and role-based access to grant permissions to operators. AWS Key Management Service (KMS) encrypts data at rest. HTTPS endpoints with transport layer security (TLS) provide encryption for in-transit data, including service endpoints and API Gateway endpoints.

    Read the Security whitepaper 
  • This Guidance uses serverless services whenever possible, such as API Gateway, Lambda, and Timestream, enabling auto-scaling to respond to fluctuating demands. This Guidance also uses AWS services such as Amazon S3, Amazon RDS, and Timestream to provide built-in functionality for data backup and recovery.

    Read the Reliability whitepaper 
  • This Guidance uses serverless managed services, such as Lambda, that automatically scale in response to changing demand, reducing resource overhead. Additionally, customers can apply different analytics tools to their data stored in Amazon S3, depending on their needs.

    Read the Performance Efficiency whitepaper 
  • This Guidance relies on serverless and fully managed services, such as Lambda, Amazon S3, and Timestream, which automatically scale according to workload demand. As a result, you only pay for the resources you use.

    Read the Cost Optimization whitepaper 
  • Amazon S3 lifecycle policies can automatically move data to more energy-efficient storage classes, enforce deletion timelines, and minimize overall storage requirements. Timestream allows for data to automatically be moved from the memory tier to the magnetic tier to minimize cost. This Guidance also uses managed, serverless technologies such as AWS Glue, Lambda, and Timestream to help ensure hardware is minimally provisioned to meet demand.

    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?