I might be in the minority on this, but I don't see why customers are charged for AWS PrivateLink for AWS services. I should be able to use a PrivateLink for ECS in my private subnet without being charged $7 per AZ. This seems flawedhttps://aws.amazon.com/about-aws/whats-new/2019/01/aws-fargate--amazon-ecs--and-amazon-ecr-now-have-support-for-aws/ …
-
-
Thank you for a peek behind the curtain. My bigger question is why are we the customer on the hook for the data cost for an AWS service communicating with another AWS service via PrivateLinks. If my Lambda function calls over to ECS from a private subnet, I'm charged by PL.
-
Pricing is hard! We learned from gateway endpoints and decided it was better to price out each piece of functionality rather than build it into overall data transfer or service charges. I think the result is more "fair" for customers, who pay for what they use.
- 1 more reply
New conversation -
-
-
Gateway endpoints are great and we still support them, but use public IP addresses and so don't work in those situations.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.