Cloud services
Cloud working is just the modern version of using timesharing mainframes from the early days of computing.
For almost all sustained workloads it is cheaper to use your own kit rather than rent services from a cloud provider.
Valid reasons for using a cloud
1) Short term peak (under 3 months)
2) Insufficient internet connectivity at own premises
3) Keeping development and testing well away from production
4) Temporary substitute for unavailable systems (eg after a fire)
Reasons for NOT using a cloud
1) Cost - in under 3 years (under 1 year in many cases) running the job on own hardware will be cheaper than the cloud price
2) Legal constraints - any company in the EU that allows personal data to be on a cloud controlled by US firms is in danger of massive fines due to the EU GDPR and the US CLOUD act.
3) Data security - if the access to the cloud application is not set correctly then massive data breaches are all too easy - this again raises the potential of nasty fines to companies that trade in the EU due to GDPR. Data breaches on own kit behind a firewall are usually due to an attack (rather than the stupidity that has left so many Amazon storage buckets with world access).
4) Lock in to one cloud supplier. It is far too easy to embed implicit assumptions about the available facilities into applications resulting (for example) in an application that works on AWS but needs extensive rework to run on Azure.
PLEASE before committing a job to "the cloud" price the costs of own kit vs cloud kit over the expected timeframe. Include the costs of 2,3,and 4 above in the analysis before committing to the cloud.