It is strange to see this error in the device log /greengrass/ggc/var/log/system/localwatch/localwatch.log. It seems this issue is related to the permission/ credentials settings. After I update the Group Role (AWS IoT -> Classic V1 -> Group -> Settings) and re-deploy the group, this issue is gone.
Read More »cd /greengrass/ggc/core/sudo ./greengrassd start You can also use the parameters: start/ stop/ restart
Read More »sudo yum remove awscli Install Java 8 runtime: sudo yum install java-1.8.0-openjdk Verify Java version: java -version
Read More »As you may know that “AWS IoT Core supports 50 subscriptions per connection. AWS IoT Core might reject subscription requests on the same connection in excess of this amount and the connection is closed. Clients should validate the SUBACK message to ensure that their subscription requests have been successfully processed.” However, if you didn’t check the SUBACK message, it could…
Read More »As you may know, API GW follows CORS specifications which are defined by Mozilla. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin Due to CORS specification, the server cannot respond with multiple domains in a single Access-Control-Allow-Origin header unfortunately. For REST API to have multiple domains in CORS, a work around could be to create an API with a Lambda proxy integration. So that we can assign…
Read More »Sometimes the settings of environment is tricky. It is better to check the boto version in your code.
Read More »