Live data from Hacker News

AWS to begin charging for public IPv4 addresses

aws.amazon.com

151–160 of 377 posts

Re: AWS to begin charging for public IPv4 addresses

#151

[flagged]

Inflation has been aberrant over the past 3 years in some areas, i.e., food, from profit-price spirals but there is not widespread hyperinflation.

No one reputable is predicting the USD will crash imminently.

US T-bills lost a notch of rating due to long-term declining governance tied to the cozy relationship and revolving door between Wall St. and federal regulators. This is a form of corruption that undermines the economy and strategic power.

Re: AWS to begin charging for public IPv4 addresses

#152

Earlier quoted context omitted.

ELB is a substantial cost itself, though.

And not very good, together with the auto scaling groups, it performs the record act of not being able to do an instance refresh without downtime. We’ve put countless hours into that, seems like a simple problem, forums say it’s not solved.

This is not true.

You have to define health checks on your instances that reflect the availability of all services they host.

And you have to allow there to be more instances than your target number in each autoscaling group.

Re: AWS to begin charging for public IPv4 addresses

#154
post #9

This is a hidden price hike. It would be more reasonable if there was a corresponding decrease in server costs.

The move may seem unreasonable, but it seems more unreasonable to expect anything different from the oligarchy.

> but it seems more unreasonable to expect anything different from the oligarchy

oh my god when the demand for a scarce resource outstrips supply, prices go up. this is high school microecon, not some conspiracy by tHe oLiGaRcHy

Re: AWS to begin charging for public IPv4 addresses

#155
post #114

Earlier quoted context omitted.

sure they became a multi billion dollar business by not being cost effective

They became a multi-billion dollar business by: 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 cos…

> cost effective

> it’s worth the cost

Sounds about the same.

Re: AWS to begin charging for public IPv4 addresses

#156

So 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…

Throwing the VPC behind cloudfront is probably the best course of action, if your site is static I'd recommend looking into S3 + Cloudfront for hosting it. It's basically free, and great if your site is mostly static. I run a few scheduled jobs on Lambda to pull some data for my site and it comes out at basically $0 every month.

Re: AWS to begin charging for public IPv4 addresses

#158
post #137

Earlier quoted context omitted.

Bit confused. Couldn't you just run a Linux VM to do your NAT and only pay normal egress?

> just run a Linux VM + Run extra for failover, HA etc + manage security + Monitor performance + ...

You would have to run that in your own data center which is what original poster was comparing to.

Re: AWS to begin charging for public IPv4 addresses

#159
post #79

The only barrier for me to go IPv6-only is those VPS that are provided with a single /128 IPv6, and I do not know of a service that would offer IPv6 tunneling other than HE, that requires an IPv4 endpoint. The day I get a full /48 or /64 with my VPSes, I'm ready to drop IPv4.

Does your VPS assign you multiple ipv4 addresses? Otherwise seems like feature parity.

I use ipv6 everywhere, but I get annoyed when some features are missing.

For example, OVH won't let me transfer an IPv6 prefix like they do for IPv4. I thought I could just migrate my VMs to another box, but one of them had lots of clients with their own DNS/domains, so it was a huge pain to update.

Re: AWS to begin charging for public IPv4 addresses

#160
post #131

Earlier quoted context omitted.

Hmm, I use IPv4 mostly because nobody in their right mind can remember a IPv6 address…

Who's out there remembering IPv4 addresses?

Plenty of people own ipv4 addresses (I mean, all of them are owned, but most by companies) and have been using the same addresses for a very long time, you start to remember some of them by heart after that :)
Post reply on HN