- Newest
- Most votes
- Most comments
Hi, IoT Greengrass promotes a different approach: secure tunnelling over MQTT. See https://docs.aws.amazon.com/greengrass/v2/developerguide/secure-tunneling-component.html Is it unapplicable to your use case? Didier
Hi Luke, Have you launched a Localproxy in your local source machine? Scure tunneling needs a Local Proxy software to be able to get up the tunnel and allows you reach greengrass from your local computer terminal. In the following link you could find a workshop whereyou could download a local proxy made in C with the steps to get it configured. https://catalog.us-east-1.prod.workshops.aws/workshops/6d30487a-48e1-4631-b6bc-5602582800b5/en-US/chapter7-securetunelling/20-dc-setup
Hi, if you are using the Secure Tunneling Greengrass component, the logs will be found in /greengrass/v2/logs/aws.greengrass.SecureTunneling.log, not /greengrass/v2/logs/greengrass.log
Please check if you can find info helpful for debugging there.
Relevant content
- asked 7 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 10 months ago
So I can successfully create a secure tunnel over MQTT and SSH login via username and password to the device using the AWS IoT Console; however, the option to login via private key does not work. Even with my same private key which works logging in over local network (public key is in .ssh/authorized_keys).
I hope this helps clarify.