AWS's Egregious Egress (blog.cloudflare.com)

Article summary

The article discusses AWS's egress fees, which some commenters believe are excessive and a form of vendor lock-in. The fees are compared to other cloud providers and network transit services, with some arguing that AWS's prices are not competitive. The article's content is not available, but the comments suggest that the author is critical of AWS's pricing model. The discussion revolves around the implications of these fees for customers and the potential motivations behind AWS's pricing strategy.

Main themes

• AWS egress fees
• vendor lock-in
• cloud pricing models
• network transit costs
• competition and innovation
• customer choice and flexibility

What commenters say

• AWS's egress fees are a form of vendor lock-in, making it expensive for customers to migrate their data to other providers.
• The fees are not justified by the costs of providing the service, and are instead a way for AWS to profit from customer data.
• Charging for egress but not ingress is a reasonable business decision, as it reflects the different costs and risks associated with each type of traffic.
• AWS's pricing model is not competitive with other cloud providers or network transit services, and customers are being overcharged for egress.
• The fees are a necessary part of AWS's business model, and customers who are unhappy with the prices can choose to use other providers.
• The distinction between egress and ingress is not relevant to the customer's experience, and AWS should charge based on total data transfer rather than direction.
• AWS's egress fees are a barrier to innovation and competition, as they make it difficult for customers to move their data to other providers and try new services.