3 ms·
You can bring your own IP range or pay for an elastic IP. Isn't this how folks do this (I do!). You get a bunch of elastic IPs, you point your domains to those
by thoraway1010 6y ago
You can bring your own IP range or pay for an elastic IP. Isn't this how folks do this (I do!).
You get a bunch of elastic IPs, you point your domains to those, you point those to your instances.
That's secure, no one can use those IPs until you release them. Is this rocket science? On AWS I don't think you really get charged for this even (or very little) from what I can tell if you have them all pointing to your instances.
- thanksforfish 6y agoYup. Used elastic IP addresses are mostly free[1]. Unused elastic IP addresses are $0.005/hr[2]. Although watch the remapping fee... $0.1 per remapping past the first 100. That could add up. [1] https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/ https://aws.amazon.com/premiumsupport/knowledge-center/elast... [2] https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Addresses https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Add...
- kstrauser 6y agoThat would go a long way, but note that AWS limits you to 5 IPs per account per region[0] by default, and charge[1] $0.005 per Elastic IP per hour for EIPs that aren't attached to a running instance, and $0.10 to transfer an EIP from one instance to another. So, if you want to keep 1,000 EIPs around to map to ephemeral VMs, and you're not actively using them, you'll be paying $3,600 per month for those alone. One could argue that this is pocket change for a large customer to do the right them, but from a PM's perspective that $40K per year they could be spending towards another engineer's salary. [0] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-limit https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-... [1] https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Addresses https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Add...