- 最新
- 投票最多
- 评论最多
You can use an Elastic IP if you want, as it's free to have one associated with your instance. You're only charged for >1 on an instance or for ones that are unassociated.
When you configure the DHCP server on your EC2 instance, you can use the EC2 instance's public IPv4 address as the default gateway. This should work with the configured IP helper address from your local router.
note 1 : such configurations are not recommended
note 2: You do not need to worry about AWS only routing unicast, as DHCP requests and responses are unicast messages.
I know it's not recommended, but in my case it must be free so i cant use any utility to secure that connection, I can use only security group to set some rules, for example inbound/outbound rule only for my local router's public IP.
相关内容
AWS 官方已更新 2 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
I didn't know that. I assigned public IP within creation of instance. Also, I'll be using only 1 instance so I will not use that elastic IP's potential. Or is there any advantage by using that elastic IP?
The purpose of an Elastic IP is to get a public IP address that doesn't change on instance restart. If you're relying on the instance having a specific IP because something else is referring to it, then use an Elastic IP.