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/ …
-
Show this thread
-
Replying to @kylegalbraith
Thanks for the feedback! Unfortunately the ECS team doesn't set pricing for PrivateLink but I'll forward your feedback along anyway! Note that PrivateLink is about 1/4th the cost of a using a managed NAT gateway per AZ for your private subnet
1 reply 0 retweets 0 likes -
Replying to @nathankpeck @kylegalbraith
Were running in the public subnet before? Because for people who were already running in a private subnet and using a NAT gateway to reach AWS services they should see a savings from using PrivateLink instead.
1 reply 0 retweets 0 likes -
Replying to @nathankpeck
Yes, it's cheaper than the NAT gateway, but that felt broken as well. In my mind AWS services should be able to call AWS services, this is the model used by Dynamo and S3 with gateway endpoints. I don't see why other services are being coupled to PrivateLink.
2 replies 0 retweets 2 likes -
Replying to @kylegalbraith
Perhaps
@colmmacc has more insight into why AWS PrivateLink over the gateway endpoints. To be honest I’m not sure I can explain this properly2 replies 0 retweets 2 likes -
Replying to @nathankpeck @kylegalbraith
The charge covers the underlying AWS HyperPlane capacity, which glues packets together stabefully and securely. It bridges the private networking so that PrivateLink services work even across VPN, Direct Connect, and between regions (with Inter-region VPC peering).
2 replies 0 retweets 7 likes -
Replying to @colmmacc @nathankpeck
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.
2 replies 0 retweets 0 likes
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.
-
-
Hopefully it also means that as we lower the cost of AWS HyperPlane internally, we can reduce pricing much more easily than adjusting the price for many separate services!
0 replies 0 retweets 4 likesThanks. 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.