13 ms·

Not to detract from what you're saying about IPv6: support there is key. Azure and AWS both support IPv6. That said, Azure charges for IPv4 external IPs. AWS d

Not to detract from what you're saying about IPv6: support there is key. Azure and AWS both support IPv6. That said, Azure charges for IPv4 external IPs. AWS does not, but I'd be surprised if the cost wasn't internally associated with ELB/ALB, EC2 instances, or other products. That is, you're still paying for it.

omeid2 7y ago
Sure, you're paying for everything you use, but the difference is when you compare costs. The less "addons" you need, the more true is the cost.
ben509 7y ago
While elastic IPs are free for an active instance, AWS does charge for unused EIPs[1]. (You can also set a public IP on an instance, but it can change when the instance is restarted.) So if you need to hold on to an IPv4 address, it's going to cost you. That seems like it's exactly the same model as GCP. [1]: https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/ https://aws.amazon.com/premiumsupport/knowledge-center/elast...
- alexeldeib 7y ago
  It won't be the same, right? Per the article, GCP will be charging on active instances.
  - unionpivo 7y ago
    No they will charge you for addresses you don't use. Which makes perfect sense imo.
    - cowsandmilk 7y ago
      > No they will charge you for addresses you don't use. No, that is what they currently do. Starting January 1, 2020, they will charge you for addresses on active instances. Current: Static IP address (assigned but unused) $0.010/hr Starting January 1, they add: Static and ephemeral IP addresses in use on standard VM instances $0.004/hr Static and ephemeral IP addresses in use on preemptible VM instances $0.002/hr
  - ben509 7y ago
    Oh, derp, I must have skipped past the article to the GCP page.
    - alexeldeib 7y ago
      Not sure if I'm just misunderstanding you -- by "article" I mean "GCP documentation page", which for completeness states: "Static and ephemeral IP addresses in use on standard VM instances *Starting January 1st, 2020, you will be charged $0.004 per hour."

omeid2 7y ago

Sure, you're paying for everything you use, but the difference is when you compare costs. The less "addons" you need, the more true is the cost.

ben509 7y ago

While elastic IPs are free for an active instance, AWS does charge for unused EIPs[1]. (You can also set a public IP on an instance, but it can change when the instance is restarted.) So if you need to hold on to an IPv4 address, it's going to cost you. That seems like it's exactly the same model as GCP. [1]: https://aws.amazon.com/premiumsupport/knowledge-center/elastic-ip-charges/ https://aws.amazon.com/premiumsupport/knowledge-center/elast...

alexeldeib 7y ago
It won't be the same, right? Per the article, GCP will be charging on active instances.
- unionpivo 7y ago
  No they will charge you for addresses you don't use. Which makes perfect sense imo.
  - cowsandmilk 7y ago
    > No they will charge you for addresses you don't use. No, that is what they currently do. Starting January 1, 2020, they will charge you for addresses on active instances. Current: Static IP address (assigned but unused) $0.010/hr Starting January 1, they add: Static and ephemeral IP addresses in use on standard VM instances $0.004/hr Static and ephemeral IP addresses in use on preemptible VM instances $0.002/hr
- ben509 7y ago
  Oh, derp, I must have skipped past the article to the GCP page.
  - alexeldeib 7y ago
    Not sure if I'm just misunderstanding you -- by "article" I mean "GCP documentation page", which for completeness states: "Static and ephemeral IP addresses in use on standard VM instances *Starting January 1st, 2020, you will be charged $0.004 per hour."