Of course, it wasn't that simple. Each cloud has different services and those services have different dependencies. We had to re-evaluate the architecture on each cloud platform to ensure we were leveraging resources in a cost-effective and sane way. The architecture turned out highly different on each cloud platform. Moreover, the work to design with the cost in mind was significant. There are so many resources and "savings plans". Of course, these differentiators are what drives competition among the cloud providers but I think it is hurting adoption instead of helping in the long run.
The cost of resources on each cloud provider is a major factor in how we architect our apps. I think it would revolutionize the cloud industry and accelerate adoption if there existed a standard pricing model for cloud computing (at least for a subset of common services/compute/storage resources). That way, the cost of a design on one cloud provider is a reasonable estimate of the cost on another provider adhering to the standard pricing model. Moreover, advances in technology that drive prices down for resources in the standard pricing model can drive costs down across providers.
It's a naive ask from a neophyte cloud architect. But I think it's the future. What are your thoughts?
Cloud companies can either offer very fine grained pricing - where you pay small amounts for everything (bandwidth in and out, storage, cpu, memory usage, etc) which will be tied to how they have implemented their product (often charged on a cost+%profit basis). Or bundle stuff up in tiers (developer, business, enterprise levels etc) which are simpler to understand but can work out expensive if you use up your limit.
AWS atleast provides tools for working out costs - it should also be possible to model your app costs in a spreadsheet for each service provider.