At the very least you should look at what is needed to make a cloud migration successful for you.
I was part of the team that moved my employers systems to AWS as an IaaS move in 2012. Back then AWS was the only reasonable host for an operation of our scale, but this is no longer the case. For our move we installed SQL on to AWS servers using our own licenses, but this was always regarded as a stepping stone towards DB as a Service, and we are now starting this move.
Part of our planning covered email, as we send a few million emails each day. AWS SES looked too costly, so eventually we chose PowerMTA to do the email send, and hired PostMastery to manage the email reputation issues.
All hosting options have costs, risks, and opportunities. Different costs, risks and opportunities apply to wholly-owned, co-lo, hybrid cloud and dedicated cloud. Doing nothing is never cost and risk free, and will limit your opportunities compared to one of the other options. Part of the job of IT is to align the costs, risks and opportunities with what will best help the business to succeed.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara