Problem statement
Hi — first, thank you for this project and all the work on CloudBurn; I discovered it through the AWS Community Builders program and it’s already helped me reduce risky AWS spend in CI and live environments.
Feature request
Summary: I’d love to see CloudBurn extended to support additional cloud providers (specifically Google Cloud Platform and Microsoft Azure) so teams using multi‑cloud environments can apply the same cost‑policy and remediation tooling.
Why it matters: Many teams run multi‑cloud setups or are migrating between providers; having consistent policy checks and automated remediation across AWS, GCP, and Azure would reduce risk, simplify governance, and increase CloudBurn’s applicability.
Suggested scope / approach:
Provider adapters: add modular adapters for GCP and Azure to translate provider-specific resource metadata into CloudBurn’s internal policy model.
Authentication: document recommended auth patterns (service accounts/managed identities) and least‑privilege roles for each provider.
CI integration: examples for GitHub Actions and common CI systems showing multi‑cloud scanning and blocking workflows.
Incremental rollout: start with read‑only scanning for common cost resources (compute, storage, DB) and then expand to remediation actions once the adapter surface stabilizes.
Proposed solution
Implementation notes / ideas:
Reuse the existing plugin/adapter pattern (if any) to keep core logic provider‑agnostic.
Consider mapping common resource attributes (SKU, size, region, tags) to a unified cost/policy schema.
Provide example policies for equivalent resources across clouds (e.g., EC2 vs GCE vs Azure VM).
Alternatives considered
No response
Area
Free vs paid impact
No response
Problem statement
Hi — first, thank you for this project and all the work on CloudBurn; I discovered it through the AWS Community Builders program and it’s already helped me reduce risky AWS spend in CI and live environments.
Feature request
Summary: I’d love to see CloudBurn extended to support additional cloud providers (specifically Google Cloud Platform and Microsoft Azure) so teams using multi‑cloud environments can apply the same cost‑policy and remediation tooling.
Why it matters: Many teams run multi‑cloud setups or are migrating between providers; having consistent policy checks and automated remediation across AWS, GCP, and Azure would reduce risk, simplify governance, and increase CloudBurn’s applicability.
Suggested scope / approach:
Provider adapters: add modular adapters for GCP and Azure to translate provider-specific resource metadata into CloudBurn’s internal policy model.
Authentication: document recommended auth patterns (service accounts/managed identities) and least‑privilege roles for each provider.
CI integration: examples for GitHub Actions and common CI systems showing multi‑cloud scanning and blocking workflows.
Incremental rollout: start with read‑only scanning for common cost resources (compute, storage, DB) and then expand to remediation actions once the adapter surface stabilizes.
Proposed solution
Implementation notes / ideas:
Reuse the existing plugin/adapter pattern (if any) to keep core logic provider‑agnostic.
Consider mapping common resource attributes (SKU, size, region, tags) to a unified cost/policy schema.
Provide example policies for equivalent resources across clouds (e.g., EC2 vs GCE vs Azure VM).
Alternatives considered
No response
Area
Free vs paid impact
No response