standard
turbot/gcp_thrifty
- Detect & correct AlloyDB clusters exceeding max age
- Detect & correct long-running AlloyDB instances exceeding max age
- Detect & correct Compute addresses if unattached
- Detect & correct Compute disks attached to stopped instances
- Detect & correct Compute disks exceeding max size
- Detect & correct Compute disks if unattached
- Detect & correct Compute disks with low usage
- Detect & correct Compute engine instances exceeding max age
- Detect & correct Compute engine instances large
- Detect & correct Compute instances with low utilization
- Detect & correct Compute node groups without autoscaling
- Detect & correct Compute snapshots exceeding max age
- Detect & correct Dataproc clusters without autoscaling
- Detect & correct Kubernetes clusters exceeding max age
- Detect & correct GKE clusters without vertical pod autoscaling
- Detect & correct Logging Buckets with high retention period
- Detect & correct Redis instances exceeding max age
- Detect & correct SQL database instances exceeding max age
- Detect & correct SQL DB instances with low connection count
- Detect & correct SQL DB instances with low cpu utilization
- Detect & correct Storage buckets without lifecycle policies
- Detect & correct VPN gateways with no tunnels
Get Involved
Version
Detect & correct VPN Gateways with no tunnels
Overview
VPN Gateways can be costly to run, especially if they're rarely used, gateways with no tunnels should be reviewed to determine if they're still required.
This query trigger detects VPN Gateways with no tunnels and then either sends a notification or attempts to perform a predefined corrective action.
Getting Started
By default, this trigger is disabled, however it can be configured by setting the below variables
vpn_gateways_with_no_tunnels_trigger_enabled
should be set totrue
as the default isfalse
.vpn_gateways_with_no_tunnels_trigger_schedule
should be set to your desired running schedulevpn_gateways_with_no_tunnels_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_vpn_gateway"
to delete the gateway).
Then starting the server:
flowpipe server
or if you've set the variables in a .fpvars
file:
flowpipe server --var-file=/path/to/your.fpvars
Query
select concat(name, ' [', location, '/', project, ']') as title, name, project, sp_connection_name as conn, locationfrom gcp_compute_target_vpn_gatewaywhere tunnels is null;
Schedule
15m
Tags
category = Cost
class = unused
plugin = gcp
service = GCP/Network