Earlier quoted context omitted.
yep, and they should. aws has never really been suited to the hobbyist. does it work for that? of course. is it most cost effective? absolutely not. is it cost effective for people who need the resources? yes.
> is it cost effective for people who need the resources? yes. There is no possible use case in no possible universe where AWS is cost effective. Renting the same compute resources wholesale will cost you 20 times less. (Not a typo.)
AWS to begin charging for public IPv4 addresses
111–120 of 377 posts
Re: AWS to begin charging for public IPv4 addresses
#112Earlier quoted context omitted.
This seems unlikely, as 6to4 was deprecated in 2015: https://datatracker.ietf.org/doc/html/rfc7526
I couldn't believe it either, but using Chome on ChromeOS 114, updated yesterday, all the public sites report that I am connecting from 2002::/16
Re: AWS to begin charging for public IPv4 addresses
#113Earlier quoted context omitted.
It's not really computationally expensive, it's memory expensive. You need per connection state.
it already has stateful firewall so that's: source ip, dest ip, protocol, source port, dest port, connection state (say 16 bytes total) doing NAT too is what, 3 more bytes per connection (8 bits for an offset into an IP table and 16 bits for the translated port)
I hear such takes all the time and its really frustrating; usually in threads regarding IPv6, incidentally it is usually programmers who think they understand everything about networks because they know how tcp operates.
Re: AWS to begin charging for public IPv4 addresses
#114Earlier quoted context omitted.
> is it cost effective for people who need the resources? yes. There is no possible use case in no possible universe where AWS is cost effective. Renting the same compute resources wholesale will cost you 20 times less. (Not a typo.)
sure they became a multi billion dollar business by not being cost effective
A) Promising scale (and delivering to a certain extent)
B) being significantly more convenient than contemporary solutions
C) becoming trendy
D) hoodwinking CxO’s into the belief that not owning your data is better for you, actually. (CapEx vs OpEx)
E) unfathomable amounts of DevRel.
Nobody has ever claimed AWS was cost effective, they have said that “it’s worth the cost” though.
Re: AWS to begin charging for public IPv4 addresses
#115So I have a tiny personal website hosted on ec2. Right now the DNS points to the server's public IPv4 address. But I don't really want to pay $40+/year for an IPv4 for my personal project. Does anyone have experience switching a small personal site to IPv6 only in 2023? I'm guessing the vast majority of my (North American/European-based) friends and visitors can probably connect just fine to an IPv6 address. I wish I…
Re: AWS to begin charging for public IPv4 addresses
#116> A new blog post shows you how to use Elastic Load Balancers and NAT Gateways for ingress and egress traffic, while avoiding the use of a public IPv4 address for each instance that you launch. It would be nice if this came with reasonably priced NAT gateways. The current pricing is outrageous.
$40/mo is outrageous? We spend thousands a month on AWS and drive most traffic thru a single NAT gateway. It's rock solid and it "just works" without any fuss. Totally worth it.
For a little traffic $40 is outrageous.
Re: AWS to begin charging for public IPv4 addresses
#117Earlier quoted context omitted.
yep, and they should. aws has never really been suited to the hobbyist. does it work for that? of course. is it most cost effective? absolutely not. is it cost effective for people who need the resources? yes.
> is it cost effective for people who need the resources? yes. There is no possible use case in no possible universe where AWS is cost effective. Renting the same compute resources wholesale will cost you 20 times less. (Not a typo.)
Re: AWS to begin charging for public IPv4 addresses
#118So I have a tiny personal website hosted on ec2. Right now the DNS points to the server's public IPv4 address. But I don't really want to pay $40+/year for an IPv4 for my personal project. Does anyone have experience switching a small personal site to IPv6 only in 2023? I'm guessing the vast majority of my (North American/European-based) friends and visitors can probably connect just fine to an IPv6 address. I wish I…
How about removing the public IP and receiving connection from cloudfront? Or have it hosted in apprunner. Then you cname your domain to the services' domain, and skip the cost.
Re: AWS to begin charging for public IPv4 addresses
#119Earlier quoted context omitted.
Most applications will be able to move to v6 eventually. Hopefully moves like this will push that development.
Even already, I think you can get away with doing almost everything v6 with a much smaller number of ipv4s for legacy traffic. I say that but still largely use v4 for everything, so maybe I'm not one to talk.
Re: AWS to begin charging for public IPv4 addresses
#120Earlier quoted context omitted.
explain that page any other way
AWS has spent billions (with a b) on ipv4 addresses: https://news.ycombinator.com/item?id=36991477 This investment wasn't just of a strategic nature: they have enough market power to hold back the move towards ipv6.
it will have the exact opposite effect