VPC
VPC Interface endpoint Idle
Identifying VPC interface endpoints that are running but not actively transmitting data could represent unused endpoints costs. By identifying idle interface endpoints.
This recommendation specifically evaluates the usage of VPC Interface Endpoints (not Gateway Endpoints) based on the following logic:
Data Signals Evaluated:
-
VpcEndpoint-Hours: Indicates the total hours the endpoint has been active.
-
VpceEndpoint-Bytes: Tracks the amount of traffic passing through the endpoint.
Algorithm: -
If an endpoint shows activity (VpcEndpoint-Hours > 0) but no data transfer (VpceEndpoint-Bytes = 0 or a different value set in the recommendation preference) for a defined period, it is considered idle.
Recommendation Trigger: -
The recommendation is generated only when an endpoint is consistently running without any traffic over the specified analysis window.
- Days to Check, default 30 days.
Specifies the evaluation period to monitor endpoint activity. Over this time, the endpoint's traffic and uptime are analyzed to determine if it is idle. - Traffic Amount Through Endpoint default 0 bytes.
Sets the threshold for identifying idle endpoints. If traffic is equal to or below this value over the evaluation period, the endpoint is flagged as idle. - Minimum Annual Cost, default $10.
Ensures recommendations focus on endpoints that incur meaningful costs. Endpoints with annual costs below this threshold are not flagged, even if idle, to avoid unnecessary focus on negligible savings.
Umbrella.
Yes.
NAT Gateway Idle
This recommendation identifies idle NAT Gateway services that can be deleted.
Identifying NAT Gateway service that had no connections for the past 7 days (subject to preferences).
Umbrella.
Yes.
Since we can't access AWS using APIs we rely on the invoice only, hence the recommendation has a different behaviour:
- Detect and recommend idle NAT Gateway based on the Resource ID from the CUR.
- New preference was added only for GovCloud: 'Max Traffic Volume', default 0.05.
When there's a cost for Usage Type='NatGateway-Hours' and no Usage Type='NatGateway-Byte' and the Max Traffic Volume meets the preference. - In that way we can see that there's a cost for data transferred out but there's no cost for hours.
Updated over 1 year ago
