Control types for @turbot/gcp-memorystore

• GCP > Memorystore > API Enabled
• GCP > Memorystore > CMDB
• GCP > Memorystore > Discovery
• GCP > Memorystore > Instance > Active
• GCP > Memorystore > Instance > Approved
• GCP > Memorystore > Instance > CMDB
• GCP > Memorystore > Instance > Discovery
• GCP > Memorystore > Instance > Labels
• GCP > Memorystore > Instance > Usage

GCP > Memorystore > API Enabled

Check whether GCP Memorystore API is enabled.

API Enabled refers specifically to the API state of a service in a cloud project. This control determines whether the API state is set as per desired level.

The GCP > Memorystore > API Enabled control compares the API state against the API Enabled policies, raises an alarm, and takes the defined enforcement action.

GCP > Memorystore > CMDB

Record and synchronize details for the GCP Memorystore into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.

Note: If CMDB is set to Skip for a resource, then it will not be added to the CMDB, and no controls that target it will run.

GCP > Memorystore > Discovery

Discover GCP Memorystore resources and add them to the CMDB.

The Discovery control is tasked with identifying instances for a particular resource. The Discovery control will periodically search for new target resources and save them to the Turbot CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

GCP > Memorystore > Instance > Active

Take an action when an GCP Memorystore instance is not active based on the GCP > Memorystore > Instance > Active > * policies.

The Active control determines whether the resource is in active use, and if not, has the ability to delete / cleanup the resource. When running an automated compliance environment, it's common to end up with a wide range of alarms that are difficult and time consuming to clear. The Active control brings automated, well-defined control to this process.

The Active control checks the status of all defined Active policies for the resource (GCP > Memorystore > Instance > Active > *), raises an alarm, and takes the defined enforcement action. Each Active sub-policy can calculate a status of active, inactive or skipped. Generally, if the resource appears to be Active for any reason it will be considered Active.

Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.

See Active for more information.

GCP > Memorystore > Instance > Approved

Take an action when a GCP Memorystore instance is not approved based on GCP > Memorystore > Instance > Approved > * policies.

The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

GCP > Memorystore > Instance > CMDB

Record and synchronize details for the GCP Memorystore instance into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.

Note: If CMDB is set to Skip for a resource, then it will not be added to the CMDB, and no controls that target it will run.

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Memorystore > Instance > Regions policy, the CMDB control will delete the resource from the CMDB.

GCP > Memorystore > Instance > Discovery

Discover GCP Memorystore instance resources and add them to the CMDB.

The Discovery control is tasked with identifying instances for a particular resource. The Discovery control will periodically search for new target resources and save them to the Turbot CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note that Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in GCP > Memorystore > Instance > Regions policy, the CMDB control will delete the resource from the CMDB.

GCP > Memorystore > Instance > Labels

Take an action when an GCP Memorystore instance labels is not updated based on the GCP > Memorystore > Instance > Labels > * policies.

If the resource is not updated with the labels defined in GCP > Memorystore > Instance > Labels > Template, this control raises an alarm and takes the defined enforcement action.

See Labels for more information.

GCP > Memorystore > Instance > Usage

The Usage control determines whether the number of GCP Memorystore instance resources exceeds the configured usage limit for this region.

You can configure the behavior of this control with the GCP > Memorystore > Instance > Usage policy, and set the limit with the GCP > Memorystore > Instance > Usage > Limit policy.