run_5fead1c00fccd2fa

input

{
  "request": "Triage Jira ticket MZCLD-3805: MoCo FinOps: AWS Prepaid usage back up for Accounting. ",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3805"
  ],
  "sourceContext": {
    "issue": "MZCLD-3805"
  }
}

summary

MZCLD-3805 is a FinOps/Accounting data request, not an infrastructure incident. Mozilla's Global Accounting team needs detailed AWS committed-spend (prepaid usage) utilization data because they cannot reconcile the AWS billing console/dashboard screenshots to the amortization schedule Finance is using. They need: (1) actual 2026 utilization vs. the $388K currently scheduled recognition, (2) the AWS commitment end date(s) for both commitment "plans" (one active, one not yet started), (3) a forecast of remaining ~$781K prepaid balance utilization through commitment expiration, and (4) documentation that clearly ties AWS usage data to the prepaid balance/expense recognition schedule. The ticket is currently unassigned in Backlog with no comments, so it needs to be routed to whoever owns AWS commitment/Cost Explorer reporting (likely Cloud Ops/FinOps) and Accounting's specific questions need direct answers or a data export.

findings

• none

proposed actions

Thanks for flagging this. To close the loop with Accounting, we need to pull committed-spend (AWS Savings Plans / Reserved Instance) utilization data rather than relying on billing-console screenshots, since those don't map cleanly to the prepaid/amortization schedule. Proposed next steps:

1) Pull the two commitment/plan details from AWS Billing > Savings Plans (or Cost & Usage Report) including: commitment ID, start date, end date/term, total committed amount, and monthly utilization for the plan currently in use, plus start date for the second (not-yet-active) plan.
2) Export monthly utilization ($ used vs. committed) for CY2025 and CY2026-to-date via Cost Explorer's Savings Plans utilization report or CUR, in a format Accounting can reconcile against the $32,337.40/month recognition schedule.
3) Build a simple forecast (run-rate + planned workload changes) projecting utilization through the end of the commitment term(s), to answer whether 2026 utilization will exceed the ~$388K currently scheduled and whether the remaining ~$781K balance will be consumed before expiration.
4) Confirm commitment end date(s) for both plans -- this directly answers Accounting's 'Commitment period' question and is likely the fastest win.

Who owns AWS Cost Explorer/Savings Plans reporting on our side -- can this be assigned to that person/team? Given the finance-close relevance (year-end 2026 balance), recommend prioritizing above Backlog.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3805"
    },
    "result": {
      "key": "MZCLD-3805",
      "summary": "MoCo FinOps: AWS Prepaid usage back up for Accounting. ",
      "status": "Backlog",
      "description_text": "I was not able to pull usage details from the AWS billing console and the usage information is not available in the billing data. I am looking for help with gathering the necessary data for accounting. ticket:   Accounting is requesting: Hello Finance Team, As you are aware, we recorded $1,169,536.63 to Prepaid Usage in December 2025 related to our AWS committed spend. Based on my discussions with Kristin, there are two AWS commitment \u201cplans.\u201d One is currently being utilized, while the second has not yet begun to be used. We are currently recognizing\u00a0\u00a0$32,337.40 per month based on the AWS schedule. At the current rate, we would recognize approximately $388,048 during 2026 and have an estimated prepaid balance of  $781,487.83 remaining at year-end . Given the size of the remaining balance, I would like to better understand our expected utilization of the AWS commitment and how we are forecasting it. Specifically: 2026 utilization:  Do we expect to utilize more than the current scheduled amount of approximately $388K this year? If so, what is our current estimate? Commitment period:  What is the end date of our commitment with AWS? At the current rate, we are on track to utilize only about 33% of the original prepayment during 2026, so I want to make sure we understand the time-frame available to utilize the remaining commitment. Forecast:  How are we forecasting utilization of the remaining prepaid balance for the rest of 2026 and into 2027? Supporting documentation:  Kristin provided screenshots from the AWS dashboard demonstrating that the commitment is being utilized. However, the information is not particularly easy for Accounting to reconcile to the prepaid balance and expense recognition schedule. If we anticipate carrying a significant prepaid balance at December 31, 2026, I think we should have clear support for the remaining balance, the period over which the commitment can be utilized, and a forecast demonstrating how we expect to utilize it before the commitment expires. My primary concern is making sure we identify any potential under-utilization early enough to address it, rather than reaching the end of the commitment period with a significant unused balance. Thank you, Amanda Gallagher Global Accounting Team",
      "comment_count": 0,
      "comments": []
    }
  }
]

log