aws / iot-atlas Goto Github PK

The Gateway Pattern page has 'tbd' placeholder under the example box.

This is a request for enhancement to translate the IoT Atlas in French.

On Safari 12.0 and Chrome 69.0 the footer including the copyright is large and overlaps the core content of the page even when scrolling.

When device's use credentials to authenticate and authorize with an IoT solution, they will inevitably have confidential information residing somewhere in the device. There should be a design describing the common approach to the protection of confidential content on a resource constrained device.

When any Edge device sends data to cloud, it is not always necessary to send those in very frequently. Most of the cases every 15 minutes or 20 minutes works in real time. So, if we can have design around time and size for each kind of data that will be great cost saving approach for the Edge devices.

Proposed Design Synopsis: A collection of devices is managed as a system to accomplish a control objective. A control system actively monitors telemetry outputs and uses commands to inject system inputs to achieve the objective.

This is a backwards-looking Issue to track the change necessary to make room for multiple languages.

I've received some questions on this... Which local area network topology is used by devices connected to a gateway?

It would be nice to have a small "On this page" table of contents in the upper-right of each Design page. Initially this would show the Challenge, Solutions, Considerations, and Examples sections of the page.

Hi Guys,

I just wanted to explore IoT Atlas what are all software need to install and how to start this. Could any one please help me.

Proposed Design Synopsis: A human uses their voice to trigger a control objective in the IoT solution. The control objective drives commands that are sent to the devices or other components of the IoT solution.

The tiny "Improve this Page" link in the footer of each page is broken.

Describe how to implement sending a bulk / large amount of data. This may come about due to the sample frequency being significantly higher than the reporting frequency, it may arise when the samples from sensors are simply too large for the transport protocol in use, or it might arise when a device/gateway experiences a long duration of time without an ability to send data into the solution. Furthermore, this new design would flesh out the high-level guidance already captured in the Telemetry design's considerations.

The height of the language selection dropdown box is too small.

It is still possible to see that it is a selection bar with a language but the text is cropped by the height being too small.

It is not a major problem as the location of that dropdown list and the crop text is enough to understand that it is probably the language selection dropdown. Once you click on the box the languages appear clearly.

By removing the local copies of images in the zh-cn content hierarchy hugo will still find the en-us images automatically when generating the site. By using the same images we will not have to copy them to new languages.

Proposed Design Synopsis: A collection of assets are sending telemetry data to gauge the health of the assets (vibrations, temperature, voltage, ...). This data is monitored by a control systems which sends notifications and alerts to a maintenance supervisor. For a preventive maintenance scenario threshold based comparison is used to send alerts to a maintenance supervisor for further human analysis and scheduling labor work to perform maintenance. For a predictive maintenance scenario, a machine algorithm is used to predict failure in the future; other 3rd party sources of data are integrated to retrieve past historical failure and service records. For a prescriptive maintenance scenario, the control system integrates with 3rd party applications to schedule the labor and order new parts automatically.

Although it is nice to have PPTx download links on each of the Design pages it would be easier to update the diagram set and download them if the Designs were centralized into a single file.

The ubuntu docker image is ARM64 but the Golang binaries are hardcoded to amd64.
Binaries should be compatible for the build architecture.

There are an increasing number of good whitepapers and articles about IoT design implementations on the internet. The IoT Atlas should include curated links to this content. The curated links could/should also include metadata about which IoT Atlas designs are described in the linked content.

Readers should be able to select Examples of Designs that are general (i.e. pseudo-code based) or cloud-specific.

Each Examples section would have (in the fullness of time) a set of tabs allowing such a selection. These might be similar to the tabs used here to switch between configuration formats.
https://gohugo.io/getting-started/configuration/#example-configuration