# Change external IP of AWS Node **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [June 25, 2018, 1:48pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889 "2018-06-25T13:48:54Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![praveenperera](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/praveenperera/32/4102_2.png) [@praveenperera](https://forums.suse.com/u/praveenperera)\ **Post date:** [June 25, 2018, 1:48pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/1 "2018-06-25T13:48:54Z")
I am running a cluster with a single AWS node. This node restarted and now has a different IP address. Now rancher is showing it as unavailable "This cluster is currently Unavailable; areas that interact directly with it will not be available until the API is ready. Failed to communicate with API server: Get https://\:6443/api/v1/componentstatuses: waiting for cluster agent to connect" How do I change the IP? Also how can make sure new nodes on AWS gets created with an elastic IP? ---
**Author:** ![jeremyweber-np](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jeremyweber-np/32/4190_2.png) [@jeremyweber-np](https://forums.suse.com/u/jeremyweber-np)\ **Post date:** [July 3, 2018, 1:09am UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/2 "2018-07-03T01:09:28Z")
I had a similar question here [Expected behavior when a node gets a new IP](http://forums.suse.com/t/expected-behavior-when-a-node-gets-a-new-ip/10813) but no responses. ☹ ---
**Author:** ![cro](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/cro/32/3687_2.png) [@cro](https://forums.suse.com/u/cro)\ **Post date:** [July 7, 2018, 4:53pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/3 "2018-07-07T16:53:18Z")
Likewise. RancherOS 1.4, Rancher 2.0.4. I was trying to switch my nodes from dynamic to static DHCP and now my cluster is unavailable. This is concerning for the same reason @praveenperera noted–if I have nodes in the cloud and they reboot unexpectedly, how can I make sure they rejoin the cluster? ---
**Author:** ![sirwolfgang](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/sirwolfgang/32/4291_2.png) [@sirwolfgang](https://forums.suse.com/u/sirwolfgang)\ **Post date:** [July 13, 2018, 8:09pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/4 "2018-07-13T20:09:41Z")
I am running into this problem now, it breaks the rancher cli’s ssh as-well as heapster. I just tried to basically reimport the node with the following generated command, and it doesn’t seem to have an effect. This was based on a lot of older issues that talked about change the CATTLE\_AGENT\_IP. sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.0.4 --server [https://rancher.aquilacashflow.com](https://rancher.aquilacashflow.com) --token TOKEN --address IP\_ADDRESS --worker > > > Rancher Version: 1.0 > > Docker Version: 1.10.3 > > OS: Ubuntu 14.04.02 LTS > > Steps to …Reproduce: > \- Create a VM in Azure via Resource Manager > \- Add a dynamic public IP on it > \- Deploy an agent to an Host on Azure > \- Let it register en complete the task > (it will now show up in Rancher with IP X) > \- Shut down the host for a while > \- Start it up again... > (it will now have IP Y) > \- It will go from "reconnecting" to the "connected" state > > Results: > \- The IP in the console still shows IP X > \- VPN Connectivity is NOT possible anymore > > Expected: > \- Dynamically adjust IP address upon changes > > > Version - V0.14.1 > Steps to reproduce the problem: > > Add amazon host. > Create a con…tainer on this host and export port 8080. > > F0rom Amazon EC2 Dashboard , stop and start the host instance. > This results in a different public ip address being assigned the host. > > This results in Network Agent on this host being restarted. > I don't see the ipaddress of the host being updated on the rancher server. ---
**Author:** ![ml2](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@ml2](https://forums.suse.com/u/ml2)\ **Post date:** [July 25, 2018, 1:28pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/5 "2018-07-25T13:28:29Z")
Did you find a solution ? ---
**Author:** ![praveenperera](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/praveenperera/32/4102_2.png) [@praveenperera](https://forums.suse.com/u/praveenperera)\ **Post date:** [July 25, 2018, 7:59pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/6 "2018-07-25T19:59:34Z")
I tried a bunch of things, but ultimately I was unable to find a solution. I ended remaking the cluster again. I had some older backups of the YAML files which made things a little easier. Now I don’t run it with a single node, I run a 3 node cluster. So if one of the node’s IP changes I will remove it and rancher will automatically launch a new node. PS: digitalocean has a better elastic IP system, they allow you to make nodes current IP “elastic” instead of having to assign it a new IP ---
**Author:** ![ml2](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@ml2](https://forums.suse.com/u/ml2)\ **Post date:** [July 25, 2018, 8:33pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/7 "2018-07-25T20:33:40Z")
That what I was thinking I could do. The problem I had was that since it was a dev server, it was stopped for a comple of days and all the ips were changed so I coundn’t do a rollover. ---
**Author:** ![praveenperera](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/praveenperera/32/4102_2.png) [@praveenperera](https://forums.suse.com/u/praveenperera)\ **Post date:** [July 26, 2018, 3:11pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/8 "2018-07-26T15:11:33Z")
I guess you could create the nodes manually in EC2, attach the elastic IPs and then do a custom rancher deployment. ---
**Author:** ![francesco2013](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/francesco2013/32/4611_2.png) [@francesco2013](https://forums.suse.com/u/francesco2013)\ **Post date:** [November 9, 2018, 12:04pm UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/9 "2018-11-09T12:04:07Z")
Could you please specify what you mean for “custom rancher deployment” ? Could you please give steps ? I have exactly the same problem if a node goes down and then back up with a new IP from EC2 Rancher does not realize it. I mean guys these are big bugs including the one where you cannot manage in any way to connect to the ECR repository and pull images from there. Is this product ready for production ? Are we sure ? It looks to me it is full of bugs but big and potentially very dangerous to be used in a production environment. I am not really willing to put my company in the hands of a product that basically is a little more than a beta … ---
**Author:** ![junder](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/junder/32/5724_2.png) [@junder](https://forums.suse.com/u/junder)\ **Post date:** [October 28, 2019, 11:32am UTC](https://forums.suse.com/t/change-external-ip-of-aws-node/10889/10 "2019-10-28T11:32:05Z")
Hi, I have some success with amazon eip. After creating my cluster in rancher, assign an eip to your nodes in the aws console. Then navigate to the nodes tab in rancher and edit the node you just gave an eip to by assigning the `rke.cattle.io/external-ip` value to your eip: ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/6/65fd1e983251c9838604419263279c007082fdf0.png)