AgentaaS OS
IFO4 PLAYGROUND
P1
1
Run the Untagged Resource AuditP2
2
Design the Mandatory Tag SchemaP3
3
Implement Tag Enforcement PoliciesP4
4
Retroactive Tagging for Existing ResourcesP5
5
Build the Compliance DashboardInitiatives6
Capital Under Change$8.7M
Health Score54/100
Waste %31.2%
Value at Risk$5.1M
Phase 1: Audit
Run the Untagged Resource Audit
COMPLIANCE50 pts
Compliance Framework Coverage
Tag Compliance66% / 95% required
Cost Allocation71% / 90% required
Security Tags89% / 85% required
Untagged Resources by Service
EC2
412/890 untagged$34K/mo
S3
287/1140 untagged$9K/mo
RDS
164/380 untagged$20K/mo
Lambda
105/437 untagged$3K/mo
SITUATION
The AgentaaS Compliance Auditor has scanned all 2,847 resources. Results show 968 untagged resources (34%). The worst offenders are EC2 instances (412 untagged), S3 buckets (287 untagged), and RDS instances (164 untagged). Cost-center and team are the two required tags.
Health
54/100
Waste
31.2%
Spend
$156K/mo
Savings
$8K
AGENT INSIGHT
Compliance Auditor: if you tag only EC2 and RDS (576 resources), tagging compliance jumps from 66% to 86%. Add S3 and you reach 96%.
DECISION REQUIRED
Where should you prioritize tagging remediation first?
Hint: In FinOps, prioritize by financial impact, not by count or alphabetical order.