library
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 Storage buckets without lifecycle policy
Overview
Storage buckets can be costly to run, especially if they're rarely used, buckets without a lifecycle policy should be reviewed to determine if they're still required.
This pipeline detects storage buckets without a lifecycle policy 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
storage_buckets_without_lifecycle_policy_trigger_enabled
should be set totrue
as the default isfalse
.storage_buckets_without_lifecycle_policy_trigger_schedule
should be set to your desired running schedulestorage_buckets_without_lifecycle_policy_default_action
should be set to your desired action (i.e."notify"
for notifications or"delete_bucket"
to delete the bucket).
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, _ctx ->> 'connection_name' as credfrom gcp_storage_bucketwhere lifecycle_rules is null;
Schedule
15m