News for hackers. Stuff that matters.

A comment on AWS Customers Cannot Escape IPv4.

Re:AWS Customers Cannot Escape IPv4 by NovemberWhiskey on Friday September 22, 2023 @02:02PM (#37615413)
>almost no AWS API can be used from a VPC without public IPv4 addresses

Virtually every single application at the company I work at deploys into VPCs without public IPv4 addresses - this seems like a ridiculous claim.

[ Parent | on HN ]
Re:AWS Customers Cannot Escape IPv4 by ericpauley on Friday September 22, 2023 @02:55PM (#37616156)
Do they use NAT gateways? These require public IPs.
[ Parent | on HN ]
Re:AWS Customers Cannot Escape IPv4 by NovemberWhiskey on Friday September 22, 2023 @03:15PM (#37616405)
No; we use AWS Direct Connect for access from our on-premise networks.
[ Parent | on HN ]
Re:AWS Customers Cannot Escape IPv4 by apparentorder on Saturday September 23, 2023 @12:47AM (#37620644)
As mentioned in the footnote, this can be done by using PrivateLink; it costs a few bucks too, but it is the way to go if your VPC does not (or must not, for Compliance™ reasons) have internet connectivity.

If your target VPC has neither PrivateLink nor public IPv4 connectivity somewhere, I'm not sure how that would work; I'd love to learn how that was built.

[ Parent | on HN ]
Re:AWS Customers Cannot Escape IPv4 by NovemberWhiskey on Saturday September 23, 2023 @08:18AM (#37622621)
Yeah, sure, we use PrivateLink. In my opinion, it's clickbait to say "almost no AWS API can be used from a VPC without public IPv4 addresses" with a footnote "actually most can if you use the service that enables that".
[ Parent | on HN ]