Supported AWS Sources and Coverage

What the AWS-first platform reads and what it does not claim.

CoreFinOps v1 is intentionally AWS-first. Coverage is shaped by the deployed customer read-only role, service enrollment, available regions, and which source data the account actually produces.

Tier-1 resource inventory

The original v1 inventory includes EC2, EBS, RDS/Aurora, NAT Gateway, ELB/ALB/NLB, and Lambda at supported API/region scopes. Collection obtains current configuration and identifiers; it is not a complete CMDB or every-service AWS inventory.

Billing and financial data

Supported AWS cost ingestion is based on configured CUR 2.0 / AWS Data Exports in S3. Connection alone does not grant access to every billing bucket or create an export automatically. Billing scope (payer or linked account) influences what source facts are available.

Native optimization sources

Cost Optimization Hub and Compute Optimizer provide supported recommendations where enrolled and permitted. Trusted Advisor is not a required v1 recommendation feed. Availability varies by account eligibility, supported services and AWS source readiness.

Boundary of control

CoreFinOps does not modify customer AWS resources, purchase commitments or deploy workloads. The AWS IAM role is intended for read-oriented collection/validation. Any future remediation requires a separately reviewed consent and execution design.

Coverage labels

Use explicit labels for supported and collected, supported but unavailable, permission-limited, stale, and not supported. An empty result must not be presented as proof that no resource or cost exists in the AWS account.