{"post":"

Introduction

The basic structure of the DevOps begins with data. After the right changes that take place within an organization to make sure that the people accustom themselves with DevOps, teams often rely on the process of monitoring, measurement, and continuous improvement to keep track of the project under their responsibility.

The best teams use KPIs, which set a benchmark for their performance and report to the management. However, there is one metric which probably every DevOps team might not be tracking. The metric is most commonly the cloud cost of their engineering decisions.

In the cloud, every engineering choice has its own cost. The only thing that interferes with decision making is the access to the relevant real-time data. Every engineer makes their cloud infrastructure decisions with the best intentions. Still, there are some in the dark till date.

Every successful DevOps engineer ensures that they know how to include the cost in their thinking and make it the most critical metric. Close monitoring and availability of the cost are what every successful DevOps engineer keeps track of.

There can be situations where the DevOps engineer might face a lack of time and relevant cost data, which can make the process of cloud cost optimization reactive for the various DevOps teams. Such a situation is not rare; it happens most of the time in almost every organization. The cloud architect chooses to respond to the finance request rather than reporting on the cost of the application. This makes an explanation of the monthly AWS bills very hard.

Often, the developers' time to find the root cause of the financial problem becomes too late, and therefore, any drastic measures cannot be taken. And the entire process goes into waste. Every developer might also face an interruption in their work, which is caused due to this investigation of the incident.

The real cost of engineering choices

The DevOps team's main intention is to make their cost decisions right, but it often becomes too hard for the DevOps team to know the real structure of the cost as an engineering choice after reaching a certain limit.

Various DevOps teams try to use cloud vendors' budgeting features to define how much they should be spending on a project. However, these tools can be effective, but they don't give an idea of the unexpected costs. It is easier to predict the fixed costs of computer resources than the variable costs like Data Transfer, Requests, NATGateway, and Snapshots.

These unexpected costs often lead to the introduction of one significant, unpredictable amount.

The uncomplicated engineering decisions often lead to various ups and downs in decision-making if the visibility is not sufficient by the DevOps team. Every developer can use any effective tools they might think will be successful in bringing a smooth decision process for monitoring the monthly AWS bill; they may even abstract out some of the financial processes together.

However, suppose they count on feedback while building the cost to make engineering decisions; in that case, it becomes more impactful. Developers continually make choices about the system's usage and how to provision those systems appropriately. When the DevOps teams are empowered with the instance data, they can make better, more effective decisions faster than the usual decisions, which leads to the slowdown of the workflow.

\n","title":"AWS Engineering choices","authorDetails":{"name":"Indrita Chandra","slug":"indrita-chandra"},"description":"In this article we'll learn about engineering choices and cost of engineering choices in AWS.","slug":"aws/aws-engineering-choices","articleId":"636a83417bb1ce5072622b13","bookmarkStatus":{"isBookmarked":false,"bookmarkId":null}}