- Más nuevo
- Más votos
- Más comentarios
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.
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.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 10 meses
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
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.