3 ms·

It's pretty galling for AWS to ask their customers "to be a bit more frugal with your use of public IPv4 addresses and to think about accelerating your adoption

by zokier 3y ago

It's pretty galling for AWS to ask their customers "to be a bit more frugal with your use of public IPv4 addresses and to think about accelerating your adoption of IPv6 as a modernization" when they themselves have been dragging their feet in IPv6 adoption, and in many cases are still blocking or at least making it unnecessarily difficult to use IPv6.

messe 3y ago
A significant number of AWS Customers are "internal", and—believe it or not—the cost of resources does come up in design meetings at Amazon. This change might actually light a fire those teams to actually start supporting IPv6 properly.
BaseballPhysics 3y ago
Well, ask yourself: if you're Amazon and you have the choice to spend money getting ipv6 working properly, or you can make money selling v4 addresses without any risk of customers jumping ship, what would you do?
- hinata08 3y ago
  > without any risk of customers jumping ship actually, changing of cloud services is in the sweet spot of being both manageable, and pretty complex so you won't do it every other day. So if companies are fed up for long enough (or if engineers find it so complicated or costly that they learn to do cloud with something else), they will change. And when they will change, they will never come back. Amazon would be just like AOL or Yahoo (or Jenkins or SVN) or any forgotten giant. Additionally, many companies don't rely on any cloud service so far. One day, when they will eventually implement it, they won't take what has annoyed others. AWS is already more expensive than the services of smaller companies (OVH and the like). So Beware. This change on its own won't make much difference, but they shouldn't be too pushy.
  - BaseballPhysics 3y ago
    > actually, changing of cloud services is in the sweet spot of being both manageable, and pretty complex so you won't do it every other day. Exactly. Once you're tied to Amazon's cloud, and especially their managed services, moving away is enormously costly and complex. Early in the cloud game people used to pretend to build abstractions to try to avoid being locked down to a single vendor, but these days that's all but done. The result is AWS is beyond sticky. > So if companies are fed up for long enough (or if engineers find it so complicated or costly that they learn to do cloud with something else), they will change. Which is why Amazon will keep their fees for IPv4 high enough to be profitable but low enough that investing in changing cloud providers isn't worth the cost to their customers. > Additionally, many companies don't rely on any cloud service so far. One day, when they will eventually implement it, they won't take what has annoyed others. No one ever got fired for picking AWS.

by zokier 3y ago

messe 3y ago

A significant number of AWS Customers are "internal", and—believe it or not—the cost of resources does come up in design meetings at Amazon. This change might actually light a fire those teams to actually start supporting IPv6 properly.

BaseballPhysics 3y ago

Well, ask yourself: if you're Amazon and you have the choice to spend money getting ipv6 working properly, or you can make money selling v4 addresses without any risk of customers jumping ship, what would you do?

hinata08 3y ago
> without any risk of customers jumping ship actually, changing of cloud services is in the sweet spot of being both manageable, and pretty complex so you won't do it every other day. So if companies are fed up for long enough (or if engineers find it so complicated or costly that they learn to do cloud with something else), they will change. And when they will change, they will never come back. Amazon would be just like AOL or Yahoo (or Jenkins or SVN) or any forgotten giant. Additionally, many companies don't rely on any cloud service so far. One day, when they will eventually implement it, they won't take what has annoyed others. AWS is already more expensive than the services of smaller companies (OVH and the like). So Beware. This change on its own won't make much difference, but they shouldn't be too pushy.
- BaseballPhysics 3y ago
  > actually, changing of cloud services is in the sweet spot of being both manageable, and pretty complex so you won't do it every other day. Exactly. Once you're tied to Amazon's cloud, and especially their managed services, moving away is enormously costly and complex. Early in the cloud game people used to pretend to build abstractions to try to avoid being locked down to a single vendor, but these days that's all but done. The result is AWS is beyond sticky. > So if companies are fed up for long enough (or if engineers find it so complicated or costly that they learn to do cloud with something else), they will change. Which is why Amazon will keep their fees for IPv4 high enough to be profitable but low enough that investing in changing cloud providers isn't worth the cost to their customers. > Additionally, many companies don't rely on any cloud service so far. One day, when they will eventually implement it, they won't take what has annoyed others. No one ever got fired for picking AWS.