By using AWS re:Post, you agree to the Terms of Use
/Internet of Things/

Internet of Things

There are billions of devices in homes, factories, oil wells, hospitals, cars, and thousands of other places. With the proliferation of devices, you increasingly need solutions to connect them, and collect, store, and analyze device data.

Recent questions

see all
1/18

Greengrass V2: LegacySubscriptionRouter component target LambdaNotFoundException

I have a Greengrass Lambda component subscribed to the `aws.greengrass.SNS` output topic `sns/message/status` using the `aws.greengrass.LegacySubscriptionRouter` component with the following configuration: ``` { "subscriptions": { "GreengrassSnsOutput": { "id": "GreengrassSnsOutput", "source": "component:aws.greengrass.SNS", "subject": "sns/message/status", "target": f"component:MyComponentName", } } } ``` That works as expected, but if I update the Lambda corresponding to `MyComponentName`, I get the following error message in the main Greengrass log file: ``` com.aws.greengrass.lambdamanager.LambdaNotFoundException: Lambda arn:aws:lambda:region:account:function:my-function-name:# does not exist ``` The [developer guide](https://docs.aws.amazon.com/greengrass/v2/developerguide/legacy-subscription-router-component.html#legacy-subscription-router-component-configuration) suggests that v2.1.0... >Adds support to specify component names instead of ARNs for source and target. If you specify a component name for a subscription, you don't need to reconfigure the subscription each time the version of the Lambda function changes. I took that to mean nothing needs to happen with respect to the subscription after a new component version with the same name but a new Lambda ARN is deployed. Is that right or is there something else that needs to be done? I'm using the following component versions: ``` "aws.greengrass.LegacySubscriptionRouter": { "componentVersion": "2.1.4" }, "aws.greengrass.Nucleus": { "componentVersion": "2.5.5" }, "aws.greengrass.SNS": { "componentVersion": "2.1.0" }, ```
1
answers
0
votes
4
views
asked 7 days ago

FTP Transfer Family, FTPS, TLS resume failed

We have: - an AWS transfer family server with FTPS protocol - a custom hostname and a valid ACM certificate which is attached to the FTP server - a Lambda for the Identity provider The client is using: - EXPLICIT AUTH TLS - our custom hostname - port 21 The problem is: the client can connect, the authentication is successfully (see below for the auth test result), but during the communication with the FTP server a TLS_RESUME_FAILURE occurs. The error in the customer client is "522 Data connection must use cached TLS session", and the error in the CloudWatch LogGroup of the transfer server is just "TLS_RESUME_FAILURE" I have no clue why this is happen. Any ideas? Here is the auth test result ``` { "Response": "{\"HomeDirectoryDetails\":\"[{\\\"Entry\\\":\\\"/\\\",\\\"Target\\\":\\\"/xxx/new\\\"}]\",\"HomeDirectoryType\":\"LOGICAL\",\"Role\":\"arn:aws:iam::123456789:role/ftp-s3-access-role\",\"Policy\":\"{\"Version\": \"2012-10-17\", \"Statement\": [{\"Sid\": \"AllowListAccessToBucket\", \"Action\": [\"s3:ListBucket\"], \"Effect\": \"Allow\", \"Resource\": [\"arn:aws:s3:::xxx-prod\"]}, {\"Sid\": \"TransferDataBucketAccess\", \"Effect\": \"Allow\", \"Action\": [\"s3:PutObject\", \"s3:GetObject\", \"s3:GetObjectVersion\", \"s3:GetObjectACL\", \"s3:PutObjectACL\"], \"Resource\": [\"arn:aws:s3:::xxx-prod/xxx/new\", \"arn:aws:s3:::xxx-prod/xxx/new/*\"]}]}\",\"UserName\":\"test\",\"IdentityProviderType\":\"AWS_LAMBDA\"}", "StatusCode": 200, "Message": "" } ```
1
answers
0
votes
7
views
asked 8 days ago

Memory leak with AWS C SDK released by ESP for ESP32C3 (example OTA mqtt) on Internet disconnection and reconnection

Hi All, We are working on ESP32C3 for OTA functionality using https://github.com/espressif/esp-aws-iot/tree/release/beta/examples/ota/ota_mqtt. We understood original C SDK from AWS side updated from ESP side to make it compatible to ESP32C3. As a part of testing, ESP32C3 is always connected to the Router over WiFi (Mobile Hotspot always ON). We are toggling the internet connection to the router.(**Mobile Data turned Off and ON**) We observed on every internet reconnection, there is memory leak of ~3KB. The memory leak used to get restored. But it take ~12 Min, ~17 Min, ~23Min. In one of the captured log, original free heap of 121828 get reduced to 118620 (~3K leak) after internet restore. After ~23 min, memory leak recovered to 121740. We are following with ESP for this issue. But we are getting little slow reply from ESP side. We have following observation, i) The AWS CSDK has WiFi disconnect event. But there is no event to handle Internet disconnect as we highlighted above - **Mobile Data turned Off and ON** ii) On WiFi disconnection and reconnection, memory leak not observed **Our queries/request:** i) If possible, we request AWS to replicate above testing on ESP32 device and share result. We are also trying to build code for ESP32 - mqtt OTA released from AWS side. We are getting some error. We are working on same. ii) Provide input from AWS side for memory leak observation. That will help to work on this issue further. **Did you came across the mentioned memory leak error in past? ** iii) Provide input on Internet disconnect event as we mentioned in observation 1 Thanks....
0
answers
0
votes
2
views
asked 10 days ago

MQTT Connection keeps getting disconnected/closed while publishing or subscribing to topics using LTE Modem

- 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] ```
1
answers
0
votes
7
views
asked 11 days ago

Popular users

see all
1/18

Learn AWS faster by following popular topics

1/1