Hey Tomas,

I was just setting up everything in the IoT console for Greengrass and couldn't detect any connection from my core device, so I ssh'd into the core and checked the logs and noticed it was failing to get a broker connection. From the logs the config is stated as:

[2020-01-22T00:43:37.52Z][DEBUG]-CoreThing Connection Config:
{
"Region": "us-east-1",
"ThingArn": "arn:aws:iot:us-east-1:753958714070:thing/Balena_Core",
"IoTMQTTEndpoint": "a2n7ue1pyspgxx-ats.iot.us-east-1.amazonaws.com:8883",
"IoTHTTPEndpoint": "a2n7ue1pyspgxx-ats.iot.us-east-1.amazonaws.com:8443",
"GGMQTTPort": 8883,
"GGHTTPEndpoint": "greengrass-ats.iot.us-east-1.amazonaws.com:8443",
"GGMQTTKeepAlive": 600,
"GGMQTTMaxConnectionRetryInterval": 60,
"GGMQTTConnectTimeout": 30,
"GGMQTTPingTimeout": 30,
"GGHTTPTimeout": 60,
"FIPSMode": false,
"CoreClientId": ""
}

...which is very odd, because that's not what is in the .tar file in the downloads folder which I just pushed to the device.

Could this be using a casched version (I was using east-1 yesterday, but today I'm using west-2), and if so how would I clear that?

Thanks,
Paul