# Worth Reading: Using AWS Services via IPv6

DevFeed: [Worth Reading: Using AWS Services via IPv6](<https://devfeed.tech/articles/worth-reading-using-aws-services-via-ipv6-11012.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/05/worth-reading-aws-egress-traffic-ipv6/>)

Published: 2024-05-24T06:23:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

## AI overview

The article comments on AWS charging for public IPv4 addresses and argues that access to many AWS services may still require public IPv4 connectivity or a private link, complicating migration to IPv6. It directs readers to a related analysis of AWS egress traffic and IPv6 service access.

## Source excerpt

AWS started charging for public IPv4 addresses a few months ago, supposedly to encourage users to move to IPv6. As it turns out, you need public IPv4 addresses (or a private link) to access many AWS services, clearly demonstrating that it's just another way of fleecing the sheep Hotel California tax. I'm so glad I moved my videos to Cloudflare ;) For more details, read AWS: Egress Traffic and Using AWS Services via IPv6 (rendered in beautiful, easy-to-read teletype font).