The managed services are expensive, but boy do they work well. Over the last couple years been running +100 each of managed elastic searches, RDS, and firehouse with minimal to no issues.
The managed services are expensive, but boy do they work well. Over the last couple years been running +100 each of managed elastic searches, RDS, and firehouse with minimal to no issues.
An interesting question: why does AWS charge so much for egress knowing that it could dissuade some currently-on-prem use cases? It definitely forces optimization, use of CDNs, compression, etc. Previously it likely reduced transfers to another provider, but as the parent alludes to, the use of managed services makes sticking to AWS much more likely. What else?
I’m unconvinced. A lot of money is spent on third party services (think Snowflake, but there are a ton) where the third party service is offered in AWS, GCP, and Azure. There is no on-the-Internet option.
If egress fees go away, on-the-Internet becomes appealing, and there goes a lot of revenue. If fees for other services go up, on-the-Internet becomes even more appealing.
1) Starting charging legacy fees like the MySQL 5.7 fees 2) Start charging for hits, IO, etc 3) Tier out fees like with Aurora IO optimized to increase revenue 4) Push support levers 5) Stop reducing prices for older instance models