2 ms·
>The alternative isn't IPv6, it's private addresses. I really wish more AWS services or workflows worked with private addresses. Sometimes a service can be com
by nemothekid 3y ago
>The alternative isn't IPv6, it's private addresses.
I really wish more AWS services or workflows worked with private addresses. Sometimes a service can be completely internal but needs a public address to either talk to Dynamo or install packages; but those endpoints aren't available via private IP, even though they physically live in the same region
- paulddraper 3y agoWhy?
- nemothekid 3y agoI really don't care about IPv6 or IPv4. In my neck of the woods, 10.0.0.0/8 is more than I would ever need. Most architectures I've seen only realistically need only a handful of public IPs, that then are assigned to a load balancer that does service discovery on internal services. I don't think about IP addresses at all.
- paulddraper 3y agoYeah but then you have to futz around with NAT.
- nemothekid 3y agoToday you have to futz around with NAT, but you wouldn't have to if you simply never made any connections to the public internet. And for many services that's completely fine.
- coredog64 3y agoI believe the latest version of the VPC wizard defaults to gateway endpoints for both S3 and DynamoDB. If you’re in a 6-only VPC/subnet, an egress only gateway will allow you to grab packages from IPv6 enabled public data sources.