This is more of a side effect of providing self-support solutions, and a trend in Customer Support departments. Amazon Support has been on top of the lists and awards for best support because they have proper KPIs that incentive customer retention/satisfaction over just number of contacts resolved.<p>So when you have good support/sales staff and most contacts are solved with self-service, what remains are contacts about complicated cases and inquiries.<p>I imagine that they always had a lot of contacts about optimizing spending, and policies to help and retain those customers accordingly, and now the percentage of time spent in those is higher, probably because the other types of contacts are now self-service.
This sounds like a good thing. I work for a <1000 employee firm, and AFAIK we're spending in 6 figures monthly with AWS. I cannot even imagine what huge places spend there.<p>All it takes is bad support, severe price undercutting, or degrading service and we're off to another, or a split. By having people at least feign caring, giving support, and giving suggestions, they're locking us in and getting way more back in revenue than what it's costing them, at least from us.
The original promise of the cloud was that it was cheaper than on prem. For many companies this has turned out not to be the case. Having worked on a cost optimization product for the past year (<a href="https://vantage.sh" rel="nofollow">https://vantage.sh</a>) my belief is that the cloud _is_ cheaper than on prem but it is difficult to configure it to be so.<p>In particular it is difficult and stressful to understand all the knobs to turn within each cloud provider. It's a very AWS thing to put a lot of effort into lowering their customers' bills and I do think it makes for longer lasting business relationships.
Not just their "clouds" but their "cloud spend".<p>From the article:<p>> Amazon Web Services sales and support teams are currently “spending much of their time helping customers optimize their AWS spend so they can better weather this uncertain economy.”
I was in Google Cloud's partner org for >7 years, managing a team of solution architects pointed at our most strategic partners (Accenture, Deloitte, Infosys, HCL, TCS, etc). I have been saying for nearly the entirety of the time that the way things will pan out for hyperscalers is going to roughly look like this:<p>AWS = the bazaar of public clouds. A service for nearly everything, but WYSIWYG and quality & consistency will be all over the place, just like amazon.com has become.<p>Azure = will ultimately own the enterprise. Microsoft is the new IBM and their mature GTM and Professional Services organizations will carry increasing value as cloud services become mostly commoditized. Microsoft has multiple large revenue streams to fund disruptive acquisitions and these will bear fruit through good management. Satya is proving to be an exceptional CEO.<p>GCP = an also-ran on compute/network/storage, but potentially differentiated on data, analytics & AI if leadership can organize the troops and keep focus on things that matter. Still very rough on the GTM side, and late to the party, making enterprise sales that much harder. Has some unique strengths, but can't rest on its laurels. Execution and focus are key.<p>Oracle = Making a killing selling an easy-button-to-cloud to existing Oracle on-prem customers, and frankly, this is plenty to keep things moving forward for a while.<p>IBM = Lots of hopes & dreams associated with RedHat acquisition and GBS/GTS split. It's still a bit early to tell how things will pan out, but IBM isn't playing the same sport as the rest, and has a lot more in common with Oracle than the big three.<p>My prediction for the next couple of years is that AWS continues to lose market share due to QoS and ultimately being spread too thin (and alienating partners), and all the rest capture it. MSFT is the biggest winner, Google will eventually find a sweet spot (it's already in the "too big to fail" category, and will achieve profitability this year), and ORCL/IBM will see increasing success in their niches but largely avoid direct competition/comparison with the others.
1. At which point does it become cheaper for AWS to offer discounts to customers rather than optimizing their spend?<p>2. At which point does it become cheaper for AWS to just simplify their pricing structure?
Personally, this is what I expect of them, specifically for smaller orgs that don't have CISO, SRE or other ops folks needed.<p>Now, I'm not saying this should be the expected behavior for everyone or every situation, but "aws staff spends majority of time doing what aws staff is hired and skilled to do"<p>Seems pretty "cost of doing business" to me
A few weeks back helped someone move from EC2/ELB/RDS to Lightsail Vm/LB/Database The same app and stuff, but the price is now fixed[0]. So many apps can use something like Lightsail and cut costs. I am surprised AWS don't promote lightsail. They also have a weird OS selection and still have CentOS 8, which is no longer supported. They treat Lightsail as a second-class citizen.<p>[0] <a href="https://aws.amazon.com/lightsail/pricing/" rel="nofollow">https://aws.amazon.com/lightsail/pricing/</a>
Isn't that the point? "Don't build your own infrastructure, outsource to the cloud!" has been the rally call for a decade. It's the entire reason "the cloud" has any value at all, beyond renting at hardware depreciation rates. Someone else is there maintaining the data center, managing failover, ensuring uptime, etc. by contract.<p>This press release could easily be interpreted as AWS backpedaling on a commitment to maintain its infrastructure.
We have some kind of k8s cluster that's just locked into a state where we can't delete it because of some wacky dependencies that no one at the company understands (it was set up by others). So at some point we'll reach out to amazon to have them wipe it.<p>It's kind of a messy product.
Now if only they'd spend time optimizing their management APIs and SDKs so they were more coherent.<p>I do not like using the console or having to login to the web portal, but there are things you just can't do from the SDK, or at least, I haven't figured out the right way to do them yet. Entirely Byzantine.<p>I wonder if they'll ever get around to addressing the mountain of complaints folks have about local dev and emulators too.
The title has two grammatical errors with quotes. The corrected form would be:<p>> AWS staff spending ‘much of their time’ optimizing customers' clouds
We had a RDS db running at 100% when typical traffic is say 40/50%.<p>Support never found the solution, we had to scale up and out and completely replace the db two times for performance to return to the baseline.<p>All costed about 10k for what was essentially an aws bug.
I believe the next wave of SaaS is products that provide custom deployment, operational support, and cost optimization, where specialist software orgs can provide standard efficiencies and engage AWS for deeper looks.
Use vanilla products (K8S, "RDS", ...) so you can always dangle the threat of going on-prem or to another cloud provider.<p>Once you use Lambdas and other deep AWS product, you're locked in.
Of course. AWS apps are a mess and needlessly over complicated. Even if sales went on they'd still spend more time untangling the mess they've made for their clients.
IBM's Hybrid Cloud concept is promising.<p>Run your sensitive or expensive bulk resources like dbs onprem and go cloud for the rest. You can often save big just bringing your db onsite.
TL;DR: they want to rip you off less aggressively, so you don't ditch them on the short term.<p>Cloud computing has become so expensive that so many companies are moving away from it. And for good reason.<p>The only providers that are actually reasonable on pricing at the moment are OVH and Hetzner... by an order of magnitude (or two) cheaper than Google Cloud, AWS, Azure, Vercel, etc.<p>Trusting for any of the latter companies to not rip you off is like trusting a wolf to take care of the sheep herd. It just doesn't make any sense, as their incentives are many times at the opposite spectrum than their customers.