What risks or challenges do you see with AWS Savings Plan for customers purchasing cloud services through a systems integrator?
VP of IT in Software, 5,001 - 10,000 employees
We purchase savings plans but we do not purchase our cloud services through a systems integrator.Senior Vice President - Advanced Engineering & Data Analytics in Manufacturing, 10,001+ employees
I don’t see this as risk rather see this as a risk mitigation strategy with the right SI. This model is evolving and there are multiple engagements where SI is taking e2e responsibility.1. Security has become a shared responsibility in well architected framework and SIncan take ownership on behalf of both AWS and client.
2. SI gets root access and can provided best in class Cloud managed services.
3. Si can apply CMP ( Cloud management platform) to optimize and managed cloud spend.
The only challenge is selecting the right partner and implementing the governance.
These topics are POV’s ( Point of view) in itself.
Content you might like
Production45%
Backup65%
Replication33%
Non-production DBs (Dev, Training, QA, etc.)30%
217 PARTICIPANTS
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.Data security51%
Shared resources/services35%
Compliance11%
Other: please specify.1%
685 PARTICIPANTS
We are also not buying our cloud products/services through a system integrator. So cannot share from experience, however, I’m curious to know if there are views from those who have used SI and if they faced any challenges or have opinions on why there could be challenges. :)