Guidance for Monitoring and Optimizing Energy Usage on AWS
Overview
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
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.
Operational Excellence
This Guidance takes in real-time and batch telemetry data from IoT sensors, and trains a Machine Learning model to deliver recommendations to reduce energy usage. The model is stored as a model artifact in Amazon S3 and will trigger AWS CodePipeline to request human approval before deployment. This allows end users to question and validate the model recommendation with ease.
Security
This Guidance encourages the use of role-based access with AWS Identity and Access Management (AWS IAM). This ensures only the appropriate people have access to the content. All roles are defined with least-privilege access, and all communications between services stay within the customer account.
All data is encrypted both in-transit and at rest using AWS Key Management Service (AWS KMS). The data catalog in AWS Glue is encrypted.
Reliability
AWS Glue, Amazon S3, and Neptune are all serverless, and will scale data access performance as data volume increases. Neptune also adjusts capacity to provide just the right amount of database resources that the application needs, avoiding the need to set up and manage any servers or data warehouses.
Data is stored in a data lake that is built with an Amazon S3 bucket. Amazon S3 objects are stored across a minimum of three Availability Zones. This provides 99.999999999% durability of objects. Therefore, the Guidance is inherently resistant to failures.
Performance Efficiency
By using serverless technologies, you provision only the exact resources you use. AWS Glue and AWS Lambda only run when needed. Additionally, Neptune is a fully managed serverless graph database, which also scales according to demand to ensure just the right number of resources are needed to complete the job.
Cost Optimization
This Guidance uses serverless components such AWS Glue, Amazon S3, and Neptune. These services automatically scale up and down to meet demand, so you only pay for what you use.
Sustainability
All resources in this Guidance are serverless and scale with use, which reduces the number of resources that are idle.
Implementation resources
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages