Amazon API Gateway REST API
Does ZopNight manage Amazon API Gateway REST API?
Amazon API Gateway REST APIs bill per million requests, so an abandoned API costs nothing while idle. ZopNight discovers every REST API from the apigateway:restapis type, and RC-166 deliberately abstains rather than claim a saving, because Cost Explorer reports no per-API figure to recover.
Rules that fire on Amazon API Gateway REST API
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost attribution only; deletion is a remediation workflow, not a schedule. |
Amazon API Gateway REST APIs sit in front of Lambda functions, HTTP endpoints, and private services in a VPC. The meter is the request, not the hour, which makes an abandoned API a governance problem long before it is a cost problem.
Requests bill, the idle API does not
A REST API with no traffic bills nothing for its existence. There is no hourly charge for the API itself, so the usual idle-resource logic, which assumes a resource burns money while nobody uses it, simply does not apply. The exception is a provisioned cache, which bills per hour for as long as it is attached regardless of hit rate. That inverts the normal priority: the reason to clean up a dead REST API is the route it still exposes and the stage config nobody reviews, not the invoice.
Why RC-166 abstains instead of estimating
RC-166 Idle API Gateway exists, is wired into the rule set, and reports nothing on live data. Per-API cost resolves to zero in the cost pipeline because the request meter is not attributable to an individual API, and the rule refuses to multiply a zero by a savings fraction and present the result as a recommendation. An abstain is the honest output when the input is missing. Rules that guess in this position are the reason a directory like this one publishes the abstain condition rather than hiding it.
What discovery collects, and what it does not
Discovery runs through AWS Resource Explorer 2 on the six-hour cycle, reading the apigateway:restapis type into the inventory with its ARN, region, and tags. That is the whole picture: no per-stage request counts, no latency series. The declared permissions match that narrow scope, and no read action on the API Gateway control plane is claimed beyond what Resource Explorer needs.
Deletion is the only write lever
An abandoned REST API can be removed through the delete remediation workflow, which uses apigateway:DELETE. There is no start or stop, so a REST API never appears on a schedule. Treat the delete path as cleanup with a review step, not as an off switch you can put on a calendar.
Finding the APIs nobody calls
The console lists every API under API Gateway, and each stage carries its own deployment history. Sorted by last deployment date, the abandoned ones tend to identify themselves: a stage last deployed two years ago, wired to a Lambda function that no longer exists.