Skip to content

Phase 2: AWS — configure budget for GPU spend (account 968589500754) #178

Description

@elasticdotventures

Summary

Phase 2 tracking issue for the coordinated finops/auth-renewal plan (see #111 for the full plan and the correction explaining that this is now a real crates/ledgerr-cloud build, not a fix to pre-existing code).

This is a human-only action item — creating a budget with a real dollar ceiling is a business decision, not something an agent should invent.

Action required

  1. Sign in to AWS Console → Cost Management → Budgets
  2. Create a monthly cost budget for account 968589500754 covering GPU-related services (SageMaker, EC2, etc.) — pick an actual dollar cap.

Auth precondition: AWS_ACCESS_KEY_ID env var set, aws sts get-caller-identity succeeding (already verified working as of 2026-06-28 — only the budget object itself is missing).

Verification

Once created, ledgerr-cloud's AWS provider (Phase 1/3, tracked in #111) should report RECONCILED with the configured cap instead of UNSET.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfinopsFinancial operations and cloud cost management

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions