Why
Manual ingestion requires weekly discipline that degrades over time. API automation ensures recommendations flow continuously into your ITSM tool without human intervention.
What
Build API integrations from cloud advisor services into your ITSM tool (Jira, ServiceNow, Linear) so recommendations are automatically created as tickets.
How
Build Per-Provider Integration
| Provider | Source API | Integration Method |
|---|---|---|
| AWS | Cost Optimization Hub API | Lambda (scheduled) → Jira/ServiceNow API |
| Azure | Advisor API (REST) | Azure Function (scheduled) → ITSM API |
| GCP | Recommender API | Cloud Function (scheduled) → ITSM API |
Each integration: poll for new recommendations daily, deduplicate against existing tickets, create tickets with: resource ID, recommendation type, estimated savings, affected account/team.
Implement Deduplication
Recommendations recur daily until implemented. Without dedup, your backlog fills with duplicates. Key: use resource ID + recommendation type as a composite key. If a ticket already exists for this resource+type, skip or update the existing ticket.
Test and Activate
Run for one week alongside manual extraction. Compare: are all manual findings captured by automation? Are duplicates handled? Activate and retire manual process.
Deliverable Checklist
- API integration built per provider
- Deduplication logic implemented
- Ticket template includes: resource, type, savings, team
- Parallel run validated
- Manual extraction process retired