Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS to begin charging for public IPv4 addresses

aws.amazon.com

Post reply on HN
Print view View original

341–350 of 377 posts

Re: AWS to begin charging for public IPv4 addresses

#341

Post by hidden80 »

profmonocle wrote: post #185
brickteacup wrote: post #139

Earlier quoted context omitted.

Not to mention the absurd fact that accessing (IPv4) AWS APIs from a private subnet requires paying for either a NAT gateway or an interface endpoint (we got bitten by sending a ton of Kinesis traffic through a NAT gateway once)

This is one thing Google Cloud does well - traffic to Google services bypasses NAT gateway, even over IPv4. I was curious how they do this, so I set up a service on Google Cloud Run that just echo'd the user's public IP address. When curl'd over IPv4, it said I was coming from a unique local (i.e. private) IPv6 address. The private IPv4 address of my server was embedded in the address, along with some other random-lo…

Check this out → https://www.juniper.net/documentation/us/en/software/junos/s...

Re: AWS to begin charging for public IPv4 addresses

#342

Post by doomjunky »

MagicMoonlight wrote: post #333

I still don't get why we can't just expand IPv4 into IPv5 by adding some new blocks to the front. So instead of 192.0.0.1 it becomes 0.0.0.0.192.0.0.1 All existing addresses work, you simply append zeroes to any address which is too short for the new standard. Any old timey software still works as long as you use a router between the two systems with an old timey address. This would give us as many addresses as we wa…

IP is not a text format (like HTTP). It's a binary format where each field of the IPv4 header has an exactly defined offset and length. The source IP address is placed at offset 96 and has a length of 32 bit, the destination IP address sits right afterwards with the same length. Changing anything will result in new protocol definition, et voilà that's IPv6.

https://en.wikipedia.org/wiki/Internet_Protocol_version_4#He...

Re: AWS to begin charging for public IPv4 addresses

#343

Post by anvuong »

MagicMoonlight wrote: post #333

I still don't get why we can't just expand IPv4 into IPv5 by adding some new blocks to the front. So instead of 192.0.0.1 it becomes 0.0.0.0.192.0.0.1 All existing addresses work, you simply append zeroes to any address which is too short for the new standard. Any old timey software still works as long as you use a router between the two systems with an old timey address. This would give us as many addresses as we wa…

I guess because it's not simply a text address, it's a protocol where a specific number of bytes in the packet (4 in this case) are dedicated for IP, you can't just simply modify this.

Re: AWS to begin charging for public IPv4 addresses

#344

Post by metadat »

MayeulC wrote: post #277
metadat wrote: post #7

Earlier quoted context omitted.

Thanks! Macro-expanded: AWS: IPv4 addresses cost too much, so you’re going to pay https://news.ycombinator.com/item?id=36942424 (3 days ago, 186 comments) AWS Begins Charging for Public IPv4 Addresses https://news.ycombinator.com/item?id=36910994 (6 days ago, 36 comments) AWS Public IPv4 Address Charge and Public IP Insights https://news.ycombinator.com/item?id=36910855 (6 days ago, 9 comments)

You make it sounds like that expansion was performed automatically. Is that something HN's reply box supports?

Haha, no. I do it manually, but have gotten pretty efficient at it to the point where it only takes a minute.

Re: AWS to begin charging for public IPv4 addresses

#346

Post by CSSer »

grrdotcloud wrote: post #225
dilyevsky wrote: post #193

Earlier quoted context omitted.

Egress to cloudfront is free on aws

Imagine a cloud transfer utility that made that easily possible?

If I follow what you're saying I suppose my understanding could be wrong, but there's no "cloud transfer" required. It's just a matter of both the distribution and the configured origin being on AWS. If the origin doesn't direct traffic outside of the datacenter, AWS doesn't bill that as egress to whoever owns the origin. The Cloudfront distribution, on the other hand, will take the hit once it exceeds the free tier because it's the AWS service distributing data to end-users. It has to make a request to the AWS internal service then cache it, so The SaaS lambda or s3 bucket or EC2 instance or whatever they're using is none-the-wiser. It's just how the AWS billing mechanism works.

Re: AWS to begin charging for public IPv4 addresses

#348

Post by tptacek »

colmmacc wrote: post #323
wbl wrote: post #226

Earlier quoted context omitted.

It could not have copied the UDP header. Otherwise you wouldn't be able to put any new protocol on IP without teaching it to every router.

Several other protocols solve this in a layering agnostic way by simply having a header length field. The header bytes can then be copied without any understanding of the format. This is even how IP's own ICMP protocol knows how much of an IP packet it should (at least) include in an error message so that the sender can know what triggered the error. TCP, UDP, ICMP and IP were all designed contemporaneously; UDP frag…

Also, if you get UDP completely right, do you need any other IP protocols? The whole point of UDP is programming directly to the datagram interface. Before IPv6 you could even disable the checksums.

Re: AWS to begin charging for public IPv4 addresses

#349

Post by DoughnutHole »

eqvinox wrote: post #275
alberth wrote: post #76

This was expected, and rent seeking. AWS over the last decade has spent $ billions buying up ASN blocks. I've never been one to use the word "rent seeking", but owning IPs is the ultimate rent seeking cloud business. Domain names can change registries but if you own the underlining IP being used (and there's a depleting supply of them) - it's a great business to charge rents on. https://www.techradar.com/news/amazon-…

> spent $ billions buying up ASN blocks. You can't buy/sell/trade "ASN blocks". The only people handling "ASN blocks" are the 5 RIRs (APNIC, RIPE NCC, ARIN, AfriNIC and LACNIC) and IANA. > owning IPs is the ultimate rent seeking cloud business It also seems that your use of "rent seeking" doesn't match established use. It normally refers to people extracting money for things far beyond their actual value. The IPv4 ma…

> It normally refers to people extracting money for things far beyond their actual value.

That's not what "rent-seeking" means at all.

Rent-seeking is extracting wealth from a system without creating anything. It's a term meant to differentiate profiting via productivity/adding value (eg. manufacturing a better product and outcompeting others) and profiting via extracting value from others without adding anything (eg. buying out all of the manufacturers of a product and leveraging your monopoly position to jack up prices).

Amazon haven't created any value here - they own enough of a stock of a scarce, in-demand resource that they can charge a great deal for it. It's the definition of rent-seeking.

Re: AWS to begin charging for public IPv4 addresses

#350

Post by bombcar »

MayeulC wrote: post #277
metadat wrote: post #7

Earlier quoted context omitted.

Thanks! Macro-expanded: AWS: IPv4 addresses cost too much, so you’re going to pay https://news.ycombinator.com/item?id=36942424 (3 days ago, 186 comments) AWS Begins Charging for Public IPv4 Addresses https://news.ycombinator.com/item?id=36910994 (6 days ago, 36 comments) AWS Public IPv4 Address Charge and Public IP Insights https://news.ycombinator.com/item?id=36910855 (6 days ago, 9 comments)

You make it sounds like that expansion was performed automatically. Is that something HN's reply box supports?

Macro expansion as in dang made it bigger by hand. Maybe he has a script.
Post reply on HN