5 ms·

For the uninitiated, what is the advantage?

speedgoose 5y ago
Increased margins for AWS as the shortage of public IPv4 makes the price per IP more and more expensive. You may also save a few $ per year.
- Sebb767 5y ago
  I doubt it. They still default to giving an EC2 machine a public IPv4; if their primary motivation would be saving IP costs, they could easily go for the low-hanging fruit.
  - lmm 5y ago
    EC2 is their oldest service; I bet it has oodles of legacy workflows both on Amazon's side and on customers' side. Lambda is likely a much lower hanging fruit in terms of the effort required to make changes to it.
    - tsimionescu 5y ago
      To be pedantic, SNS is their oldest service, if I remember my AWS training correctly.
      - swaranga 5y ago
        You are thinking of SQS, the preview version of which was the first to be introduced. S3 was the first non-preview service made generally available.
        jeffbarr 5y ago
        Correct - you know your AWS launch history!
  - qeternity 5y ago
    The number of deployed lambdas likely exceeds the number of ec2 instances by many multiples (pure conjecture). It's a perfect use-case for v6 - dual stack in front and then v6 internally.
  - wwn_se 5y ago
    EC2 is not really low hanging fruit. Most expect to get a ipv4 when creating an instance and many relies on that. Cheaper instances with ipv6 only is probably coming
    - pferde 5y ago
      That's very likely. Hetzner already offers cheaper ipv6-only dedicated servers: https://news.ycombinator.com/item?id=29471986 https://news.ycombinator.com/item?id=29471986
miyuru 5y ago
AWS introduced IPv6 only VPCs last year[1] and it made many AWS APIs endpoints unreachable from IPv6 instances as they are IPv4 only. So they are adding IPv6 support to them[2]. You can expect more of these type of blog posts this year. [1] https://news.ycombinator.com/item?id=29327190 https://news.ycombinator.com/item?id=29327190 [2] https://news.ycombinator.com/item?id=29767004 https://news.ycombinator.com/item?id=29767004
zokier 5y ago
Compliance with federal policies: https://aws.amazon.com/blogs/publicsector/aws-enables-us-federal-governments-move-ipv6/ https://aws.amazon.com/blogs/publicsector/aws-enables-us-fed...
- realityking 5y ago
  Interesting trickle down effect from governments having a lot of purchasing power.
disruptiveink 5y ago
This is all about being able to invoke AWS Lambda from an IPv6-only network. Their copy states as much: "(...) removes the need for expensive networking equipment to handle address translation between IPv4 and IPv6." Use cases will be IPv6-only networks with no NAT64 capabilities, either due to compliance reasons or because you're running, eg, IoT devices that need to call home over a provided 3G/4G connectivity and you were only able to get competitive prices if you stayed away from the cellular provider's IPv4 stack.

Increased margins for AWS as the shortage of public IPv4 makes the price per IP more and more expensive. You may also save a few $ per year.

Sebb767 5y ago
I doubt it. They still default to giving an EC2 machine a public IPv4; if their primary motivation would be saving IP costs, they could easily go for the low-hanging fruit.
- lmm 5y ago
  EC2 is their oldest service; I bet it has oodles of legacy workflows both on Amazon's side and on customers' side. Lambda is likely a much lower hanging fruit in terms of the effort required to make changes to it.
  - tsimionescu 5y ago
    To be pedantic, SNS is their oldest service, if I remember my AWS training correctly.
    - swaranga 5y ago
      You are thinking of SQS, the preview version of which was the first to be introduced. S3 was the first non-preview service made generally available.
      - jeffbarr 5y ago
        Correct - you know your AWS launch history!
- qeternity 5y ago
  The number of deployed lambdas likely exceeds the number of ec2 instances by many multiples (pure conjecture). It's a perfect use-case for v6 - dual stack in front and then v6 internally.
- wwn_se 5y ago
  EC2 is not really low hanging fruit. Most expect to get a ipv4 when creating an instance and many relies on that. Cheaper instances with ipv6 only is probably coming
  - pferde 5y ago
    That's very likely. Hetzner already offers cheaper ipv6-only dedicated servers: https://news.ycombinator.com/item?id=29471986 https://news.ycombinator.com/item?id=29471986

miyuru 5y ago

AWS introduced IPv6 only VPCs last year[1] and it made many AWS APIs endpoints unreachable from IPv6 instances as they are IPv4 only. So they are adding IPv6 support to them[2]. You can expect more of these type of blog posts this year. [1] https://news.ycombinator.com/item?id=29327190 https://news.ycombinator.com/item?id=29327190 [2] https://news.ycombinator.com/item?id=29767004 https://news.ycombinator.com/item?id=29767004

zokier 5y ago

Compliance with federal policies: https://aws.amazon.com/blogs/publicsector/aws-enables-us-federal-governments-move-ipv6/ https://aws.amazon.com/blogs/publicsector/aws-enables-us-fed...

realityking 5y ago
Interesting trickle down effect from governments having a lot of purchasing power.

disruptiveink 5y ago

This is all about being able to invoke AWS Lambda from an IPv6-only network. Their copy states as much: "(...) removes the need for expensive networking equipment to handle address translation between IPv4 and IPv6." Use cases will be IPv6-only networks with no NAT64 capabilities, either due to compliance reasons or because you're running, eg, IoT devices that need to call home over a provided 3G/4G connectivity and you were only able to get competitive prices if you stayed away from the cellular provider's IPv4 stack.