Speed and Cost Tradeoffs

With cost optimization, as with the other pillars in the
AWS
Well-Architected Framework, there are trade-offs to consider,
for example, whether to optimize for speed-to-market or for cost. In
some cases, it’s best to optimize for speed—going to market quickly,
shipping new features, or simply meeting a deadline—rather than
investing in upfront cost optimization.

Sometimes design decisions are directed by haste rather than data,
and the temptation always exists to overcompensate just in
case rather than spend time benchmarking for the most
cost-optimal deployment. This might lead to overprovisioned and
under-optimized deployments. However, this is a reasonable choice
when you need to lift and shift resources from
your on-premises environment to the cloud and then optimize
afterward.

Investing in a cost optimization strategy upfront allows you to
realize the economic benefits of the cloud more readily by ensuring
a consistent adherence to best practices and avoiding unnecessary
overprovisioning.

Javascript is disabled or is unavailable in your browser.

To use the AWS Documentation, Javascript must be enabled. Please refer to your browser's
Help pages for instructions.