# Agent options (--internal-address) in aws node pool

**URL:** <https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128>\
**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:** 1\
**Showing post:** 3

<div class="post-metadata">

**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")

</div>

> [@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 \<node\_name\> and changing the address to ExternalIP however after saving it is changed back immediately.

Does this resemble your problem?

---

_[View the full topic](https://forums.suse.com/t/agent-options-internal-address-in-aws-node-pool/16128)._