- Newest
- Most votes
- Most comments
This makes the IPv4 charge seem more like a money-grab than an actual attempt at reducing the use of IPv4. Come on, Amazon, I started with you years ago because you were the best value. You've started making more decisions that are increasing my bills without me having any recourse.
CloudFront service still does not support IPv6 only [+] and communicate with the Origin using IPv4.
[+] https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-support.html#ipv6-service-support
You will not be able to exclude IPv4 charges completely, as CloudFront needs to communicate to the Origin via public IPv4-address and the solutions like ELB or GA can optimize the charges by reducing the overall number of used public IPv4 [+] but will not exclude those completely.
The only way to avoid billing for using IPv4 - use BYOIP IPv4 addresses for public resources in VPC [+]: You will not be charged for IP addresses that you own and bring to AWS using Amazon BYOIP.
[+] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
Our service team is looking into supporting IPv6 requests to origin, but there is no specific date on when this feature will be launched yet. Regardless, we would like to thank you for making your needs known to us. You are making AWS better for all of our customers.
Can I please check what the status is with this? Cmon AWS, you force us to stop using IPv4 by adding charges and now we can't use your services with ipv6!
+1 on this Feature Request. With the new IPv4 charges, the cost of running nano-sized spot instances for public demo/dev purposes has DOUBLED.
please, keep efforts on this. we need do remove as much as possible public ipv4!
Are there any timeline or roadmap on this feature? This will allow me to remove my elastic IPs and cut costs with 25%.
Amazon CloudFront now supports IPv6 origins for end-to-end IPv6 delivery
https://aws.amazon.com/blogs/networking-and-content-delivery/amazon-cloudfront-now-supports-ipv6-origins-for-end-to-end-ipv6-delivery/
Here we go - not always the solution for IPv6 origins, but at least you can now use the brand new feature called 'VPC origins': https://aws.amazon.com/blogs/aws/introducing-amazon-cloudfront-vpc-origins-enhanced-security-and-streamlined-operations-for-your-applications/
So you can now declare an EC2 instance as a private resource to your Cloudfront distro and use that over private networking so you can change your EC2 from IPv4 to IPv6 now - bingo!
Let me know if you have any questions.
VPC Origins unfortunately lacks Cloud Formation support.
It also lacks Lambda@Edge support.
It's really need to be prioritised. The competitors like Cloudflare support IPv6-only origins probably since a few years and having no such feature in AWS CloudFront is very disappointing, especially if AWS blames the lack of IPv4 addresses and charges for their usage.
IPV4 is Now Money Making service of AWS. Their own services are not supporting ipv6, then why are they charging for ipv4.
The feature is now supported. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cloudfront-enable-ipv6.html
Why is this still not possible, but AWS also doesn't mind forcing the charge down to us while also spending their resources on just a UI update on the console?
The VPC origins is still insufficient. Mainly for me, it does not support Lambda@Edge functions. Is it really that hard for CloudFront to interface with a public IPv6 load balancer? VPC origins are a nice feature but they do not address the issue here. Again, this is extremely hypocritical of AWS to say they are forcing us to reduce our IPv4 usage when they themselves can't even handle IPv6.
Amazon CloudFront now supports IPv6-only and dual-stack origins. https://aws.amazon.com/about-aws/whats-new/2025/09/amazon-cloudfront-ipv6-origins/
Relevant content
- asked 2 years ago
This really needs prioritization since AWS has started forcing IPv4 charges on to us.
I recommend cutting a support ticket requesting this in your impacted accounts.
I still cannot believe AWS forced IPv4 pricing without supporting IPv6 across their full stack. Asked support again about IPv6 and just said it is "coming".