Start a cloud cost / FinOps scan of a linked account and return a job_id. Use
this when the user wants to find idle, unused or underutilized cloud resources,
review cloud spend, or estimate savings.
The provider comes from the connection, and **AWS is the only provider supported
today** (see `list_connections`). Other clouds will appear on this same tool as
connections for them become linkable; nothing else about the call changes.
READ-ONLY against your cloud: it reads resource metadata and monitoring metrics and
reports; it never changes, stops or deletes anything. (It does create a scan job
here and consume that account's scan quota, which is why this tool is not marked
read-only.)
On AWS it covers EC2 instances, EBS volumes and snapshots, RDS instances, Elastic
IPs, NAT Gateways, load balancers, VPCs and VPC endpoints, site-to-site VPN and
Transit Gateway attachments, Client VPN endpoints, Secrets Manager secrets,
CloudFront distributions and WAF web ACLs. Resource kinds outside that list are not
inspected, so a clean scan is not a claim that the whole bill is optimized.
`connection_id` picks which linked AWS account to scan (see `list_connections`).
Omit it to run against sample data — useful for showing the user what the output
looks like before any account is linked.
The scan runs asynchronously: poll `get_job(job_id)` roughly every 10 seconds
until status is COMPLETED (typically 1-3 minutes), then call
`list_cost_findings(job_id)`. Do NOT start another scan while one is running —
each scan consumes the account's monthly quota.
Pass `idempotency_key` (any unique string you choose) if you may retry on a
network error: a retry with the same key returns the original job instead of
starting a second scan.
ConnectorNo auth