Skip to content

Implement resources — list AWS resources via Resource Groups Tagging API #110

Description

@glennmichael123

Implementation issue split out from #107.

Replace the mock-data body in packages/ts-cloud/bin/commands/cost.ts (resources command) with real implementation:

  • Use AWS Resource Groups Tagging API (tagging:GetResources) for a unified resource list across services. Falls back to per-service Describe* / List* calls if tagging is incomplete.
  • Honor the existing --type <ec2|rds|s3|...> filter.

Acceptance

Notes

  • "Total Cost/mo" column probably needs to come from a Cost Explorer call grouped by RESOURCE_ID — that's only available with CUR (Cost and Usage Reports) configured. If CUR isn't set up, blank that column or document the prereq.

Related

  • #107 — tactical guard

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions