Design considerations - Machine Downtime Monitor on AWS

Design considerations

Empty state

When you first launch the solution and sign in to the dashboard, a message might appear stating that there is no data available.


          Empty state

Figure 5: Empty state

This message appears when the solution has not identified any machines to display. There are two reasons why this can occur:

  • Data is not being sent to the solution’s Amazon Kinesis data stream.

    Machine data must be sent to the Kinesis data stream in order for machines to be displayed in the dashboard. If you are already collecting machine data and sending the data to the AWS Cloud, you can forward this data to the Kinesis data stream. For guidance to make this connection, refer to Prerequisites in the Automated deployment section.

    If you are not currently sending machine data to the AWS Cloud, we recommend using the Machine to Cloud Connectivity Framework solution. For guidance to use this solution implementation, refer to Prerequisites in the Automated deployment section.

  • Data sent to the solution’s Kinesis data stream cannot be parsed.

    When the solution is deployed, an item is placed in the solution’s Config DynamoDB table. This MESSAGE_FORMAT item instructs the Filter Kinesis Stream Lambda function on how to parse data sent to the solution’s Kinesis data stream. By default, this solution configures the MESSAGE_FORMAT to match the schema sent by the Machine to Cloud Connectivity Framework solution, but if your data is being sent in a different format, you must update the configuration. For guidance to update this configuration, refer to Step 2 in the Automated deployment section.

Deploying with the Machine to Cloud Connectivity Framework solution implementation

When launching this solution, you also have the option of launching the Machine to Cloud Connectivity Framework solution, which uses AWS IoT Greengrass to transfer machine data into the AWS Cloud. The Machine to Cloud Connectivity Framework solution is configured to send data to an Amazon Kinesis data stream deployed by Machine Downtime Monitor on AWS.

Deployment architecture when using the Machine to Cloud
          Connectivity Framework solution

Figure 6: Deployment architecture when using the Machine to Cloud Connectivity Framework solution

Quotas

Amazon Cognito quotas

This solution uses Amazon Cognito user pools to manage users. Amazon Cognito sends an email every time you create a user, change a password, or reset a password. Amazon Cognito applies quotas the number of emails sent daily per user pool to 50. For customers who plan to use this solution for a large number of users, we recommend using Amazon Simple Email Service (Amazon SES) for these emails. For more information, refer to Authorizing Amazon Cognito to Send Amazon SES Email on Your Behalf in the Amazon Cognito Developer Guide.

Regional deployments

This solution uses AWS AppSync, which is not currently available in all AWS Regions. You must launch this solution in an AWS Region where AWS AppSync is available. For the most current availability by Region, refer to the AWS Regional Services List.