Open mitovskaol opened 1 year ago
This is related to Warren's 'core' and 'workload' cost tracking script creation ticket, as anything this ticket above produced would be point-in-time and not necessarily showing a proper trend - Note as well that previous AWS clean up work and removal/reduction of certain services have caused a skew in cost diagrams that can make it difficult to establish a proper trend
As a general indicator one could be created to try to use as a temp projections tool, but a script should likely be the focus. A script automation would force discussion on the base criteria for the 'definition' of these costs and be able to drop periodic points-in-time. This would establish a proper trend and possible profile (linear/non, etc.). A script would establish the actual trend over time and using regression analysis be an indicator of a trend change and overall profile
Our executives would like to understand the correlation with the increase of the monthly operational expenses for AWS and scaling of the service as more teams onboard into AWS and consume more resources there. We need an infographic i.e. a matrix that list all foundational AWS services as documented in the Technical Architecture document that Jon put together, along with the current expenses that each service incures and the impact on the cost of the service as more teams onboard into AWS. Some services have a flat fee and won't be impacted by scaling up, while the cost of others is directly correlated with the consumptio of AWS resources by product teams.
Acceptance Criteria: