3 Answers
- Newest
- Most votes
- Most comments
2
The workaround would be to use NAT Gateway which supports NAT64.
https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-nat64-dns64.html
0
hi,
I wonder switching to a dual-stack subnet especially since You're trying to access GitHub, which is IPv4-only.
https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
0
I had the same problem: I moved to IPv6 only instances to save a few bucks, and found I couldn't clone from Github.
I didn't want to pay for the NAT Gateway, so I made my own using a free-tier EC2 instance. I documented it here: https://pradeepcep.com/blog/free-nat-gateway-aws
answered 5 months ago
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 2 years ago

The primary reason I want to use ipv6 is to not pay for IP address. I took a look at NAT Gateway and it incur costs. Is there a cost-effective solution available? If not, then rather than setting up a NAT Gateway, I would keep using public ipv4 instead.
I also did a simple cost comparison: 1 NAT Gateway costs - 40-50 USD a month 1 IP Address costs - 4 USD a month
You are correct, in this case since the limitation is on the destination endpoint you will need to use some sort of NAT64 forward proxy or use Public IPv4 at the source endpoint.