# Node-Red: Unexpected connection to amazonaws.com
**URL:** https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093
**Category:** General
**Created:** [23 December 2018 15:36 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093 "2018-12-23T15:36:16Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@John](https://discourse.nodered.org/u/John)
#### Post date: [23 December 2018 15:36 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/1 "2018-12-23T15:36:16Z")
Hi,
I have been running node-red on my raspberry pi for some time now just doing some basic stuff. It is all supposed to be within my private LAN so I was surprised to see a connection to an Amazon node:
$ sudo netstat -pant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
...
tcp 0 0 192.168.5.87:51654 34.236.123.240:1883 ESTABLISHED 215/node-red
host 34.236.123.240
240.123.236.34.in-addr.arpa domain name pointer [ec2-34-236-123-240.compute-1.amazonaws.com](http://ec2-34-236-123-240.compute-1.amazonaws.com).
I did tcpdump on it and my Node-Red is sending a packet about once a minute.
I don't have any flows that should involve outside servers. Is this normal? Is there a way to configure it not to do this?
My version is a bit old now 0.17.4
Thanks,
John
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [23 December 2018 15:42 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/2 "2018-12-23T15:42:26Z")
This is not something Node-RED is doing by itself. What additional node modules have you installed?
---
### Author:  [@ghayne](https://discourse.nodered.org/u/ghayne)
#### Post date: [23 December 2018 15:44 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/3 "2018-12-23T15:44:49Z")
Are you using any Alexa nodes?
---
### Author:  [@John](https://discourse.nodered.org/u/John)
#### Post date: [23 December 2018 16:13 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/4 "2018-12-23T16:13:21Z")
I am not using Alexa or anything that I think should require a connection outside. It is receiving mqtt from a few nodes inside my house.
I think the only extra I added was:
node-red-contrib-sqldbs
node-red-dashboard
Thanks for the replies.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [23 December 2018 17:27 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/5 "2018-12-23T17:27:05Z")
could you open a terminal window and enter `ls -d /home/pi/.node-red/node_modules/node-red*` and post the results
---
### Author:  [@John](https://discourse.nodered.org/u/John)
#### Post date: [23 December 2018 17:41 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/6 "2018-12-23T17:41:07Z")
Sure:
$ ls -d /home/pi/.node-red/node\_modules/node-red\*
/home/pi/.node-red/node\_modules/node-red-dashboard
Thanks
---
### Author:  [@John](https://discourse.nodered.org/u/John)
#### Post date: [23 December 2018 18:14 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/7 "2018-12-23T18:14:03Z")
I figured it out. It was for thingspeak which I tried out a while back. I had deleted all the nodes related to it in my flows but it still showed up as unused under the "all flows" tab. After I deleted it the connection went away.
Thanks,
John
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [23 December 2018 18:15 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/8 "2018-12-23T18:15:39Z")
Oh good. Now that you have figured it out, you should think about upgrading to 0.19.5...(backup your SD card first)
---
### Author:  [@John](https://discourse.nodered.org/u/John)
#### Post date: [23 December 2018 23:22 UTC](https://discourse.nodered.org/t/node-red-unexpected-connection-to-amazonaws-com/6093/9 "2018-12-23T23:22:34Z")
Done. Went smoothly. I will have to check what is new.