About This Architecture

Multi-AZ carbon footprint calculator leveraging AWS WAF, ALB, CloudFront CDN, Lambda orchestration, and ML-powered scoring across isolated subnets in us-east-1a and us-east-1b. User requests flow through WAF and ALB to a React frontend, which calls a backend API that triggers Lambda orchestrators to coordinate data extraction, enrichment via ML, CO2e scoring, and personalized recommendations. The architecture spans four subnet tiers per AZ—public, application, processing, and data—with Emission DB and User DB replicated across zones for high availability and disaster recovery. This pattern demonstrates defense-in-depth (WAF + ALB), serverless compute scaling (Lambda), and data residency isolation, critical for compliance-heavy sustainability platforms. Fork this diagram on Diagrams.so to customize subnets, add cross-region failover, or integrate additional ML services. Consider adding VPC Flow Logs and CloudTrail for audit trails in production carbon accounting systems.

People also ask

How do you design a highly available carbon footprint calculator on AWS across multiple availability zones?

This diagram shows a multi-AZ AWS architecture where user requests enter through WAF and ALB, route to a React frontend and backend API, then trigger Lambda orchestrators that coordinate data extraction, ML enrichment, CO2e scoring, and recommendations. Emission and User databases are replicated across AZ-1 and AZ-2 for fault tolerance and disaster recovery.