Questions tagged with AWS IoT Core

We are looking into iot device management solutions and are analyzing the AWS iot core and greengrass among other products. Our iot devices can be of different types and we will also have zebra devices on android. The AWS iot documents mention that greengrass is supported on Linux and windows. Can we effectively use it for Android devices also? Also we are looking at fleet provisioning of the iot devices. Is this supported for Android devices? Thank you.

Currently trying to get started with IoT Core for my business, and all the documentation tells me how easy it is to add a LoRaWAN gateway via the Console, and how I can just click "Get Started" followed by "Add Gateway". However, there is simply no "Add Gateway" option. I have sifted through every single link there is on the sidebar - with and without the "New Console Experience" option checked - and every single piece of documentation that I can lay my hands on, to try and find where this option is. What can I possibly be missing? The closest thing that I can find - Add a Device - keeps asking whether my device is running Linux or Windows and which SDK I would like to download. Surely there is no need for all that just for the sake of adding a gateway that's in my hand as we speak?

Hello! We have an IoT Core Rule which is fired when a MQTT message is published to certain topic. The message structure is: ``` { "triggers": ["door"], "datetime": "2022-06-01T00:00:00Z", "errCodes": [100], "strength": 107, "net": "GMS", "eco": 0, "light": 0, "def": 0, "fan": 0, "defrost": 1, "Mdef": 0, "comp": 0, "door": 0, "Tcond": 38.1, "Tevap": 1, "Tint": 3.8, "topic": "abc/ar/data/NVC1/test-vscode-3" } ``` We have a requirement where data buffered in remote devices could be sent to IoT Core, so we need to send a "datetime" field (the second one) in the payload. The Iot Core Rule fires a AWS Lambda function, which generates a multi-measure record to be finally sent to Timestream: ``` { "Dimensions":[ { "Name":"hw_model", "Value":"NVC1" }, { "Name":"serial_device", "Value":"test-vscode-3" } ], "MeasureName":"multimeasuredata", "MeasureValueType":"MULTI", "MeasureValues":[ { "Name":"Tint", "Value":"3.8", "Type":"DOUBLE" }, { "Name":"Tevap", "Value":"1", "Type":"DOUBLE" } ], "Time":"1654041600000" } ``` The Timestream table retention periods are: Memory store retention: 45 days Magnetic store retention: 180 days Magnetic store writes: ENABLED The exception thrown is: ``` { "errorType":"RejectedRecordsException", "errorMessage":"One or more records have been rejected. See RejectedRecords for details.", "name":"RejectedRecordsException", "$fault":"client", "$metadata":{ "httpStatusCode":419, "requestId":"VKL72WIIMCBGQNWMMSQLK7CAAQ", "attempts":1, "totalRetryDelay":0 }, "RejectedRecords":[ { "Reason":"The record timestamp is outside the time range [2022-06-17T15:21:13.756Z, 2022-06-27T22:51:04.174Z) of the data ingestion window.", "RecordIndex":0 } ], "__type":"com.amazonaws.timestream.v20181101#RejectedRecordsException", "message":"One or more records have been rejected. See RejectedRecords for details.", "stack":[ "RejectedRecordsException: One or more records have been rejected. See RejectedRecords for details.", " at deserializeAws_json1_0RejectedRecordsExceptionResponse (/var/task/node_modules/@aws-sdk/client-timestream-write/dist-cjs/protocols/Aws_json1_0.js:947:23)", " at deserializeAws_json1_0WriteRecordsCommandError (/var/task/node_modules/@aws-sdk/client-timestream-write/dist-cjs/protocols/Aws_json1_0.js:888:25)", " at processTicksAndRejections (node:internal/process/task_queues:96:5)", " at async /var/task/node_modules/@aws-sdk/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24", " at async /var/task/node_modules/@aws-sdk/middleware-signing/dist-cjs/middleware.js:11:20", " at async StandardRetryStrategy.retry (/var/task/node_modules/@aws-sdk/middleware-retry/dist-cjs/StandardRetryStrategy.js:51:46)", " at async /var/task/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:6:22", " at async Runtime.exports.handler (/var/task/lambda.js:58:20)" ] } ``` We are not falling out the memory retention period (45 days) in this example (27 days), but the range returned in the exception is (IDK why) [2022-06-17T15:21:13.756Z, 2022-06-27T22:51:04.174Z) Do you have any ideas of why this is the range and hence why the record cannot be inserted? Thanks !

After my test, the power of TX will be 12dBm, the lowest power of SX1301, Generally, transmission power is a parameter that is controlled by the LNS. I guess there is a server configuration problem or there is a problem with my configuration file, Am I missing something important? ``` 2022-06-22 01:57:17.532 [S2E:INFO] TX ::0 diid=39028 [ant#0] - on air: 925.7MHz 0.0dBm ant#0(0) DR10 SF10/BW500 frame=20309C905190DF9AD2E59C5E..DE87E47C ``` Check out this link for testing information: https://github.com/lorabasics/basicstation/issues/161 Or is there any other relevant information I can continue to provide, station.conf ``` { /* If slaave-X.conf present this acts as default settings */ "SX1301_conf": { /* Actual channel plan is controlled by server */ "lorawan_public": true, /* is default */ "clksrc": 1, /* radio_1 provides clock to concentrator */ /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */ "device": "/dev/spidev1.0", /* freq/enable provided by LNS - only HW specific settings listed here */ "radio_0": { "type": "SX1257", "rssi_offset": -166.0, "tx_enable": true, "antenna_gain": 0 }, "radio_1": { "type": "SX1257", "rssi_offset": -166.0, "tx_enable": false } /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */ }, "station_conf": { "routerid":"a84041ffff1eeb34", "radio_init": "rinit.sh", "RADIO_INIT_WAIT": "5s", "RX_POLL_INTV": "10ms", "TC_TIMEOUT": "360s", "log_file": "stderr", "log_level": "DEBUG", /* XDEBUG,DEBUG,VERBOSE,INFO,NOTICE,WARNING,ERROR,CRITICAL */ "log_size": 10000000, "log_rotate": 3, "CUPS_RESYNC_INTV": "1s" } } ```

I might be missing something here, but I'd like to use Boto3 to create and queue downlink messages to LoRa devices. However, the docs only appear to support `delete_queued_messages()` and `list_queued_messages()`. https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/iotwireless.html Does boto3 really only support listing and deleting downlinks? Is there no way to create?

I want to show data on Quicksight made by AWS IoT device simulator. [https://repost.aws/questions/QUeJmozwQnTWefA45Ti4aGjQ/canot-find-the-data-iot-simulator-generated] I don't know how to set IoT core in order to receive IoT device simulator's data. If anyone know handson or procedure about this, please let me know.

I have created a lambda function. Where lambda is connected to VPC with two private subnet. Without using Nat Gateway we need to create lambda function and publish a mqtt message to IoT core. We configured VPC endpoint to AWS iot core. Created private hosted zone but no use we are getting error like Timeout task Below is the code we used to publish a message to mqt ``` import json import boto3 client = boto3.client('iot-data', region_name='*******') def lambda_handler(event, context): print(event) # TODO implement # Change topic, qos and payload response = client.publish( topic='esp32/sub', qos=1, payload=json.dumps({"foo":"bar"}) ) print(response) return { 'statusCode': 200, 'body': json.dumps('Published to topic') } ```

Hi, I would like to connect my documentDB to an AWS IoT Core properly (do something similar to IoT Core -> Dynamo Db with a rule). I need it to be highly scalable to handle millions of devices. Has someone done that before? What are the best practices? Thanks in advance !

Hi, I have followed the tutorial [here](https://docs.aws.amazon.com/iot-sitewise/latest/userguide/ingest-data-from-iot-things.html). I can see my data in IoT core, but the measurement are not reported in IoT SiteWise. There seem to be a permission problem. This is the error from the error rule ``` { "ruleName": "SiteWiseTutorialDeviceRule", "topic": "$aws/things/SiteWiseTutorialDevice1/shadow/update/accepted", "cloudwatchTraceId": "e3aec656-d5d7-b500-5558-d51ae7aee895", "clientId": "N/A", "base64OriginalPayload": "eyJzdGF0ZSI6eyJyZXBvcnRlZCI6eyJ0ZW1wZXJhdHVyZSI6MTAuMSwiaHVtaWRpdHkiOjY0LjIsInRpbWVzdGFtcCI6MS42NTU3OTk2MjQ0NTczODFFOX19LCJtZXRhZGF0YSI6eyJyZXBvcnRlZCI6eyJ0ZW1wZXJhdHVyZSI6eyJ0aW1lc3RhbXAiOjE2NTU3OTk2MjR9LCJodW1pZGl0eSI6eyJ0aW1lc3RhbXAiOjE2NTU3OTk2MjR9LCJ0aW1lc3RhbXAiOnsidGltZXN0YW1wIjoxNjU1Nzk5NjI0fX19LCJ2ZXJzaW9uIjo5NjAsInRpbWVzdGFtcCI6MTY1NTc5OTYyNCwiY2xpZW50VG9rZW4iOiIyYzU2Zjg1NC0zM2IzLTQzNmQtYjJjZC1kMzk2ZmZkNTYxMGYifQ==", "failures": [ { "failedAction": "IotSiteWiseAction", "failedResource": "", "errorMessage": "Failed to send message data to IoT SiteWise asset properties. [Code: AccessDeniedException, Message: User: arn:aws:sts::908401988620:assumed-role/SiteWiseTutorialDeviceRuleRole/9SUxG6SG is not authorized to perform: iotsitewise:BatchPutAssetPropertyValue on resource: /tutorial/device/SiteWiseTutorialDevice1/temperature because no identity-based policy allows the iotsitewise:BatchPutAssetPropertyValue action]. Message arrived on: $aws/things/SiteWiseTutorialDevice1/shadow/update/accepted, Action: iotSiteWise" } ] } ``` Any suggestion?

I wanted to ask how the LoRaWAN server filter (if at all) duplicate uplink messages that received by two or more GW and transmitted to the server.

Hi everyone, I am looking for information on how to disable or revoke the certificate of a thing in IoT Core and I have only found that it can be done from its API. - Is it possible to modify the state of a thing from the java sdk? - How can I, from java, communicate with the IoT Core API? Regards.

I'm trying to call IoT Data Plane from a browser (only from localhost) and I'm trying to authenticate the client using a certificate registered in IoT Core. I found some code examples where it's implemented by setting `requestHandler` in clientConfig: ``` this.client = new IoTDataPlaneClient({ region: 'us-east-1', endpoint: 'XXXXX.iot.us-east-1.amazonaws.com', requestHandler: new NodeHttpHandler({ httpAgent: agent, httpsAgent: agent }) }) ``` `NodeHttpHandler` is for backend use and for browser there's `FetchHttpHandler` (from "@aws-sdk/fetch-http-handler"), which does not allow setting up the agent. What's the best approach to implement certificate+key based authN in IoT from browser?

I have a manifest file which looks like : ``` { "Platform": { "os": "all" }, "Lifecycle": { "Setenv": { "ENDPOINT": "Test_endpoint" }, "Run": "docker rm core -f && docker rm A -f && docker rm B -f && docker rm C -f && docker-compose -f {artifacts:path}/docker-compose.yml up -d" }, "Artifacts": [ { "URI": "docker:D" }, { "URI": "s3://bucket/docker-compose.yml" }, { "URI": "docker:C" }, { "URI": "docker:B" }, { "URI": "docker:A" } ] } ``` and in docker compose file ``` service: image: "XXXXX.dkr.ecr.us-east-1.amazonaws.com/service-1.0:latest" container_name: service network_mode: host environment: AWS_GG_NUCLEUS_DOMAIN_SOCKET_FILEPATH_FOR_COMPONENT: ${AWS_GG_NUCLEUS_DOMAIN_SOCKET_FILEPATH_FOR_COMPONENT} SVCUID: ${SVCUID} AWS_CONTAINER_CREDENTIALS_FULL_URI: ${AWS_CONTAINER_CREDENTIALS_FULL_URI} AWS_CONTAINER_AUTHORIZATION_TOKEN: ${AWS_CONTAINER_AUTHORIZATION_TOKEN} AWS_REGION: ${AWS_REGION} AWS_IOT_THING_NAME: ${AWS_IOT_THING_NAME} ENDPOINT: ${ENDPOINT} depends_on: - core - ledservice - scannerservice volumes: - ${AWS_GG_NUCLEUS_DOMAIN_SOCKET_FILEPATH_FOR_COMPONENT}:${AWS_GG_NUCLEUS_DOMAIN_SOCKET_FILEPATH_FOR_COMPONENT} command: --uri localhost:4400 --port 9100 --name stow ``` But i am unable to retrieve the value of ENDPOINT in my docker container using System.getEnv("ENDPOINT") or print all the environment variable using printenv on SSH. Value being returned is 'ENDPOINT=' i.e. empty. What am i doing wrong here? because i could not find much references where Setenv is being used or how to use it using docker.

So I have some sensors that are sending MQTT data using the IOT Core to DynamoDB. However I note that there are always 2 messages(duplicates). I am using Select for the topic, set up a Rule as was needed,etc. ITs all working fine, except for the duplicates. I looked through the questions but didn't find an answer. Any suggestion to find the root cause appreciated. Regards 6/11/22 additional data Some additional info might be useful so I have provided it here. Rule query statement The source of the messages you want to process with this rule. Extract below............. SELECT state.reported.value as state_reported_value FROM '#' Using SQL version 2016-03-23 Actions Actions are what happens when a rule is triggered. Insert a message into a DynamoDB table Extract end................. Hope this helps in directing me. Regards

I'm getting error with TOO_MANY_REQUESTS code when requesting thing shadow in a server connection. I think this error is caused by a quota exceeds, but I don't know what is the specific quota. If it is the case, can anyone help me to understand what is the quota my server is exceeding? Bellow is the part of stack trace error ``` Caused by: com.amazonaws.services.iot.client.AWSIotException: TOO_MANY_REQUESTS at com.amazonaws.services.iot.client.core.AwsIotCompletion.get(AwsIotCompletion.java:213) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.amazonaws.services.iot.client.shadow.AwsIotDeviceCommand.get(AwsIotDeviceCommand.java:58) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.amazonaws.services.iot.client.shadow.AwsIotDeviceCommandManager.runCommand(AwsIotDeviceCommandManager.java:135) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.amazonaws.services.iot.client.shadow.AwsIotDeviceCommandManager.runCommandSync(AwsIotDeviceCommandManager.java:108) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.amazonaws.services.iot.client.shadow.AbstractAwsIotDevice.get(AbstractAwsIotDevice.java:93) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.amazonaws.services.iot.client.AWSIotDevice.get(AWSIotDevice.java:299) ~[aws-iot-device-sdk-java-1.3.4.jar!/:na] at com.kl.compatec.app.central.iot.service.impl.AwsCentralIoTServiceImpl.loadCentralShadow(AwsCentralIoTServiceImpl.java:78) [classes!/:1.0.0] ... 121 common frames omitted ```

I have been referred here by TI Support given that my issue seems to be caused by AWS Embedded C SDK. I am using CC3235S evaluation board. I have had success publishing, subscribing, and updating, Shadows/Topics but receiving JSON payloads from a published topic has been a challenge. I am setting breakpoints in my callback function, and they are never being hit, unless I set my timeout seconds to 0, which results in an immediate timeout. The callback is expected to be called upon Timeout, Rejected, or Accepted statuses. My thing/shadow/get/accepted Topic IS Publishing. The problem is that I'm unable to capture it into my Microcontroller. I also can tell you that my AWS Iot Core / Thing policies are not the problem. I have set my permissions as loose as possible for testing. I have Confirmed that the client IS Subscribing to the /shadow/get/rejected + /accepted topics, and I've confirmed that the Shadow is getting updated form my Device/Thing. I have tried: - Adding aws_iot_shadow_yield() / aws_iot_mqtt_yield() after my GET and UPDATE functions - Different timeouts - Setting persistent subscribe argument to true and false - Adjusting permissions then reverting them back to known good The Return Code always returns SUCCESS for all my aws functions within this routine, and during the GET function I have confirmed that the client IS Connected to AWS. My GET Function: ``` IoT_Error_t rcGS; rcGS = aws_iot_shadow_get(&client, AWS_IOT_MY_THING_NAME, getShadowCallback, NULL, 5, true); ``` My GET function Callback: ``` static void getShadowCallback(const char *pThingName, ShadowActions_t action, Shadow_Ack_Status_t status, const char *pReceivedJsonDocument, void *pContextData){ IOT_UNUSED(action); IOT_UNUSED(pContextData); IOT_UNUSED(pReceivedJsonDocument); IOT_UNUSED(pThingName); nop; // breakpoint if (SHADOW_ACK_TIMEOUT == status) { IOT_INFO("GET Timeout--"); } else if (SHADOW_ACK_REJECTED == status) { IOT_INFO("GET RejectedXX"); } else if (SHADOW_ACK_ACCEPTED == status) { IOT_INFO("GET Accepted !!"); GetFromAWS = true; }else{ IOT_INFO("Unknown Update Status"); } } ``` I appreciate any help. Thank you.

Hi, I am trying to follow the instructions in (https://docs.aws.amazon.com/iot/latest/developerguide/mqtt-based-file-delivery-managing.html) to create a stream for my application purpose. however, when following the instruction in the doc, I was stuck at trying to following step (https://docs.aws.amazon.com/cli/latest/reference/iot/create-stream.html), there's a json file as follows, how do I create this json file ? Thanks in advance. Contents of create-stream.json: ``` { "streamId": "stream12345", "description": "This stream is used for Amazon FreeRTOS OTA Update 12345.", "files": [ { "fileId": 123, "s3Location": { "bucket":"codesign-ota-bucket", "key":"48c67f3c-63bb-4f92-a98a-4ee0fbc2bef6" } } ] "roleArn": "arn:aws:iam:123456789012:role/service-role/my_ota_stream_role" } ```

Hi, I want to send data from AWS iot to influxdb cloud. In iot core, there is no influxdb rule. Is there any way to send data using a service like timestream for this problème ? Thanks in advance

As HSM we are using the microchip tech ATECC608A. We are using that in Greengrass v1 and it is properly working. Here is the configuration example: ``` "IoTCertificate": { "privateKeyPath": "pkcs11:object=device;type=private", "certificatePath": "file:///path-to-core-device-certificate/xxx.pem.crt" } ``` In this, we are giving certificatePath that is available on the device. but in Greengrass v2 we have to specify the certificateFilePath as "pkcs11:object=device;type=cert". Example config.yaml ``` certificateFilePath: "pkcs11:object=iotdevicekey;type=cert" privateKeyPath: "pkcs11:object=iotdevicekey;type=private" ``` So is there any way to use the on-device connection certificate path in "certificateFilePath" attribute or do I have to write connection certificate in chip?

I have created a component using GreengrassV2 and running multiple containers inside this component. Now, my requirement is to call API Gateway and fetch some data into one of the docker containers running on the local device inside the component. I am using "import com.amazonaws.auth.DefaultAWSCredentialsProviderChain;" for fetching the credentials but getting ``` 05:45:06.476 INFO - Calling API Gateway with request params com.amazon.spiderIoT.stowWorkcell.entities.ApiGatewayRequest@e958e637 Exception in thread "main" com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: [EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: To use assume role profiles the aws-java-sdk-sts module must be on the class path., com.amazonaws.auth.profile.ProfileCredentialsProvider@7c36db44: profile file cannot be null, com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@6c008c24: Failed to connect to service endpoint: ] at com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:136) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.getCredentialsFromContext(AmazonHttpClient.java:1269) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.runBeforeRequestHandlers(AmazonHttpClient.java:845) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:794) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:781) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:755) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:715) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:697) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:561) at com.amazon.spiderIoT.stowWorkcell.client.ApiGatewayClient.execute(ApiGatewayClient.java:134) at com.amazon.spiderIoT.stowWorkcell.client.ApiGatewayClient.execute(ApiGatewayClient.java:79) at com.amazon.spiderIoT.stowWorkcell.StowWorkcellService.startMQTTSubscriberForSortLocationEvents(StowWorkcellService.java:120) at com.amazon.spiderIoT.stowWorkcell.StowWorkcellService.onInitialize(StowWorkcellService.java:65) at com.amazon.spideriot.sdk.service.Service.run(Service.java:79) at com.amazon.spiderIoT.stowWorkcell.StowWorkcellServiceDriver.main(StowWorkcellServiceDriver.java:26) ``` My dependencyConfiguration looks like :- ``` { "aws.greengrass.TokenExchangeService": { "componentVersion": "2.0.3", "DependencyType": "HARD" }, "aws.greengrass.DockerApplicationManager": { "componentVersion": "2.0.4" }, "aws.greengrass.Cloudwatch": { "componentVersion": "3.0.0" }, "aws.greengrass.Nucleus": { "componentVersion": "2.4.0", "configurationUpdate": { "merge": "{\"logging\":{\"level\":\"INFO\"}, \"iotRoleAlias\": \"GreengrassV2TestCoreTokenExchangeRoleAlias\"}" } }, "aws.greengrass.LogManager": { "componentVersion": "2.2.3", "configurationUpdate": { "merge": "{\"logsUploaderConfiguration\":{\"systemLogsConfiguration\": {\"uploadToCloudWatch\": \"true\",\"minimumLogLevel\": \"INFO\",\"diskSpaceLimit\": \"10\",\"diskSpaceLimitUnit\": \"MB\",\"deleteLogFileAfterCloudUpload\": \"false\"},\"componentLogsConfigurationMap\": {\"LedService\": {\"minimumLogLevel\": \"INFO\",\"diskSpaceLimit\": \"20\",\"diskSpaceLimitUnit\": \"MB\",\"deleteLogFileAfterCloudUpload\": \"false\"}}},\"periodicUploadIntervalSec\": \"5\"}" } } } ``` Java code for using AWS credentials ``` public class APIGatewayModule extends AbstractModule { @Provides @Singleton public AWSCredentialsProvider getAWSCredentialProvider() { return new DefaultAWSCredentialsProviderChain(); } @Provides @Singleton public ApiGatewayClient getApiGatewayClient(final AWSCredentialsProvider awsCredentialsProvider) { System.out.println("Getting client configurations"); final com.amazonaws.ClientConfiguration clientConfiguration = new com.amazonaws.ClientConfiguration(); System.out.println("Got client configurations" + clientConfiguration); return new ApiGatewayClient(clientConfiguration, Region.getRegion(Regions.fromName("us-east-1")), awsCredentialsProvider, AmazonHttpClient.builder().clientConfiguration(clientConfiguration).build()); } } ``` I have been following this doc: https://docs.aws.amazon.com/greengrass/v2/developerguide/device-service-role.html My question is regarding everywhere in this document, it is mentioned that "AWS IoT Core credentials provider", what credentials provider should we use? Also, as mentioned in this doc we should use --provision true when "When you run the AWS IoT Greengrass Core software, you can choose to provision the AWS resources that the core device requires." But we started without this flag, how can this be tackled and is there any other document that provides reference to using credentials provider and calling API Gateway from AWS SDK Java. On SSH to docker, i could find that the variable is set ``` AWS_CONTAINER_CREDENTIALS_FULL_URI=http://localhost:38135/2016-11-01/credentialprovider/ ``` But unable to curl from docker to this URL, is this how this is suppose to work?

Hi, After making a change to a component's config and then deploying this via GG V2 deployment, how can I trigger the component to restart automatically so it picks up the new configuration? Many thanks in advance

I am using IOT grengrass to deploy lamda function for my IOT core device - Raspberry Pi 3. I have completed all the necessary steps regarding the same. While starting Daemon from raspbery pi 3 and deploying from AWS greengrass console (using group V1), i am getting this below error, "Deployment 6cc8251b-f006-44f6-bebc-050da8d84bd7 of type NewDeployment for group 4fd1b5be-8b43-4734-a805-266d7482b81a failed error: process start failed: failed to run container sandbox: container_linux.go:380: starting container process caused: exec: "/lambda/greengrassSystemComponents": stat /lambda/greengrassSystemComponents: no such file or directory" I using AWS IOTfor first time, so not sure why this error is comimg. Please help me. Thanks

I have a device with 2 modules which can connect to AWS IoT. They will never be connected at the same time, so I'm planning to use the same `clientId` for both modules. One of the modules is a leader and decides who should be connected: Leader (L) or Follower (F). The network connections they use might be of low quality. I'm wondering if it's possible to have a scenario like this: 1. (F) is connected but because of network issues it has to reconnect and sends CONNECT to IoT 2. (L) wants to take over the connection so tells (F) it takes over the connection. [(L) has high priority message to deliver and can't wait for ACK from (F) that it has disconnected] 3. (L) connects to IoT and sends CONNECT and receives CONACK 4. Network is slow and only now CONNECT sent by (F) arrives to IoT which knocks off (F) from IoT Is this scenario possible or IoT takes care of this (for instance using timestamp sent in requests)? I know that (L) can reconnect upon disconnection, but network might be slow/unreliable so it might introduce significant latency which I have to avoid.

I am considering using the mechanism described [here](https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html) to transfer data in chunks from a micro controller to AWS S3. If I need to cut my payload into 10 000 chunks (so that it fits in RAM) would that mean that i'll have to pay for 10 000 HTTP requests ? Thanks for your help, David.

I'm just now learning about the Basic Ingest feature which could be a great fit for our use case. We're interested primarily in LoRa Device -> Gateway -> AWS Wireless -> Basic Ingest -> Rule -> 3rd Party Application Where we're interested in getting the Lora encoded messages into the 3rd party application as quickly and cheaply as possible. Even considering doing the Lora payload decoding outside of AWS too. Basic Ingest seems to be a nice fit, but it's not clear how to properly utilize for Lora devices in AWS. For example, non-Lora devices allow you to specify the topic at the device level. Whereas Lora devices do not. Also, Lora Wireless Destinations are not clear on whether to specify the basic ingest topic (which calls the rule using `$aws/rules/basic_ingest_rule` OR to call a rule directly? I understand Basic Ingest is about bypassing the message broker to call rules directly, but which is the correct method? Should I use: **Enter a rule name** Enter the name of the rule or a rule/topic that will process the messages sent to this destination. (where the `basic_ingest_rule`rule is selected) or **Publish to AWS IoT Core message broker** If you need a publish/subscribe broker to distribute messages to multiple subscribers (where the topic is `$aws/rules/basic_ingest_rule`)

We just started implementing a dockerized greengrass v2 component, inspired by - https://github.com/awslabs/aws-greengrass-labs-local-web-server When we do "self._ipc_client: GreengrassCoreIPCClient = awsiot.greengrasscoreipc.connect()" we get the following error: ``` `"``14:07:51 - robot.system - INFO - Start Init IPC Traceback (most recent call last): File "/usr/local/bin/start-farm", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.10/site-packages/command/farm.py", line 139, in main mqtt: IPC = IPC(config, logger) File "/usr/local/lib/python3.10/site-packages/common/ipc.py", line 75, in __init__ self._ipc_client: GreengrassCoreIPCClient = awsiot.greengrasscoreipc.connect() File "/usr/local/lib/python3.10/site-packages/awsiot/greengrasscoreipc/__init__.py", line 65, in connect connect_future = connection.connect(lifecycle_handler) File "/usr/local/lib/python3.10/site-packages/awsiot/eventstreamrpc.py", line 449, in connect raise e File "/usr/local/lib/python3.10/site-packages/awsiot/eventstreamrpc.py", line 437, in connect protocol.ClientConnection.connect( File "/usr/local/lib/python3.10/site-packages/awscrt/eventstream/rpc.py", line 305, in connect _awscrt.event_stream_rpc_client_connection_connect( RuntimeError: 44 (AWS_ERROR_FILE_INVALID_PATH): Invalid file path." ` ``` Any idea where this comes from? Thanks !!

I'm looking for information on pricing of attribute-search/update operations of an IOT thing when fleet-indexing is DISABLED 1. where can I find the price of attribute search operation (i.e. using client.describe_thing())? 2. where can I find the price of attribute update operation (i.e. using client.update_thing())?

I'm trying to find a list of active topics in our account. During testing it's very difficult to understand what devices are publishing to which topics and how often. Worse, a device could be publishing to a random topic and could be billing for messages we can't find. It's a feature we've used heavily in other MQTT brokers like EMQX & HiveMQ. I think it would be a very useful feature to have a topic overview where all topics recently used in the broker are listed along with their volume of use. This would be especially useful for debugging topics when trying to define an application-wide topic schema. Perhaps there is a way to do this already?

Hi, Currently AWS MQTT connection is established using below link: https://docs.aws.amazon.com/freertos/latest/userguide/getting_started_espressif.html I can see the certificate expiry is in 2050 year through AWS console. I wanted to know: 1. Can this expiry period be changed to 2060 or 2040 or any other? 2. How to automate expiry check monitoring 3. How to renew certificates? Are new certificates required to be replaced? Please guide.

Hi All IOT core is showing that i have a duplicate clientId and so disconnects form my device the issue is i dont know how to locate the duplicate device is there a way to find what the other device is ... as i only know one at this point and as the clinetid is the imei number of the modem... it cannot be changed there are too many devices to delete and start again... so thats not an option

[this page](https://docs.aws.amazon.com/freertos/archive/202012.00/userguide/getting_started_espressif.html) explains how to easily connect. Does this also work with DevKitC-1 or only DevKitC-4? Does my specific devboard support quick connect and all the benefits listed [here](https://devices.amazonaws.com/detail/a3G0h0000077nRtEAI/ESP32-WROOM-32SE)? I don't have much experience, so any help would be greatly appreciated.

Hi, I'm using STM32WL55 Nucleo with MW_RADIO_VERSION: V1.2.0. I'm trying to follow the instruction in the YouTube "Get started with AWS IoT Core for LoRaWAN FUOTA" I can see my device and my GW registered up-to-date on the AWS Core IOT console After adding my device to a multicast group I don't see that the device is getting any data even though it is transmitting once every 30sec. The console show under the device status in the multicast section that the device is "Package attempting" Any idea what I'm doing wrong? Thanks Eyal

Hello, I'm creating a LoRaWAN FUOTA task and I'm trying to schedule it for now but I get an error: "The date entered must be greater than or equal to the current calendar date and not greater then 48 hours" For example, I'm doing this at May 29, 2022, 09:57:00 (UTC+0300) and I'm trying to enter May 29, 2022, 09:59 and I get this error. I assume it somhow connected to UTCC and day light saving but I did not understand how. As I'm doing testing of the FUOTA I need to activate the task now and not in a future time. Thanks, Eyal

I have a device which consists of 2 modules: one High-Power and one Low-Power. High-Power module is connected to the Iot, but if nothing is happening, it goes to ac stand-by mode and the Low-Power module wakes up and connects to IoT. High-power module is using `${thingName}` as `clientId` in MQTT client and I would like Low-Power module to use the same certificate as High-Power but different `clientId`. For High-Power I have a IoT `iot:Connect` policy with resource `arn:aws:iot:REGION:ACCOUNT_ID:client/${iot:Connection.Thing.ThingName}` and it works fine. For Low-Power I'd like to use `clientId` `${thingName}-low`. I tried setting up the `iot:Connect` policy as follows: `arn:aws:iot:REGION:ACCOUNT_ID:client/${iot:ClientId}` but client cannot connect. If a Certificate is attached to a Thing does it mean I can use **only** `clientId` == `${thingName}`? EDIT: When I attach the connect policy to the Device-Group - Lower-Power module CANNOT connect. When I attach the same policy directly to the Certificate, it CAN connect

I'd like to be able to publish a message to a topic, which name is build up dynamically based on one of the input values. I can access to the input already when setting up Transition Events, but can't find a way to interpolate the input value into the topic name. Suppose I have an input such as: $input.foo = bar Would like to use it in the topic name as: "my/topic/$input.foo", resulting into "my/topic/bar" Have tried all type of proposed substitution templates w/o success (https://docs.aws.amazon.com/iotevents/latest/developerguide/iotevents-expressions.html)

I tried connecting to AWS IoT using ESP32 with DTH11 sensor. After uploading the sketch to ESP32 and watching Serial monitor, I can see it connecting to WiFi and then it is taking for ever to connect to AWS. Here is the output: ``` 19:13:50.257 -> rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) 19:13:50.257 -> configsip: 0, SPIWP:0xee 19:13:50.257 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 19:13:50.290 -> mode:DIO, clock div:1 19:13:50.290 -> load:0x3fff0018,len:4 19:13:50.290 -> load:0x3fff001c,len:1216 19:13:50.290 -> ho 0 tail 12 room 4 19:13:50.290 -> load:0x40078000,len:10944 19:13:50.290 -> load:0x40080400,len:6388 19:13:50.290 -> entry 0x400806b4 19:13:50.689 -> Connecting to Wi-Fi 19:13:51.188 -> .....Connected to the WiFi network 19:13:53.182 -> Connecting to AWS IOT 19:13:53.581 -> ...................................................................................................................................................................................................... ``` I ran `openssl s_client -connect custom_endpoint.iot.aws-region.amazonaws.com:8443 -CAfile CA.pem -cert cert.pem -key privateKey.pem` with downloaded certificates from AWS to confirm that are fine and the handshake is happening. ``` SSL handshake has read 5529 bytes and written 1609 bytes Verification: OK ``` How could I debug further? Here is the sketch I am using... ``` #include "secrets.h" #include <WiFiClientSecure.h> #include <PubSubClient.h> #include <ArduinoJson.h> #include "WiFi.h" #include "DHT.h" #define DHTPIN 13 // Digital pin connected to the DHT sensor #define DHTTYPE DHT11 // DHT 11 #define AWS_IOT_PUBLISH_TOPIC "esp32/pub" #define AWS_IOT_SUBSCRIBE_TOPIC "esp32/sub" float h ; float t; DHT dht(DHTPIN, DHTTYPE); WiFiClientSecure net = WiFiClientSecure(); PubSubClient client(net); void connectAWS() { WiFi.mode(WIFI_STA); WiFi.begin(WIFI_SSID, WIFI_PASSWORD); Serial.println("Connecting to Wi-Fi"); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println("Connected to the WiFi network"); // Configure WiFiClientSecure to use the AWS IoT device credentials net.setCACert(AWS_CERT_CA); net.setCertificate(AWS_CERT_CRT); net.setPrivateKey(AWS_CERT_PRIVATE); // Connect to the MQTT broker on the AWS endpoint we defined earlier client.setServer(AWS_IOT_ENDPOINT, 8883); // Create a message handler client.setCallback(messageHandler); Serial.println("Connecting to AWS IOT"); while (!client.connect(THINGNAME)) { Serial.print("."); delay(100); } if (!client.connected()) { Serial.println("AWS IoT Timeout!"); return; } // Subscribe to a topic client.subscribe(AWS_IOT_SUBSCRIBE_TOPIC); Serial.println("AWS IoT Connected!"); } void publishMessage() { StaticJsonDocument<200> doc; doc["humidity"] = h; doc["temperature"] = t; char jsonBuffer[512]; serializeJson(doc, jsonBuffer); // print to client client.publish(AWS_IOT_PUBLISH_TOPIC, jsonBuffer); } void messageHandler(char* topic, byte* payload, unsigned int length) { Serial.print("incoming: "); Serial.println(topic); StaticJsonDocument<200> doc; deserializeJson(doc, payload); const char* message = doc["message"]; Serial.println(message); } void setup() { Serial.begin(115200); connectAWS(); dht.begin(); } void loop() { h = dht.readHumidity(); t = dht.readTemperature(); if (isnan(h) || isnan(t) ) // Check if any reads failed and exit early (to try again). { Serial.println(F("Failed to read from DHT sensor!")); return; } Serial.print(F("Humidity: ")); Serial.print(h); Serial.print(F("% Temperature: ")); Serial.print(t); Serial.println(F("°C ")); publishMessage(); client.loop(); delay(1000); } ``` I have referred following url [https://how2electronics.com/connecting-esp32-to-amazon-aws-iot-core-using-mqtt/]()

Hello, How can I ensure minimal impact on service availability (AWS IoT Greengrass Core Device) while deploying new/updated components? Is there a way to schedule these activities (e.g., maintenance windows)? The Greengrass device is not connect to any client-device, it is the actual device used by users and it may have severe impact on users if it goes down unexpectedly. Thank you, Yossi

Hello, The use case I have is this - There are two types of AWS IoT Greengrass V2 core devices that are implemented, which are connected (in the same private LAN network) in hub and spoke architecture. None of them are connected to client devices (Greengrass is being used because of its IPC and orchestration benefits): 1. [Spoke] AWS IoT Greengrass V2 core device is directly attached to a camera. The Video stream is sent to an Hub AWS IoT Greengrass V2 core device for ML processing (inference) that must be near-real time. 2. [Hub] AWS IoT Greengrass V2 core device that is processing and Fan-Out video streams: **A)** to ML inference interface (**local component of the hub**) **B)** to Kinesis Firehose (S3; to re-train the model) **C)** AWS Kinesis Video Stream (for human to view the video online) I have a couple of questions: 1. Is the architecture feasible? Make sense? 2. What is the best (performance and security wise) technology (open source, AWS component, protocol) to use in Spoke and Hub devices to send the video stream from the spokes to the hub (the video has to be high quality with minimal/no compression to keep the inference accuracy high)? 2. Can the Stream Manager component of AWS IoT Greengrass V2 core send (Hub) streams in fun-out mode (**e.g., to two different destinations concurrently, AWS Kinesis Firehose and AWS Kinesis Video Streams**)? Thank you, Yossi

Hello, I have a couple of questions about the [provisioning process](https://docs.aws.amazon.com/iot/latest/developerguide/provision-wo-cert.html) by either trusted user or provisioning claim: 1. If you do not want to put too much trust on the supplier, how would you provide it the ability to establish provisioning claim certificates so it can install them on the device during manufacturing? 2. If the device is delivered and then being reset to factory settings - how the device can be recovered if the provisioning claim certificate is expired/revoked? 3. If you choose to use the trusted-user approach, how would you connect to the device's local web server? More specifically how would you securely install TLS certificate for the device's local web server? 4. If the IoT device is Greengrass (V2) would it make more sense to use HSM Key (e.g., [USB A Yubico](https://www.yubico.com/il/works-with-yubikey/catalog/aws-iot-greengrass/)) just to support secure re-bootstrapping of the device (so it can load all the initial secrets/certificates/ssm-activation codes)?

I have followed the "Connect to AWS IoT" steps provided in AWS IOT (1.Register a device 2.Download a connection kit 3.Configure and test your device). When I tried to run the script, I am getting `No module named AWSIoTPythonSDK.MQTTLib` Environment: Platform: Linux Choose a AWS IoT Device SDK: Python More info: ``` user::~/Downloads/connect_device_package$ ./start.sh Downloading AWS IoT Root CA certificate from AWS... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1188 100 1188 0 0 7378 0 --:--:-- --:--:-- --:--:-- 7378 Cloning the AWS SDK... Cloning into 'aws-iot-device-sdk-python'... remote: Enumerating objects: 870, done. remote: Counting objects: 100% (135/135), done. remote: Compressing objects: 100% (77/77), done. remote: Total 870 (delta 71), reused 58 (delta 58), pack-reused 735 Receiving objects: 100% (870/870), 334.31 KiB | 1.92 MiB/s, done. Resolving deltas: 100% (423/423), done. Installing AWS SDK... ~/Downloads/connect_device_package/aws-iot-device-sdk-python ~/Downloads/connect_device_package Requirement already satisfied: AWSIoTPythonSDK in /home/om/.local/lib/python3.8/site-packages (1.4.9) ~/Downloads/connect_device_package Running pub/sub sample application... Traceback (most recent call last): File "aws-iot-device-sdk-python/samples/basicPubSub/basicPubSub.py", line 18, in <module> from AWSIoTPythonSDK.MQTTLib import AWSIoTMQTTClient ImportError: No module named AWSIoTPythonSDK.MQTTLib ```

Hi repost community, I'm looking to populate AWS IOT core device shadow in a lambda function. I'm looking to use Device Shadow REST API. After looking around, it looks like I need to add "Authorization" header myself. Then I looked into [documentation](https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html) which suggested me to look into AWS SDK. Finally I found [AWSIOTDataPlaneBuilder](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/iotdataplane/IotDataPlaneClientBuilder.html) which does have a bunch of shadow methods I need. But there's no documentations or example for this. 1. So what is AWSIOTDataPlaneBuilder? Is this supposed to be used? 2. if not, is any example for REST API calling to device shadow(from cloud with auth header)? All I found is MQTT examples.

**Gentlefolks, why is the the token exchange service (TES) failing to fetch credentials?** I have greengrass installed on Ubuntu 20.x.x running on a virtual machine. At the end of the numbered items is an error log (truncated) obtained from `/greengrass/v2/logs/greengrass.log`. Thank you What I've done or what I think you should know: 1. There exist `GreenGrassServiceRole` which contains `AWSGreengrassResourceAccessRolePolicy`, and every other policy containing the word "greengrass" in its name. It also has a trust relationship as below. This was created when I installed Greengrass, but I added additional policies. ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "greengrass.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "StringEquals": { "aws:SourceAccount": "<MY_ACCOUNT_NUMBER>" }, "ArnLike": { "aws:SourceArn": "<ARN_THAT_SHOWS_MY_REGION_AND_ACC_NUMBER>:*" } } }, { "Effect": "Allow", "Principal": { "Service": "credentials.iot.amazonaws.com" }, "Action": "sts:AssumeRole" } ] } ``` 2. `aws.greengrass.Nucleus` component is deployed with the following configuration update. The alias also exists. ``` { "reset": [], "merge": { "ComponentConfiguration": { "DefaultConfiguration": { "iotRoleAlias": "GreengrassV2TokenExchangeRoleAlias", "awsRegion": "us-east-1", "iotCredEndpoint": "https://sts.us-east-1.amazonaws.com", "iotDataEndpoint": "<ENDPOINT_OBTAINED_FROM_IOT_CORE_SETTINGS>" } } } } ``` 3. `aws.greengrass.TokenExchangeService` is deployed. 4. There's a custom component that uses the Greengrass SDK to publish to IoT Core. It has the following configuration update. ``` { "reset": [], "merge": { "ComponentDependencies": { "aws.greengrass.TokenExchangeService": { "VersionRequirement": "^2.0.0", "DependencyType": "HARD" } } } } ``` 5. There is an IoT policy from a previous exercise which attached to the core device (Ubuntu on virtual machine) certificate. It allows **all** actions. There's also another `GreengrassTESCertificatePolicyGreengrassV2TokenExchangeRoleAlias` which is associated with the thing's certificate. The policy allows `iot:AssumeRoleWithCertificate` **ERROR LOG BELOW** ``` 2022-05-21T21:07:39.592Z [ERROR] (pool-2-thread-28) com.aws.greengrass.tes.CredentialRequestHandler: Error in retrieving AwsCredentials from TES. {iotCredentialsPath=/role-aliases/GreengrassV2TokenExchangeRoleAlias/credentials, credentialData=Failed to get connection} 2022-05-21T21:08:38.071Z [WARN] (pool-2-thread-28) com.aws.greengrass.tes.CredentialRequestHandler: Encountered error while fetching credentials. {iotCredentialsPath=/role-aliases/GreengrassV2TokenExchangeRoleAlias/credentials} com.aws.greengrass.deployment.exceptions.AWSIotException: Unable to get response at com.aws.greengrass.iot.IotCloudHelper.getHttpResponse(IotCloudHelper.java:95) at com.aws.greengrass.iot.IotCloudHelper.lambda$sendHttpRequest$1(IotCloudHelper.java:80) at com.aws.greengrass.util.BaseRetryableAccessor.retry(BaseRetryableAccessor.java:32) at com.aws.greengrass.iot.IotCloudHelper.sendHttpRequest(IotCloudHelper.java:81) at com.aws.greengrass.tes.CredentialRequestHandler.getCredentialsBypassCache(CredentialRequestHandler.java:207) at com.aws.greengrass.tes.CredentialRequestHandler.getCredentials(CredentialRequestHandler.java:328) at com.aws.greengrass.tes.CredentialRequestHandler.getAwsCredentials(CredentialRequestHandler.java:337) at com.aws.greengrass.tes.LazyCredentialProvider.resolveCredentials(LazyCredentialProvider.java:24) at software.amazon.awssdk.awscore.internal.AwsExecutionContextBuilder.resolveCredentials(AwsExecutionContextBuilder.java:165) at software.amazon.awssdk.awscore.internal.AwsExecutionContextBuilder.invokeInterceptorsAndCreateExecutionContext(AwsExecutionContextBuilder.java:102) at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.invokeInterceptorsAndCreateExecutionContext(AwsSyncClientHandler.java:69) at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.lambda$execute$1(BaseSyncClientHandler.java:78) at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.measureApiCallSuccess(BaseSyncClientHandler.java:175) at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76) at software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45) at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56) at software.amazon.awssdk.services.s3.DefaultS3Client.getBucketLocation(DefaultS3Client.java:3382) at com.aws.greengrass.componentmanager.builtins.S3Downloader.lambda$getRegionClientForBucket$2(S3Downloader.java:134) at com.aws.greengrass.util.RetryUtils.runWithRetry(RetryUtils.java:50) at com.aws.greengrass.componentmanager.builtins.S3Downloader.getRegionClientForBucket(S3Downloader.java:133) at com.aws.greengrass.componentmanager.builtins.S3Downloader.getDownloadSize(S3Downloader.java:115) at com.aws.greengrass.componentmanager.ComponentManager.prepareArtifacts(ComponentManager.java:420) at com.aws.greengrass.componentmanager.ComponentManager.preparePackage(ComponentManager.java:377) at com.aws.greengrass.componentmanager.ComponentManager.lambda$preparePackages$1(ComponentManager.java:338) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.net.UnknownHostException: https at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797) at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1509) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1368) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1302) at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at jdk.internal.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at software.amazon.awssdk.http.apache.internal.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:80) at com.sun.proxy.$Proxy15.connect(Unknown Source) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at software.amazon.awssdk.http.apache.internal.impl.ApacheSdkHttpClient.execute(ApacheSdkHttpClient.java:72) at software.amazon.awssdk.http.apache.ApacheHttpClient.execute(ApacheHttpClient.java:253) at software.amazon.awssdk.http.apache.ApacheHttpClient.access$500(ApacheHttpClient.java:106) at software.amazon.awssdk.http.apache.ApacheHttpClient$1.call(ApacheHttpClient.java:232) at com.aws.greengrass.iot.IotCloudHelper.getHttpResponse(IotCloudHelper.java:88) ... 27 more 2022-05-21T21:08:38.073Z [ERROR] (pool-2-thread-28) com.aws.greengrass.tes.CredentialRequestHandler: Error in retrieving AwsCredentials from TES. {iotCredentialsPath=/role-aliases/GreengrassV2TokenExchangeRoleAlias/credentials, credentialData=Failed to get connection} ```

Hi, I am working through general LoRaWAN functions and applications as part of a larger IoT project. I'm having trouble connecting my gateway (Multitech Conduit) to AWS. I've gone through all the steps provided in the AWS help documentation and documentation from the manufacturer, including creating new Gateway Cert Manager permissions/roles (AWS steps here https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-rfregion-permissions.html). Still, when I try to add my gateway I get an error message saying that I do not have the correct permissions set to add a gateway. Has anyone run into this? Is there a way to associate the role/permission with my IAM account? or should it be set for the root account?

Hi, the framework given by AWS for ESP32-DevkitC based OTA MQTT is crashing when internet disconnects. During crash, 6 out of 5 retry for TLS attempts is seen in serial log. Please suggest how to overcome this. If any other info required please let me know.

HI, I have followed the instructions from : https://aws.amazon.com/premiumsupport/knowledge-center/aws-iot-core-jitp-setup/, and i have created a thing in the AWS IoT Core. But there is no shadow created in the Device Shadows -- Device Shadows (0)Info. How i can create also the Device Shadow with JITP Provision? Thanks.

Hello, I generated an MQTT client certificate using create-keys-and-certificate. The issuer of this certificate is: issuer= /OU=Amazon Web Services O=Amazon.com Inc. L=Seattle ST=Washington C=US is there any way to access that intermediate certificate and any other intermediate ones in the chain? I've checked all the certificates here: https://www.amazontrust.com/repository/ but unfortunately none of them is that one. thank you!

- I'm using Quectel modem BG95 with a host MCU to connect to AWS IoT core and publish to topics and subscribe to topics as well. - I used to get an error occasionally that closed the MQTT connection exactly while doing pub/sub operations and connection had to be re-established , but that was very rare. - However, since the last few days I have been running tests on multiple devices (using same IoT core endpoint) and have been getting this MQTT dis-connection on each pub or sub operation. I am attaching a log for review. - To me it seems a server side issue since I have tried it with multiple modems and previous versions of firmware. ``` [While publishing to topic] ;2022-05-08T02:29:41Z;28;-966233403;462863960;;RAK000121|-45,RAKTEST|-56 AT+QIDEACT=1 OK[ 2022-05-08T02:29:41Z ] [FARM_IP][INFO] MDM_SET_DEACTIVATE_PDP-else AT+QIACT=1 OK AT+QMTOPEN=0,"a5u9klmd2viw3z-ats.iot.us-west-1.amazonaws.com",8883 OK +QMTOPEN: 0,0 --- [Opening MQTT Connection] [ 2022-05-08T02:29:41Z ] [FARM_IP][INFO] Mqtt opened AT+QMTCONN=0,"0123qwer786" OK +QMTCONN: 0,0,0 --- [MQTT client connected] AT+QMTPUB=0,1,1,0,"fm/1011",72 --- [Publishing to the MQTT Topic] > ;2022-05-08T02:29:41Z;28;-966233403;462863960;;RAK000121|-45,RAKTEST|-56 OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] ``` ``` [While Subscribing to topic] AT+QMTSUB=0,1,"imei/get_logs",0 --- [Subscribing to the MQTT Topic] OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] [ ] [FARM_IP][INFO] Starting timer AT+QMTSUB=0,1,"imei/get_logs",0 --- [Subscribing to the MQTT Topic] OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] ```

As my understanding, there are two required steps. I think only 1) is ok. **Is this redundancy? ** 1) From AWS IoT core policies, grant access to cognito_identity_id ```shell aws iot attach-policy --policy-name 'myIoTPolicy' --target '<YOUR_COGNITO_IDENTITY_ID>' ``` 2) From Cognito side, attach AWSIoTDataAccess and AWSIoTConfigAccess to Cognito Authenticated Role

Hello, I am sending data using MQTT test client in AWS IoT. The data is showing up properly when I subscribe to the topic. I then wanted to send the data to DynamoDB using a rule. I created the rule and double checked everything: made sure the topics were the same, the rule and MQTT were in the same location (ie: u-west-1), i tried creating different roles when the first didn't work, and i double checked to make sure the attributes were spelled correctly in the MQTT message and DynamoDB table. Any help or additional troubleshooting methods will be greatly appreciated. Thanks.

Hi I was following this [AWS tutorial](https://aws.amazon.com/blogs/mobile/analyze-device-generated-data-with-aws-iot-and-amazon-elasticsearch-service/) but with my own sensor data. I've created the following IoT Core Rule OpenSearch Action: ``` OpenSearchTopicRule: Type: AWS::IoT::TopicRule Properties: TopicRulePayload: Actions: - OpenSearch: Endpoint: !Join ['', ['https://', !GetAtt OpenSearchServiceDomain.DomainEndpoint]] Id: '${newuuid()}' Index: sensors RoleArn: !GetAtt IoTOSActionRole.Arn Type: sensor_data Sql: SELECT *, timestamp() as ts FROM 'Greenhouse/+/Sensor/Status' ``` The IoTOSActionRole has propper es:ESHttpPut permission. But when I try to create an index with following command send from Postman that would match the `Type: sensor_data` attribute: ``` curl --location --request PUT 'https://search-iot***-avt***i.eu-west-1.es.amazonaws.com/sensors' \ --header 'Content-Type: application/json' \ --data-raw '{ "mappings": { "sensor_data": { "properties": { "ts": { "type": "long", "copy_to": "datetime"}, "datetime": {"type": "date", "store": true}, "deviceID": {"type": "text", "store": true}, "humidity": {"type": "integer", "store": true}, "temperature": {"type": "integer", "store": true}, "lux": {"type": "integer", "store": true}, "soil": {"type": "integer", "store": true} }}}' ``` I receive an error: ``` { "error": { "root_cause": [ { "type": "mapper_parsing_exception", "reason": "Root mapping definition has unsupported parameters: [sensor_data : {properties={datetime={store=true, type=date}, temperature={store=true, type=integer}, humidity={store=true, type=integer}, soil={store=true, type=integer}, deviceID={store=true, type=text}, lux={store=true, type=integer}, ts={copy_to=datetime, type=long}}}]" } ], "type": "mapper_parsing_exception", "reason": "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters: [...]", "caused_by": { "type": "mapper_parsing_exception", "reason": "Root mapping definition has unsupported parameters: [...}]" } }, "status": 400 } ``` I've tried removing the 'type' `"sensor_data"` attribute and that allowed me to create an index with that mapping, ``` { "acknowledged": true, "shards_acknowledged": true, "index": "sensors" } ``` and then index pattern in OpenSearch Dashboard, but what happens then is that the IoT Core Rule even though it gets triggered does not result in any data ingestion to the OpenSearch domain. So I guess IoT Core Action tries to send that data with type `sensor_data`but there's no corresponding type in OS. Additionally, when I open the Discovery tab in OS dashboard I get this notice: ``` "undefined" is not a configured index pattern ID Showing the default index pattern: "sensors*" (d97775d0-cc44-11ec-acd4-bf72aa2fd725) ``` I'm using the OpenSearch 1.2 (latest) version. Sample data: ``` { "deviceID": "Tomatoes", "Greenhouse": 1, "date": "05-05", "time": "09:35:39", "timestamp": 1651743339, "humidity": 60, "temperature": 33.3, "lux": 9133.333, "soil": 78 } ``` What PUT call I have to make to create a `sensor_data` type mapping in OS that would match the type specified in IoT Core OpenSearch Action Rule?

At current, my Greengrass core device (v2.5.5), is on my rasp 3b+ running normally with manual deployment from local/cloud. However, the IDT (version 4.5.3 with suite=GGV2Q_2.3.1) execution passed for 3/6 test cases as below only: ========== Test Summary ========== * Execution Time: 1m51s * Tests Completed: 6 * Tests Passed: 3 * Tests Failed: 3 * Tests Skipped: 0 ---------------------------------- Test Groups: * pretestvalidation: PASSED * version: PASSED * coredependencies: PASSED * mqtt: FAILED * component: FAILED ---------------------------------- Failed Tests: * Group Name: mqtt Test Name: mqttpubsub; Reason: Failed at 'my device is running Greengrass * Group Name: component Test Name: cloudcomponent; Reason: Failed at 'my device is running Greengrass' Test Name: localcomponent; Reason: Failed at 'my device is running Greengrass' ---------------------------------- **Is there further detail/meaningful info from these error log/code?** **I have tried to look into the log folder but nothing else there.** **I have attached all failed logs as below:** # localcomponent: - time="22:48:06+07:00" level=info msg=22:48:06.237 [localdeployment] [INFO] com.aws.greengrass.testing.features.LoggerSteps - Attaching thread context to scenario: 'A component is deployed locally using CLI' - time="22:48:06+07:00" level=info msg=22:48:06.238 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 4: 'my device is registered as a Thing' - time="22:48:08+07:00" level=info msg=22:48:08.085 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotPolicy in IotLifecycle - time="22:48:09+07:00" level=info msg=22:48:09.615 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IamPolicy in IamLifecycle - time="22:48:10+07:00" level=info msg=22:48:10.194 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IamRole in IamLifecycle - time="22:48:10+07:00" level=info msg=22:48:10.639 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotRoleAlias in IotLifecycle - time="22:48:10+07:00" level=info msg=22:48:10.837 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotPolicy in IotLifecycle - time="22:48:11+07:00" level=info msg=22:48:11.040 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotThingGroup in IotLifecycle - time="22:48:12+07:00" level=info msg=22:48:12.066 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotCertificate in IotLifecycle - time="22:48:12+07:00" level=info msg=22:48:12.466 [localdeployment] [INFO] com.aws.greengrass.testing.resources.AbstractAWSResourceLifecycle - Created IotThing in IotLifecycle - time="22:48:14+07:00" level=info msg=22:48:14.966 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 5: 'my device is running Greengrass' - time="22:48:14+07:00" level=info msg=22:48:14.976 [localdeployment] [ERROR] greengrass/features/localdeployment.feature - Failed at step: 'my device is running Greengrass' - time="22:48:14+07:00" level=info msg=com.google.inject.ConfigurationException: Guice configuration errors: - time="22:48:14+07:00" level=info msg=1) [Guice/ErrorInUserCode]: Unable to method intercept: GreengrassSteps - time="22:48:14+07:00" level=info msg= while locating GreengrassSteps - time="22:48:14+07:00" level=info msg=22:48:14.990 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 9: 'I create a Greengrass deployment with components' - time="22:48:14+07:00" level=info msg=22:48:14.990 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 11: 'I deploy the Greengrass deployment configuration' - time="22:48:14+07:00" level=info msg=22:48:14.991 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 12: 'the Greengrass deployment is COMPLETED on the device after 180 seconds' - time="22:48:14+07:00" level=info msg=22:48:14.991 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 13: 'I verify greengrass-cli is available in greengrass root' - time="22:48:14+07:00" level=info msg=22:48:14.991 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 14: 'I create a local deployment with components' - time="22:48:14+07:00" level=info msg=22:48:14.991 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 16: 'the local Greengrass deployment is SUCCEEDED on the device after 120 seconds' - time="22:48:14+07:00" level=info msg=22:48:14.991 [localdeployment] [INFO] greengrass/features/localdeployment.feature - line 17: 'the aws.greengrass.LocalHelloWorld log on the device contains the line "Hello World!!" within 20 seconds' - time="22:48:16+07:00" level=info msg=22:48:16.569 [localdeployment] [INFO] com.aws.greengrass.testing.features.LoggerSteps - Clearing thread context on scenario: 'A component is deployed locally using CLI' - time="22:48:16+07:00" level=info msg=22:48:16.577 [localdeployment] [ERROR] com.aws.greengrass.testing.launcher.reporting.StepTrackingReporting - Failed: 'A component is deployed locally using CLI': Failed at 'my device is running Greengrass' - time="22:48:16+07:00" level=info msg=22:48:16.584 [] [] [INFO] com.aws.greengrass.testing.modules.AWSResourcesCleanupModule - Cleaned up com.aws.greengrass.testing.resources.iam.IamLifecycle$$EnhancerByGuice$$10441879@e128dc2 - time="22:48:23+07:00" level=error msg=Test exited unsuccessfully error=exit status # cloudcomponent: - 2022-May-04 15:37:28,499 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 9: 'I create a Greengrass deployment with components' - 2022-May-04 15:37:28,499 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 11: 'I deploy the Greengrass deployment configuration' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 12: 'the Greengrass deployment is COMPLETED on the device after 180 seconds' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 13: 'the com.aws.HelloWorld log on the device contains the line "Hello World!!" within 20 seconds' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 15: 'I create a Greengrass deployment with components' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 17: 'I deploy the Greengrass deployment configuration' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 18: 'the Greengrass deployment is COMPLETED on the device after 180 seconds' - 2022-May-04 15:37:28,500 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] greengrass/features/cloudComponent.feature - line 19: 'the com.aws.HelloWorld log on the device contains the line "Hello World Updated!!" within 20 seconds' - 2022-May-04 15:37:31,557 [cloudComponent] [idt-b47156801aee3f29c860] [INFO] com.aws.greengrass.testing.features.LoggerSteps - Clearing thread context on scenario: 'As a developer, I can create a component in Cloud and deploy it on my device' - 2022-May-04 15:37:31,558 [cloudComponent] [idt-b47156801aee3f29c860] [ERROR] com.aws.greengrass.testing.launcher.reporting.StepTrackingReporting - Failed: 'As a developer, I can create a component in Cloud and deploy it on my device': Failed at 'my device is running Greengrass' # mqttpubsub: - 2022-May-04 15:36:55,929 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] greengrass/features/mqtt.feature - line 9: 'I create a Greengrass deployment with components' - 2022-May-04 15:36:55,931 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] greengrass/features/mqtt.feature - line 12: 'I deploy the Greengrass deployment configuration' - 2022-May-04 15:36:55,931 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] greengrass/features/mqtt.feature - line 13: 'the Greengrass deployment is COMPLETED on the device after 180 seconds' - 2022-May-04 15:36:55,931 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] greengrass/features/mqtt.feature - line 14: 'the aws.greengrass.IotMqttSubscriber log on the device contains the line "Subscribed to IoT topic idt/Mqtt/Test with QOS=AT_LEAST_ONCE" within 20 seconds' - 2022-May-04 15:36:55,931 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] greengrass/features/mqtt.feature - line 15: 'the aws.greengrass.IotMqttPublisher log on the device contains the line "Published to IoT topic idt/Mqtt/Test with payload test message and qos AT_LEAST_ONCE" within 10 seconds' - 2022-May-04 15:36:58,922 [mqtt] [idt-614fb227a4f0913ba4be] [INFO] com.aws.greengrass.testing.features.LoggerSteps - Clearing thread context on scenario: 'Component publishes MQTT message to Iot core and retrieves it as well' - 2022-May-04 15:36:58,924 [mqtt] [idt-614fb227a4f0913ba4be] [ERROR] com.aws.greengrass.testing.launcher.reporting.StepTrackingReporting - Failed: 'Component publishes MQTT message to Iot core and retrieves it as well': Failed at 'my device is running Greengrass' - 2022-May-04 15:36:58,930 [] [] [INFO] com.aws.greengrass.testing.modules.AWSResourcesCleanupModule - Cleaned up com.aws.greengrass.testing.resources.s3.S3Lifecycle$$EnhancerByGuice$$11137706@7e3ca22c

I am setting own mqtt broker using aws workshop: https://catalog.us-east-1.prod.workshops.aws/workshops/5ecc2416-f956-4273-b729-d0d30556013f/en-US/chapter6-mqtt-broker/10-step1 In startup.sh script execution step getting errors: 1. not authorized to perform: iot:CreatePolicy 2. not authorized to perform: iot:CreateKeysAndCertificate User account having all below access permissions: IAMFullAccess AmazonS3FullAccess AWSIoTFullAccess AWSGreengrassFullAccess GreengrassV2TokenExchangeRoleAcess AdministratorAccess I am trying to resolve this couple of days, but not yet succeeded . It very urgent need resolve for current project

I deployed a prototype AWS FreeRTOS device in the field last week and my message count appears way out. By my count I received nearly 5000 messages over mqtt. But according to my first bill that was 230,000 messages costing 23c - AWS IoT USW2-Messages. Am I doing something wrong? Is the cost really per character maybe? My average message length is about 50. Thanks in advance.

We installed Greengrass v2 on several EC2s that simulate edge devices. We subscribed to telemetry data from them as explained in the docs: https://docs.aws.amazon.com/greengrass/v2/developerguide/telemetry.html. We defined a very general rule on eventBridge using the default event bus and the following event pattern : { "source": ["aws.greengrass"] } We forwarded the events to a CloudWatch log group. However, we received almost no data. We notice that every time we restart the ec2, the first MQTT message is always received, but then, after a while (2-4 days), we didn't receive the messages anymore (even if we didn't change anything in the ec2 or in the Greengrass components). In the docs, it says that the telemetry agent tries to send an MQTT message every day with QOS 0, so some misses could be expected. But since we are using EC2, we assume to have an internet connection almost all the time and we expect to receive more telemetry messages. Why is this not happening? We received the expected messages only for 2/4 days. For instance, for the core device GGv2-CoreDevice, we received telemetry data on 2022-04-21 and 2022-04-22 and we didn't receive any message on the following days. Should we expect worse performance when we will use on-premise edges? IoT Greengrass Core software version: 2.5.5

I want to be bale to add a lot of devices automatically when they first activate and not one by one using the console or the API. I think I need to use OTAA but it is not clear to me how I can automate this process. I read [this ](https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-end-devices-add.html) but did not understand how to scale this. Thanks

Hello, i have been using aws iot jobs for sending custom jobs like restarting a service, rebooting a device or running a custom ota job like pulling from git. I have noticed that when i run the built binary of aws-iot-client manually from a shell with the job's config file it works when it recieves a custom ota job. But when the same binary with same config file is run from aws iot service it doesn't work. The job reports failed state with a message code exited with status code 1. Can you help me more on this. The update-software.sh file for ota handler is: ``` #!/usr/bin/env sh set -e echo "Running update-software.sh" user=$1 echo "Username: $user" if id "$user" 2>/dev/null && command -v "git" > /dev/null then echo "Starting the update command" . /home/pi/triton_software/update.sh else "Update failed!!" exit 1 fi echo "update-software command is done" ``` and the update.sh script which is being called is ``` #!/usr/bin/env sh cd /home/pi/amazon-kinesis-video-streams-producer-sdk-cpp; git pull origin main; cd build/; cmake -DBUILD_GSTREAMER_PLUGIN=TRUE ..; make; ``` Any help is appreciated, Thanks Subham

I already created post yesterday but I believe it is not visible hence asking again. We are on track to upgarde to GG V2 but before that we need to document the below cause. Your help will be highly appreciated. Have faced the following 3 issues in the past few weeks -->> My colleague stated that his deployment fails with error stating “Group definition is not valid”? I couldn't find anything in the GG troubleshooting document about the error. -->> I updated my group definition and added Lambdas to it but I don’t see that reflected on the device. Do the changes take place upon rebooting device ? is the deployment failed ? or the change made on cloud but never made to the device. -->> In the beginning I couldn't find error logs in my Green grass local machine, neither CloudWatch Thanks Community, looking forward to exploring GG. Joan.

Currently I am unable to publish data with custom own Mqtt broker to aws iot core. Whereas I am able to publish data to open MQTT server i.e broker.emqx.io. Is there any configuration need to be provide like, certification of AWS? Or access id and secrete key is enough?

When an IoT message is sent, via IPC channel (MQTT proxy), but greengrass is not connected to the internet, are the messages discarded? ``` accessControl: aws.greengrass.ipc.mqttproxy: com.savic.Telemetry:pub:0: policyDescription: Allows access to publish to telemetry topic operations: - aws.greengrass#PublishToIoTCore resources: - device/dev/telemetry/events - device/prod/telemetry/events ``` ``` try: op = ipc_client.new_publish_to_iot_core() op.activate(model.PublishToIoTCoreRequest( topic_name=TELEMETRY_TOPIC, qos=model.QOS.AT_LEAST_ONCE, payload=json.dumps(message).encode(), )) try: op.get_response().result(timeout=TIMEOUT) except: pass ``` Does GG keep them, then send them later, when there is connectivity, or is this something we have to handle in our component?

I have successfully created an IoT device and was able to make it work with Windows and Python SDK. I then wanted to see how the Java code worked so I selected Windows and the Java SDK and on this page https://us-east-2.console.aws.amazon.com/iot/home?region=us-east-1#/connectdevice/, clicked next and selected the device which I had already set up and have working in Python. I clicked Next Step and clicked the link to download the Java SDK. I extracted the Java SDK and started a windows Power Shell. I unzipped the downloaded SDK, changed directory to it, ran the change to the execution policy "Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process" and then ran start.ps1. The example fails to build with the error: > [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.373 s [INFO] Finished at: 2022-04-28T15:29:22-07:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project aws-iot-device-sdk-java-samples: Could not resolve dependencies for project com.amazonaws:aws-iot-device-sdk-java-samples:jar:0.0.1-dev: Could not find artifact com.amazonaws:aws-iot-device-sdk-java:jar:0.0.1-dev in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Any ideas how to fix this?

Have faced the following 3 issues in the past few weeks -->> My colleague stated that his deployment fails with error stating “Group definition is not valid”? I couldn't find anything in the GG troubleshooting document about the error. -->> I updated my group definition and added Lambdas to it but I don’t see that reflected on the device. Do the changes take place upon rebooting device ? is the deployment failed ? or the change made on cloud but never made to the device. -->> In the beginning I couldn't find error logs in my Green grass local machine, neither CloudWatch Thanks Community, looking forward to exploring GG. Joan.

I am attempting to update a thing shadow when a deployment completes with the components & versions that are installed on the device. The way it's set up now is: 1. An IoT rule that subscribes to `SELECT * FROM '$aws/events/jobExecution/+/succeeded'` and sends the message to a Lambda 2. The Lambda takes the event, calls the `listInstalledComponents` api from the Greengrass sdk, then calls the `updateThingShadow` with the components. However when the Lambda runs, the installed components that get updated in the shadow are not updated with the latest components. It's almost like the Lambda is run before the component listing is updated. I can see that the component listing in the AWS console updated as soon as the deployment is finished. I'm wondering if there's a better topic to watch, or if there's some other way to do what I need. Any guidance would be appreciated.

I'm interested in developing an application with Expresslink but I haven't seen any new information since the initial announcement. In addition, at least one of the development modules has been discontinued.

I'm interested in developing an application with Expresslink but I haven't seen any new information since the initial announcement. In addition, at least one of the development modules has been discontinued.

In IoT Core, it is strongly suggested to use a uniq certificate per device. Is using same cert across many devices less secure? Or simply loosing functionalities like Shadow, etc?

Seeing below error in GGConnManager.log - For the device -publisher, I used AmazonRootCA1.pem for rootCA. not sure why the connection error says unknow CA [ERROR]-MQTT message decoding error: unable to decode received MQTT message. {"errorString": "remote error: tls: unknown certificate authority"} Any help is appreciated

Hello all, I am extremely new to the AWS community as well as working with LoRa integrations. I have integrated my LoRa application to my AWS IoT core. I am now trying to republish specific data from my application into another topic. I followed a tutorial on youtube and created a Lambda function to grab that specific data. When I try to verify its functionality in the MQTT broker I get nothing ``` function Decoder(bytes, port) { var decoded = {}; var sensorRead = bytes[2] & 0x7f; var BatteryPerc = bytes[2] & 0x64; var Hour = bytes[2] & 0x00; var Min = bytes[2] & 0x64; var Sec = bytes[2] & 0x00; var lat = bytes[4] & 0x00; var lon = bytes[4] & 0x00; var alt = bytes[4] & 0x00; var time = ((Hour) + ":" + (Min) + ":" + (Sec)); var Sensor = ((sensorRead) / 240.0625); var Battery = ((BatteryPerc) / 256); decoded.Sensor = Sensor; decoded.Battery = Battery decoded.time = time; decoded.lat = lat; decoded.lon = lon; decoded.alt = alt; return decoded; } exports.handler = async (event) => { console.log(event); return { "device" : event.DeviceId, "payload" : Decoder(Buffer.from(event.PayloadData, 'base64'), 2) }; }; ``` this is my Lambda function. I have no idea how to fix my problem or what resources to read to help.

I am trying to connect a LoRaWan device (DRAGINO; RS485-LN converter) via Helium so that you (AWS) can monitor and graphically represent data from devices that communicate via modBus-RTU (RS485). In addition to "Access Key", "Secret Key", "Region" and "Topic" that Helium asks me to integrate AWS, what other data do I need and where is it for AWS to receive data from Helium? Could it be wrong that "Region = Global" and "Topic = AWS IoT MQTT"? What other parameters might be wrong or what am I missing for me to start communicating "Helium" with AWS?

Hi, We've been recently building a LoRaWAN solution using AWS IoT services and we've found that there are some missing features that would be very beneficial for developers: * Gateway status notifications (connected / disconnected), since this has already been inquired by another user in another post I won't go into detail here * Customization of the published uplink data. Currently the only customization available is to add Gateway Metadata which will depend on the Service Profile created, however in some use cases this information would be insufficient in order to easily handle uplink messages. Some additional information such as Device Profile and any defined Tags should be selectable to be included in the uplink message along with the payload and the gateway metadata, this could potentially simplify the data processing without having to query for those values specifically (using any of the available SDKs + Wirless Device Id which is already included in the uplink data) Thanks!

I'm using dynamoDB to save data from multiple devices and I noticed that only the last connected device that sends the data, never all simultaneous. Then I saw that it was because of the certificates and that I would have to register the devices one by one. But it turns out that I will use more than 10000 devices and it will be almost impossible to register one by one. So if I had a certificate that worked for all devices it would help a lot.

Hello, I am trying to create an IoT Rule that selects only the fields I need from a specified MQTT topic and republishes the message to another MQTT topic. The SQL query I am using is the following: ``` SELECT state.debug AS state.debug, state.command AS state.command, version FROM '$aws/things/my-thing/shadow/update/delta' WHERE state.debug <> '' OR state.command <> '' ``` When the selected SQL version is the latest (2016-03-23), the right operand of the WHERE clause is completely ignored and the rule is triggered only if the state.debug property has a value. When I change the SQL version to 2015-10-08, however, the rule works just fine. It seems that there is no breaking change on the way the two SQL versions handle logical operators, according to the AWS documentation. Therefore, is it possible that there is a bug with 2016-03-23 IoT SQL version or am I missing something else here?

Hello, We are using GreenGrass v2 and would like to have logs pushed as frequently as possible. We understand the limitation for certain components (eg telemetry) but our application logs should be sent as near real time as we can. Currently, regardless of the configurations set our logs are only sent intermittently to CloudWatch. Logs are seen every few hours or even few days. Could anyone please help us understand whats happening? We are using the following configuration: ``` 'aws.greengrass.Nucleus': { componentVersion: '2.4.0', configurationUpdate: { merge: `{ "logging" : { "level" : "DEBUG", "format" : "JSON" } }`, }, }, 'aws.greengrass.LogManager': { componentVersion: '2.2.1', configurationUpdate: { merge: `{ "logsUploaderConfiguration": { "systemLogsConfiguration": { "uploadToCloudWatch": "true", "minimumLogLevel": "DEBUG", "diskSpaceLimit": "2", "diskSpaceLimitUnit": "KB", "deleteLogFileAfterCloudUpload": "true" }, "componentLogsConfigurationMap": { "com.component1": { "minimumLogLevel": "DEBUG", "diskSpaceLimit": "2", "logFileDirectoryPath": "/greengrass/v2/logs/", "logFileRegex": "com.component1\\\\w*.log", "diskSpaceLimitUnit": "KB", "deleteLogFileAfterCloudUpload": "true" }, "com.component2": { "minimumLogLevel": "DEBUG", "diskSpaceLimit": "2", "logFileDirectoryPath": "/greengrass/v2/logs/", "logFileRegex": "com.component2\\\\w*.log", "diskSpaceLimitUnit": "KB", "deleteLogFileAfterCloudUpload": "true" }, "aws.greengrass.SageMakerEdgeManager": { "minimumLogLevel": "DEBUG", "logFileDirectoryPath": "/greengrass/v2/logs/", "logFileRegex": "aws.greengrass.SageMakerEdgeManager\\\\w*.log", "diskSpaceLimit": "2", "diskSpaceLimitUnit": "KB", "deleteLogFileAfterCloudUpload": "true" }, "aws.greengrass.SecureTunneling": { "minimumLogLevel": "DEBUG", "logFileDirectoryPath": "/greengrass/v2/logs/", "logFileRegex": "aws.greengrass.SecureTunneling\\\\w*.log", "diskSpaceLimit": "2", "diskSpaceLimitUnit": "KB", "deleteLogFileAfterCloudUpload": "true" } } }, "periodicUploadIntervalSec": "10" }`, }, }, ```

Hi, I'm starting as a developer and I have to use nodeJS as a way to send messages to connected devices in AWS IoT. I saw that the examples require that the nodejs code has device certificates such as: KeyPath, CertPath and CaPath. I put the data in the code and it worked normally, but in this case I am going to connect more than 1000 devices to AWS IoT and there will be no way to keep adding the certificates to the code, as there will be many devices. I wanted to know if there's anything I can do to get around this dilemma. Thank you! example: ` var device = awsIot.device({ keyPath: ''***********************************-private.pem.key', certPath: '***********************************-certificate.pem.crt', caPath: 'AmazonRootCA1.pem', clientId: 'esp32-device', region: 'sa-east-1', host: '************-ats.iot.sa-east-1.amazonaws.com', qos: 0 }) `

Hello, I have a question regarding cloud service types (IaaS, PaaS & SaaS). For an internship, the company I work at has asked me to look into a specific cloud solution. I wish to create a scalable IoT-capable cloud solution for customers. So in turn, I have done quite a bit of research on cloud/edge computing for the past few weeks. However, one thing still confuses me a little. If I used an IaaS cloud architecture, would I still be able to use services like AWS (IoT) analytics, or would this mean it isn't an IaaS architecture anymore? I looked all over, but I can't find an answer for this specific question. I hoped to find some IaaS/PaaS/SaaS cloud architecture diagrams to gain some clarity, but haven't found these. Could someone help me clarify this? Thank you very much!

I have enabled[ fleet indexing](https://docs.aws.amazon.com/en_us/iot/latest/developerguide/managing-index.html) with ["thing connectivity"](https://docs.aws.amazon.com/iot/latest/apireference/API_ThingConnectivity.html), however when I run a search on things using "search-index" all things come back as not connected. I can see on the AWS IoT Monitor Dashboard, using the "Metric type rate(%)" Pie Chart, that there are definitely "Connect" and "Ping" metrics. I have turned on debug logging in IoT and can search for logs in cloudwatch, but there are [no lifecycle events](https://docs.aws.amazon.com/iot/latest/developerguide/life-cycle-events.html) showing. Any suggestions for how to debug this further?

I have a bunch of things, each thing having multiple named shadows. I am interested in one specific named shadow when performing a search for things. When I perform a search, I get a random named shadow in the shadow property of the response. How can I control which shadow is returned? There is an example of the query I'm doing here https://docs.aws.amazon.com/iot/latest/developerguide/managing-index.html See **Querying a thing index**

Hi, Please provide the tutorials in greengrass v2 document related to publishing the messages to IoT core from an imported lambda using greengrass v2.

I am trying to create IoT x509 certificate not from AWS Console but using CloudFormation. According to [this document](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iot-certificate.html#aws-resource-iot-certificate-return-values) the cf template requires "certificatePem" as an input which I want cf output me this certificate. AWS CLI command ``` aws iot create-keys-and-certificate \ --set-as-active \ --certificate-pem-outfile esp-certificate.crt \ --public-key-outfile esp-public.key \ --private-key-outfile esp-private.key \ --region ap-southeast-1 ``` How to do the same thing with CloudFormation?

Hello, I recently onboarded one of 30 rpi's which acts like a streaming device using KVS ont aws iot Greengrass v2. I have tried with custom components and deploying them and all works fine but when i create a custom job like Amazon managed templates for rebooting the device, the greengrass is not recieving anything and the job stays in Queued State forever. I am trying to post a Snapshot type job. Any help is appreciated.

Trying to use provision by claim and provisioning hook to admit the device. The provisioning hook output will return a formatted thingName rather than the name passed into the provisioning hook, >const requestedThingName = input.parameters.ThingName; > >.... > const output = { allowProvisioning: True, parameterOverrides: { ThingName: newThingName, }, this works, but on the device side, after iot mqtt session successfully established, in /greengrass/v2/config/effectiveConfig.yaml, the file looks like this: >system: > >certificateFilePath: "" > >privateKeyPath: "" > rootCaPath: "" > rootpath: "/greengrass/v2" > >thingName: "" > >services: > >aws.greengrass.FleetProvisioningByClaim: > >configuration: I would expect, updated thingName is there under thingName key. I can only see the newThingName in config.tlog: {"TS":1649181903995,"TP":["setenv","AWS_IOT_THING_NAME"],"W":"changed","V":"newThingName"} I think effectiveConfig.yaml should be updated.

Hi, Is there any standard architectural pattern (with code sample) that I can use for monitoring real-time sensor data in a web app? I found this for monitoring real-time sensor data in mobile apps. https://aws.amazon.com/blogs/mobile/iot-with-aws-appsync/ Regards, Ashish

Using "Getting started with AWS IoT Core" to generate Python scripts. The basicPubSub.py sample script works fine. The Shadow examples, basicShadowDetailListener.py, basicShadowUpdater.py and ThingShadowEcho.py all get connection timeout exception when run. 2022-04-03 13:08:49,371 - AWSIoTPythonSDK.core.protocol.mqtt_core - ERROR - Connect timed out Traceback (most recent call last): File "/home/pi/connect_device_package/aws-iot-device-sdk-python/samples/basicShadow/basicShadowDeltaListener.py", line 110, in <module> myAWSIoTMQTTShadowClient.connect() File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/MQTTLib.py", line 1278, in connect return self._AWSIoTMQTTClient.connect(keepAliveIntervalSecond) File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/MQTTLib.py", line 520, in connect return self._mqtt_core.connect(keepAliveIntervalSecond) File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 199, in connect raise connectTimeoutException() AWSIoTPythonSDK.exception.AWSIoTExceptions.connectTimeoutException The IoT client and Shadow client appear to have the same connection configuration parameters # AWSIoTMQTTShadowClient configuration myAWSIoTMQTTShadowClient.configureAutoReconnectBackoffTime(1, 32, 20) myAWSIoTMQTTShadowClient.configureConnectDisconnectTimeout(10) # 10 sec myAWSIoTMQTTShadowClient.configureMQTTOperationTimeout(5) # 5 sec # AWSIoTMQTTClient connection configuration myAWSIoTMQTTClient.configureAutoReconnectBackoffTime(1, 32, 20) myAWSIoTMQTTClient.configureOfflinePublishQueueing(-1) # Infinite offline Publish queueing myAWSIoTMQTTClient.configureDrainingFrequency(2) # Draining: 2 Hz myAWSIoTMQTTClient.configureConnectDisconnectTimeout(10) # 10 sec myAWSIoTMQTTClient.configureMQTTOperationTimeout(5) # 5 sec

Our AWS account supports multiple private LoRaWAN networks (multi tenant- for different customers). When sending a downlink to a Class A Device using [SendDataToWirelessDevice](https://docs.aws.amazon.com/iot-wireless/2020-11-22/apireference/API_SendDataToWirelessDevice.html) Device ID is provided. Which Gateway(s) is this message dispatched to? Is it sent only to the Device's "Last connected gateway", or? I want to ensure downlinks destined for CustomerA do not broadcast to CustomerB's Gateways.

Hi. I have created a Greengrass fleet deployment workflow for my devices which works great - cloud resources are provisioned, claim certs are used to obtain device individual certs, and device gets connected. However in production environment the scenario will be different: 1. An IoT device is installed by an engineer in a newly built home, with no occupiers and no internet connection. 2. The Greengrass is ready to claim device certs and connect as soon as the device is powered up. 3. The device then is powered up by the installing engineer, meaning the Greengrass fleet provisioning plugin will try to do its job, but there is no internet connection, so it will fail. 4. The engineer will leave the device on, and it will be permanently on since now on. 5. The occupiers will move in some time later and install their broadband router, the Internet is now available. At this point, from my tests, I noticed the Greengrass/provisioning plugin won't detect Internet connection and won't try to register the device/obtain certs - meaning there is no retry functionality implemented. I understand that the device can be rebooted or Greengrass service restarted to initialize new registration attempt, however - if possible I'd like to avoid occupiers fiddling with the device, and prefer the device to the retry automatically. I also understand that I can write a software that will be automatically cyclically restarting the Greengrass service if the previous registration attempt failed (probably by checking if the thingCert.crt is present) but before I'll spend my time on coding, **the question is**: Is it possible to configure Greengrass to retry delayed provisioning using claim certificates if previous attempt has failed? Appreciate any help.

When I try to send a one byte message to my LoRa device that is connected to AWS IOT Wireless server I get a warning when I enter "1" in the Payload field and try to Submit that says: ``` Payload must follow pattern: ^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$ ``` This is under: AWS IoT > Wireless connectivity > Wireless devices > [Device ID] > Queue downlink message

I am trying to set up a simple service where I send messages from an edge device towards AWS IOT. AWS IOT then has a rule functionality (https://docs.aws.amazon.com/iot/latest/developerguide/iot-rules.html) that allows me to route that message towards a web app or service. I have managed to do is to send messages to a topic on AWS IOT Core and save them in a S3 Bucket. Now I am trying to set up a rule to route them to Telegram. I followed a Telegram Bot tutorial and obtained a link https://api.telegram.org/bot<bot token>/sendMessage?chat_id=<chat id>&text=<my message>. I have a bot token and chat id entered in. If I substitute <my message> with my personal message and add to that my browser, my telegram channel will get the message. I am trying to have custom messages to my telegram channel based on received messages on MQTT, AWS IoT Rules Engine requires a confirmation that I can access the data sent to that endpoint. The Rules Engine issues a challenge message to the specified endpoint with a token. If I can get the token and send that back to Rules Engine, then I can prove that I have access to the data on the receiving side, which would complete the confirmation process. The message has a format like this: HTTP POST {confirmationUrl}/?confirmationToken={confirmationToken} I am seriously confused how to verify that with the link from Telegram above. According to AWS, if you control that endpoint, you can simply look in your service logs for POST requests to that resource with the confirmationToken URI query, extract that token value, and paste it back into the AWS IoT console. I guess my main questions based on the telegram link I have above would be: 1. What is the HTTPS Endpoint I should enter for my rule action here? 2. What is the Confirmation Url I should enter for my rule action here? 3. How would I check for the confirmation token? I have no idea how to open the service log.

Hello I am working with IOT Wireless with LoRaWAN I have 868 MHz - Class C devices with confirmed messages. Messages are not always being actioned by my devices. I can see the message in the Downlink message queue. Its my understanding that if the message is confirmed it should either arrive at the device or there should be some indication it failed. I some times see the following CloudWatch Log: `{ "timestamp": "2022-03-21T07:44:03.2699141Z", "resource": "WirelessDevice", "wirelessDeviceId": "xxxxxxxxxxxxxxxxx", "wirelessDeviceType": "LoRaWAN", "devEui": "xxxxxxxxxxxxxxx", "event": "Downlink_Data", "logLevel": "ERROR", "messageId": "9114ba31-84af-44eb-ab1b-a92b67addbbb", "message": "Downlink message failed. MessageId: 9114ba31-84af-44eb-ab1b-a92b67addbbb" }` But why did it fail ? How can I find out more on what the cause is? In additon to this I have tried Multi-Cast but that also doesn't work with all devices stuck as: Package attempting Note I have tried the devices / gatways with TTN and I have no issues. Thank you JT

I'm using flutter/dart (mqtt_client / https://pub.dev/packages/mqtt_client) to send an AWS IOT MQTT messages over websockets and I'd like to restrict an IAM user to only specific topics that a user is allowed to Publish messages only to their specific topic. I've attempted to add some restricted policies, but the application will fail with little information on the client side. Also, in Cloud Watch, I don't see any specific errors. Here's some example topics: `arn:aws:iot:us-east-2:1234567890:topic/action_request/ASDF1234` `arn:aws:iot:us-east-2:1234567890:topic/action_request/ASDF5678` So, I want to add the proper JSON policy attached to the IAM user and they only have access to ASDF1234 All of my publish topics are patterned like the above. For now, I'm focusing on restricting the Publish endpoints and then working others like Subscribe. I've tried numerous different policies like below. Also with adding some wildcards to no success on the client side. They look right, but I'm not sure if there's indirectly other publish topics that are used internally within MQTT that's causing the failures or maybe just my syntax. Another thought is if I add a condition that would allow only the above endpoint and no others. https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "iot:Receive", "iot:ListNamedShadowsForThing", "iot:Subscribe", "iot:Connect", "iot:GetThingShadow", "iot:DeleteThingShadow", "iot:UpdateThingShadow" ], "Resource": "*" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "iot:Publish", "Resource": "arn:aws:iot:us-east-2:1234567890:topic/*/ASDF1234*" } ] } ```

Hi all, My MCU - ESP32 fails to reconnect only for subscribing after 3rd trial of reconnection so publishing is working fine. Is this a feature of AWS IoT Core or a bug of my ESP32?

When creating provisioning templates in AWS IoT Core you can attach a pre-provisioning hook. https://docs.aws.amazon.com/iot/latest/developerguide/pre-provisioning-hook.html I'm looking at onboarding devices using the JITP flow referenced here. https://docs.aws.amazon.com/iot/latest/developerguide/jit-provisioning.html There exist thing attributes that need to be populated at provisioning time. These attributes are not available to be encoded in the device certificate at manufacturing time. The attributes are used as part of the device policy and topic pattern in a multi-tenant solution to ensure no cross-contamination of data between customers. I would like to use a pre-provisioning hook to further augment the data available to the provisioning template. Is this possible? I understand that JITR is an option that would allow further augmentation but I would like to avoid having to manage the infrastructure necessary to support that approach.