Skip to main content

← Back to parent Epic

MAZENG-FT-31 · Estimate the cost of the current cloud design

Feature intent

A cloud designer needs to understand the expected cost of the resources on the saved canvas before infrastructure is created.

Why it matters

A cloud designer needs to understand the expected cost of the resources on the saved canvas before infrastructure is created.

Expected outcome

The designer can compare the total and per-resource cost impact of the current design before making a deployment decision.

In scope

  • Price the saved resources in the current project.
  • Present total monthly cost and per-resource hourly and monthly estimates.
  • Retain timestamped project-cost history when an estimate changes.
Delivery status
IN_BACKLOG
Owner
RootAtSkic
Parent Epic
MAZENG-EP-9
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    The current project is priced from its saved canvas resources.

  2. 02

    The user sees total monthly cost and a per-resource hourly/monthly breakdown.

  3. 03

    Unsupported, consumption-priced, free, and invalid configurations are distinguished.

  4. 04

    A changed project estimate creates a timestamped history record without duplicating an unchanged value.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Pricing depends on a reliable provider and normalized resource configurations.
  • Legacy behavior is USD-only, commonly assumes us-east-1, and leaves many resources unsupported.
  • The legacy source contains a committed pricing API key that must not be carried into a future solution.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source