# Agent options (--internal-address) in aws node pool **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [December 20, 2019, 7:30pm UTC](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128 "2019-12-20T19:30:29Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![michal.behun](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/michal.behun/32/5359_2.png) [@michal.behun](https://forums.suse.com/u/michal.behun)\ **Post date:** [December 20, 2019, 7:30pm UTC](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128/1 "2019-12-20T19:30:30Z")
Hello. Is it possible to pass --internal-address option to agent to register on node pool created on AWS? I tried to set Use only private IP address in node template but nodes failed to provision (docker install) due to lack of internet conectivity. Problem is when node shuts down and change its public IP address. Setting agent for using internal address will solve this problem. We run rancher server in our datacentre and was able to create custom cluster from manualy created EC2 machines. Thank you for your answers. Best regards, Michal Behun ---
**Author:** ![michal.behun](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/michal.behun/32/5359_2.png) [@michal.behun](https://forums.suse.com/u/michal.behun)\ **Post date:** [January 6, 2020, 2:11pm UTC](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128/2 "2020-01-06T14:11:56Z")
Is there any way to set this behavior? Maybe ENV variable set beforehead? ---
**Author:** ![Akito](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/akito/32/5805_2.png) [@Akito](https://forums.suse.com/u/Akito)\ **Post date:** [January 6, 2020, 2:32pm UTC](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128/3 "2020-01-06T14:32:16Z")
> [@Rancher Agent force public/external IP](http://forums.suse.com/t/rancher-agent-force-public-external-ip/10360): > > is there anyway to force rancher agent to register a node only using the public/external IP? one or more of my nodes are on a separate network and cant communicate using InternalIP I have tried setting --address & --internal-address in every combination. Have also tried editing the node directly with kubectl edit node \ and changing the address to ExternalIP however after saving it is changed back immediately. Does this resemble your problem? ---
**Author:** ![michal.behun](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/michal.behun/32/5359_2.png) [@michal.behun](https://forums.suse.com/u/michal.behun)\ **Post date:** [January 6, 2020, 6:54pm UTC](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128/4 "2020-01-06T18:54:45Z")
not exactly. we tried custom nodes created from EC2 VMs and `--internal-address aws-local` agent parameter set nodes correctly. my problem is when I let rancher to provision nodes automatically via node pool. so I need some way to set this parameter when node pool create EC2 node