This Guidance demonstrates how to deploy Amazon Monitron to detect abnormal conditions in industrial rotating equipment, helping customers implement a predictive maintenance program and reduce unplanned downtime. Amazon Monitron includes sensors to capture vibration and temperature data, a gateway to securely transfer data to AWS, and a service that analyzes the data using machine learning. It also includes a companion mobile and desktop application to set up the devices and track the conditions of machinery. Customers can connect to the SAP Business Technology Platform from AWS, and export the generated data to create maintenance notifications.

Please note: [Disclaimer]

Architecture Diagram


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.

  • Serverless services, such as Amazon S3, DynamoDB, and Lambda, use AWS CloudTrail and Amazon CloudWatch to log and analyze application metrics. Virtual Private Cloud (VPC) flow logs can also be sent to CloudWatch to analyze packet flow from network interfaces. 

    Read the Operational Excellence whitepaper 
  • Secrets Manager, with secrets rotation policies, can be used to store authentication information as it relates to SAP.  

    All of the resources in this Guidance run within your VPC and the VPC of AWS to protect resources. Data stored at rest can be encrypted using customer-managed and AWS server-side keys. 

    Read the Security whitepaper 
  • Each component of this Guidance can be independently monitored with CloudWatch automated resolution. The serverless services, such as Amazon S3, DynamoDB, and Lambda scale horizontally, automatically responding to the velocity of data ingestion and processing. 

    Read the Reliability whitepaper 
  • Amazon Monitron is purpose-built for this Guidance, utilizing machine learning to detect issues in industrial equipment before they occur. The implementation of this Guidance uses AWS services that integrates with the SAP Business Technology Platform and API, so you can quickly start monitoring equipment health. The performance of the API’s can be monitored in SAP API Management and CloudWatch.

    Read the Performance Efficiency whitepaper 
  • By utilizing serverless technologies, you only pay for the resources you use. The Amazon Monitron kit is available for purchase, and the Amazon Monitron Sensors are wireless, with an estimated five-year battery life. The sensors measure 3-directional vibration and temperature data, and can be mounted on equipment using epoxy. 

    This Guidance uses highly available and serverless services like Amazon S3, KinesisDynamoDB, and Lambda that are pay-as-you-go-services and scale with demand. Costs can be further controlled through Amazon S3 Lifecycle policies, by reducing Lambda cold starts, and instead using a Lambda 'warm start' to help minimize compute and storage requirements. 

    Read the Cost Optimization whitepaper 
  • By extensively using serverless services, you maximize overall resource utilization, as compute is only used as needed. The efficient use of serverless resources reduces the overall energy required to operate the workload. You can also use the AWS Billing Conductor carbon footprint tool to calculate and track the environmental impact of the workload over time at an account, Region, and service level.

    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?