Hi, We are using an remote connectivity application to managed unattended devices. (Gotoresolve). Apparently, it connects to AWS IoT public endpoints, which they do not advertise in their documentation. One day everything dropped offline, and it turns out our company implemented internal endpoints for AWS IoT service with matching Route53 records because we have a lot of IoT devices and want to keep that data secure. Which of course, started forcing our GoToResolve traffic to address ranges they don't have access too. Would be nice if we could keep GoToResolve traffic external, and actual IoT data internal... Working with the vendor or course right now - but they aren't terribly helpful. Anyone have this issue or something similar before? There are a bunch or ways to fix this (give access to internal IoT endpoints, use public DNS servers for our devices....) - just looking for the best one. submitted by /u/Cullingsong [link] [comments]