AWS to Begin Charging for Public IPv4 Addresses

Re:AWS to Begin Charging for Public IPv4 Addresses by pantalaimon on Thursday August 03, 2023 @06:06PM (#36992686)

Unless you need to pull anything from GitHub…

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by kccqzy on Thursday August 03, 2023 @06:22PM (#36992868)

Then direct your anger at Microsoft, not Amazon.

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by doublerabbit on Thursday August 03, 2023 @06:38PM (#36993043)

Why not both?

Both are dominating the internet-cyberspace and both screwing it over for everyone else.

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by tmpX7dMeXU on Thursday August 03, 2023 @07:24PM (#36993428)

Please stick to the topic at hand. Not every mention of a big tech company needs to devolve into a general bitch fest.

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by dundarious on Thursday August 03, 2023 @09:25PM (#36994286)

There's a collective action problem around IPv4 vs IPv6. Talking about Azure/Microsoft/GitHub and its lack of IPv6 support is very much an interrelated problem. It's ridiculous to think of noting downsides/trade offs as just kvetching.

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by duped on Thursday August 03, 2023 @07:12PM (#36993355)

Why do you need a public IPv4 address to pull from GitHub?

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by ripdog on Friday August 04, 2023 @12:23AM (#36995458)

GitHub has no modern IP support, so a system without a legacy IP is unable to pull anything from GitHub.

[ Parent | on HN ]

Re:AWS to Begin Charging for Public IPv4 Addresses by GoblinSlayer on Friday August 04, 2023 @03:34AM (#36996667)

That's the idea, you route github through a legacy route and use normal route for everything else.

[ Parent | on HN ]