|
|
Пишет Slashdot (![[info]](http://lj.rossia.org/img/syndicated.gif){kind=small} syn_slashdot)@ 2024-01-17 14:00:00 |
 |
|
 |
|
|
|
|
|
|
 |
|
 |
Brace Yourself, IPv6 is Coming
Paul Copplestone, co-founder of Supabase, writing in a blog post: On February 1st 2024, AWS will start charging for IPv4 addresses. This will cost $0.005 per hour -- around $4 month. A more accurate title for this post would be "Brace yourself, IPv4 is leaving," because I can't imagine many companies will pay to keep using the IPv4 address. While $4 is relatively small for an individual, my hypothesis is that AWS is a foundational layer to many infrastructure companies, like Supabase -- we offer a full EC2 instance for every Postgres database, so this would add millions to our AWS bill. Infrastructure companies on AWS have a few choices: 1. Pass on the cost to the customer. 2. Provide a workaround (for example, a proxy). 3. Only offer IPv6 and hope the world will catch up.
Paul Copplestone, co-founder of Supabase, writing in a blog post: On February 1st 2024, AWS will start charging for IPv4 addresses. This will cost $0.005 per hour -- around $4 month. A more accurate title for this post would be "Brace yourself, IPv4 is leaving," because I can't imagine many companies will pay to keep using the IPv4 address. While $4 is relatively small for an individual, my hypothesis is that AWS is a foundational layer to many infrastructure companies, like Supabase -- we offer a full EC2 instance for every Postgres database, so this would add millions to our AWS bill. Infrastructure companies on AWS have a few choices: 1. Pass on the cost to the customer. 2. Provide a workaround (for example, a proxy). 3. Only offer IPv6 and hope the world will catch up.
Read more of this story at Slashdot.
