Technology

37584 readers

340 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

153

AWS: IPv4 addresses cost too much, so you’re going to pay (www.theregister.com)

submitted 1 year ago by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

Cloud giant AWS will start charging customers for public IPv4 addresses from next year, claiming it is forced to do this because of the increasing scarcity of these and to encourage the use of IPv6 instead.

The update will come into effect on February 1, 2024, when AWS customers will see a charge of $0.005 (half a cent) per IP address per hour for all public IPv4 addresses. ... These charges will apply to all AWS services including EC2, Relational Database Service (RDS) database instances, Elastic Kubernetes Service (EKS) nodes, and will apply across all AWS regions, the company said.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 19 points 1 year ago (4 children)

Huh, I pay 0.4 or something at hetzner, AWS charges more than my whole Lemmy server costs.

[–] [email protected] 4 points 1 year ago

It will add tens of dollars to enterprise infrastructure costs!

[–] [email protected] 4 points 1 year ago (1 children)

Other providers will start charging more, the US and Europe have ALL ipv4 allocated now. So, yes the cost of a scarce resource goes... Up

Most of the big websites are on ipv6. Twitter isn't (but is that anyone's loss?). I think the only way we can all make sure the stragglers move to ipv6 is if we all leave an ISP that doesn't offer it.

After all these years it really should be the dominant stack.

[–] [email protected] 3 points 1 year ago (1 children)

My ISP doesn't give me v6 without giving up real v4. GitHub according to posts does not support v6. I think we are still a while away from v6 in "the west".

[–] [email protected] 7 points 1 year ago (1 children)

That's a really stupid thing for that ISP to do. It doesn't make sense. IPv6 costs them virtually nothing, yes the real IP costs them. But they're stretching out the time they need to provide it by putting conditions behind the ipv6 allocation.

Look up in this thread and just get an ipv6 tunnel, I used tunnels for 5 years between 2011 and 2015, until my ISP provided IPv6. While bigger businesses aren't going to go ipv6 only any time soon, I think smaller server operators might just do that to save money. When the cost of the IP becomes a larger part of the cost of the service.

[–] [email protected] 2 points 1 year ago

I know I can install a tunnel, but I don't see the benefit with everything supporting v4 any way. Hell, I myself use 3 v4 addresses.

And I agree that it's weird, but what can I do. Biggest cable internet provider in Germany.

[–] [email protected] 3 points 1 year ago (1 children)

Yeah. I pay like 3.50 for my lightsail instance that I host my pihole on. Are they really going to double that for my public ipv4?

[–] [email protected] 1 points 1 year ago

I'm running the smallest linux instance in US West 2, I believe. 512mb RAM, 1 core processor. More than enough for pihole+wiregurd

[–] [email protected] 1 points 1 year ago (1 children)

which package are you on? i've been wanting something like that

[–] [email protected] 1 points 1 year ago

CAX11, the smallest ARM64 offering. Though the website shows a slightly higher price than my dashboard, not quite sure who is right ;)