3 ms·
> You cannot even use github without a proxy! Luckily that does not seem to be an issue here. You only have to pay for a public IPv4 address, you still have a
by crote 3y ago
> You cannot even use github without a proxy!
Luckily that does not seem to be an issue here. You only have to pay for a public IPv4 address, you still have a full IPv4 stack and are able to make outbound connections via NAT.
- ArchOversight 3y agoAWS won't give you a NAT without you paying for it (NAT Gateway) which requires a public IPv4 address (which you will soon have to pay for). There ain't no such thing as a free lunch.
- jeroenhd 3y agoI don't think you need that based on https://aws.amazon.com/blogs/aws/let-your-ipv6-only-workloads-connect-to-ipv4-services/ https://aws.amazon.com/blogs/aws/let-your-ipv6-only-workload... It's possible that the business model has changed, but at least on this blog they say it's available free of cost.
- yorwba 3y agoNot free of cost, free of additional cost if you were already using a NAT Gateway before they added NAT64 capability.
- tedivm 3y agoThat article makes it clear that the NAT Gateway needs IPv4 > The NAT gateway recognizes the IPv6 address prefix, extracts the IPv4 address from it, and initiates an IPv4 connection to the destination. As usual, the source IPv4 address is the IPv4 address of the NAT gateway itself. If the NAT Gateway doesn't have an IPv4 address it won't work.
- ArchOversight 3y ago> Pricing and Availability > These two new capabilities to the VPC NAT gateway and Route 53 are available today in all AWS Regions at no additional costs. Regular NAT gateway charges may apply. Specifically: > Regular NAT gateway charges may apply. Which should say: "Regular NAT gateway charges apply" Since you still pay for the traffic that is processed by the NAT gateway (per GiB).