Do they offer shared IPv4 addresses with routing by HTTPS SNI?
On ELB yes.
AWS to begin charging for public IPv4 addresses
11–20 of 377 posts
Re: AWS to begin charging for public IPv4 addresses
#12As long as IPv6 remains free, and there is some kind of ipv4 accessible proxy for web stuff for free, I'm happy.
Re: AWS to begin charging for public IPv4 addresses
#13I personally dont think 45$ per year is going to change habits that much, especially for larger customers who have a lot of public IPs.
Already a lot of discussion about this at my job. It’s a lot of $ at scale. We will put a bunch of work in to avoid the fee.
Re: AWS to begin charging for public IPv4 addresses
#14I personally dont think 45$ per year is going to change habits that much, especially for larger customers who have a lot of public IPs.
Huh, speaking of lots of public IPs, most of MIT's old class A is now owned by Amazon :-(
NetRange: 18.32.0.0 - 18.255.255.255
Re: AWS to begin charging for public IPv4 addresses
#15Earlier quoted context omitted.
Hobby customers can buy an entire VPS, complete with IPv4 to tunnel through, for 1/4 that
Hobby customers aren't using AWS, by and large. And it's only a matter of time before we see more and more costs for IPv4 down in these tiers as well.
> Hobby customers aren't using AWS
AWS has the easy to use Lightsail[1] VPS offer with cheapest product at $3.5/mo but they'll likely increase these prices as well, since there's an IPv4 address included.
Re: AWS to begin charging for public IPv4 addresses
#16> 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.
Re: AWS to begin charging for public IPv4 addresses
#17Re: AWS to begin charging for public IPv4 addresses
#18This is a hidden price hike. It would be more reasonable if there was a corresponding decrease in server costs.
Their costs for delivering one service are increasing so they should lower their prices on another?
Re: AWS to begin charging for public IPv4 addresses
#19I personally dont think 45$ per year is going to change habits that much, especially for larger customers who have a lot of public IPs.
Huh, speaking of lots of public IPs, most of MIT's old class A is now owned by Amazon :-( NetRange: 18.32.0.0 - 18.255.255.255
Why :-( ? There's no way MIT was using more than a tiny fraction of that /8; now it's actually being put to real use, and MIT probably got some money out of it. Everybody wins.
Re: AWS to begin charging for public IPv4 addresses
#20I personally dont think 45$ per year is going to change habits that much, especially for larger customers who have a lot of public IPs.
Huh, speaking of lots of public IPs, most of MIT's old class A is now owned by Amazon :-( NetRange: 18.32.0.0 - 18.255.255.255
The market is working :-)