Policy types for @turbot/gcp-memorystore

• GCP > Memorystore > API Enabled
• GCP > Memorystore > Approved Regions [Default]
• GCP > Memorystore > CMDB
• GCP > Memorystore > Enabled
• GCP > Memorystore > Instance > Active
• GCP > Memorystore > Instance > Active > Age
• GCP > Memorystore > Instance > Active > Last Modified
• GCP > Memorystore > Instance > Approved
• GCP > Memorystore > Instance > Approved > Custom
• GCP > Memorystore > Instance > Approved > Regions
• GCP > Memorystore > Instance > Approved > Usage
• GCP > Memorystore > Instance > CMDB
• GCP > Memorystore > Instance > Labels
• GCP > Memorystore > Instance > Labels > Template
• GCP > Memorystore > Instance > Regions
• GCP > Memorystore > Instance > Usage
• GCP > Memorystore > Instance > Usage > Limit
• GCP > Memorystore > Labels Template [Default]
• GCP > Memorystore > Permissions
• GCP > Memorystore > Permissions > Levels
• GCP > Memorystore > Permissions > Levels > Modifiers
• GCP > Memorystore > Regions
• GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-memorystore
• GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-memorystore
• GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-memorystore

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.

[
  "Skip",
  "Check: Disabled",
  "Check: Enabled",
  "Check: Enabled if Memorystore > Enabled",
  "Enforce: Disabled",
  "Enforce: Enabled",
  "Enforce: Enabled if Memorystore > Enabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Disabled",
    "Check: Enabled",
    "Check: Enabled if Memorystore > Enabled",
    "Enforce: Disabled",
    "Enforce: Enabled",
    "Enforce: Enabled if Memorystore > Enabled"
  ],
  "default": "Skip"
}

GCP > Memorystore > Approved Regions [Default]

A list of GCP regions in which GCP Memorystore resources are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy is the default value for all GCP Memorystore resources' Approved > Regions policies.

"{\n  regions: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/approvedRegionsDefault\") {\n    value\n  }\n}\n"

"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Memorystore > CMDB

Configure whether to record and synchronize details for the GCP Memorystore memorystore into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB. All policies and controls in Turbot are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Disabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled"
}

GCP > Memorystore > Enabled

Enabled Memorystore.

[
  "Enabled",
  "Enabled: Metadata Only",
  "Disabled"
]

{
  "type": "string",
  "enum": [
    "Enabled",
    "Enabled: Metadata Only",
    "Disabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Disabled"
}

GCP > Memorystore > Instance > Active

Determine the action to take when an GCP Memorystore instance, based on the GCP > Memorystore > Instance > Active > * policies.

The 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.

[
  "Skip",
  "Check: Active",
  "Enforce: Delete inactive with 1 day warning",
  "Enforce: Delete inactive with 3 days warning",
  "Enforce: Delete inactive with 7 days warning",
  "Enforce: Delete inactive with 14 days warning",
  "Enforce: Delete inactive with 30 days warning",
  "Enforce: Delete inactive with 60 days warning",
  "Enforce: Delete inactive with 90 days warning",
  "Enforce: Delete inactive with 180 days warning",
  "Enforce: Delete inactive with 365 days warning"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Active",
    "Enforce: Delete inactive with 1 day warning",
    "Enforce: Delete inactive with 3 days warning",
    "Enforce: Delete inactive with 7 days warning",
    "Enforce: Delete inactive with 14 days warning",
    "Enforce: Delete inactive with 30 days warning",
    "Enforce: Delete inactive with 60 days warning",
    "Enforce: Delete inactive with 90 days warning",
    "Enforce: Delete inactive with 180 days warning",
    "Enforce: Delete inactive with 365 days warning"
  ],
  "example": [
    "Check: Active"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Active > Age

The age after which the GCP Memorystore instance is no longer considered active. If a create time is unavailable, the time Turbot discovered the resource is used.

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.

[
  "Skip",
  "Force inactive if age > 1 day",
  "Force inactive if age > 3 days",
  "Force inactive if age > 7 days",
  "Force inactive if age > 14 days",
  "Force inactive if age > 30 days",
  "Force inactive if age > 60 days",
  "Force inactive if age > 90 days",
  "Force inactive if age > 180 days",
  "Force inactive if age > 365 days"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Force inactive if age > 1 day",
    "Force inactive if age > 3 days",
    "Force inactive if age > 7 days",
    "Force inactive if age > 14 days",
    "Force inactive if age > 30 days",
    "Force inactive if age > 60 days",
    "Force inactive if age > 90 days",
    "Force inactive if age > 180 days",
    "Force inactive if age > 365 days"
  ],
  "example": [
    "Force inactive if age > 90 days"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Active > Last Modified

The number of days since the GCP Memorystore instance was last modified before it is considered inactive.

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.

[
  "Skip",
  "Active if last modified <= 1 day",
  "Active if last modified <= 3 days",
  "Active if last modified <= 7 days",
  "Active if last modified <= 14 days",
  "Active if last modified <= 30 days",
  "Active if last modified <= 60 days",
  "Active if last modified <= 90 days",
  "Active if last modified <= 180 days",
  "Active if last modified <= 365 days",
  "Force active if last modified <= 1 day",
  "Force active if last modified <= 3 days",
  "Force active if last modified <= 7 days",
  "Force active if last modified <= 14 days",
  "Force active if last modified <= 30 days",
  "Force active if last modified <= 60 days",
  "Force active if last modified <= 90 days",
  "Force active if last modified <= 180 days",
  "Force active if last modified <= 365 days"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Active if last modified <= 1 day",
    "Active if last modified <= 3 days",
    "Active if last modified <= 7 days",
    "Active if last modified <= 14 days",
    "Active if last modified <= 30 days",
    "Active if last modified <= 60 days",
    "Active if last modified <= 90 days",
    "Active if last modified <= 180 days",
    "Active if last modified <= 365 days",
    "Force active if last modified <= 1 day",
    "Force active if last modified <= 3 days",
    "Force active if last modified <= 7 days",
    "Force active if last modified <= 14 days",
    "Force active if last modified <= 30 days",
    "Force active if last modified <= 60 days",
    "Force active if last modified <= 90 days",
    "Force active if last modified <= 180 days",
    "Force active if last modified <= 365 days"
  ],
  "example": [
    "Active if last modified <= 90 days"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Approved

Determine the action to take 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.

[
  "Skip",
  "Check: Approved",
  "Enforce: Delete unapproved if new"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Approved",
    "Enforce: Delete unapproved if new"
  ],
  "example": [
    "Check: Approved"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Approved > Custom

Determine whether the GCP Memorystore instance is allowed to exist. This policy will be evaluated by the Approved control. If a GCP Memorystore instance is not approved, it will be subject to the action specified in the GCP > Memorystore > Instance > Approved policy. See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

{
  "example": [
    "Approved",
    "Not approved",
    "Skip",
    {
      "result": "Approved"
    },
    {
      "title": "string",
      "result": "Not approved"
    },
    {
      "title": "string",
      "result": "Approved",
      "message": "string"
    },
    [
      {
        "title": "string",
        "result": "Approved",
        "message": "string"
      },
      {
        "title": "string",
        "result": "Not approved",
        "message": "string"
      }
    ]
  ],
  "anyOf": [
    {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,32}$"
          },
          "message": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,128}$"
          },
          "result": {
            "type": "string",
            "pattern": "^(Approved|Not approved|Skip)$"
          }
        },
        "required": [
          "result"
        ],
        "additionalProperties": false
      }
    },
    {
      "type": "object",
      "properties": {
        "title": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,32}$"
        },
        "message": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,128}$"
        },
        "result": {
          "type": "string",
          "pattern": "^(Approved|Not approved|Skip)$"
        }
      },
      "required": [
        "result"
      ],
      "additionalProperties": false
    },
    {
      "type": "string",
      "pattern": "^(Approved|Not approved|Skip)$"
    }
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Approved > Regions

A list of GCP regions in which GCP Memorystore instances are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Memorystore instance is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Memorystore > Instance > Approved policy.

See Approved for more information.

"{\n  regions: policyValue(uri:\"tmod:@turbot/gcp-memorystore#/policy/types/memorystoreApprovedRegionsDefault\") {\n    value\n  }\n}\n"

"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Memorystore > Instance > Approved > Usage

Determine whether the GCP Memorystore instance is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Memorystore instance is not approved, it will be subject to the action specified in the GCP > Memorystore > Instance > Approved policy.

See Approved for more information.

[
  "Not approved",
  "Approved",
  "Approved if GCP > Memorystore > Enabled"
]

{
  "type": "string",
  "enum": [
    "Not approved",
    "Approved",
    "Approved if GCP > Memorystore > Enabled"
  ],
  "example": [
    "Not approved"
  ],
  "default": "Approved if GCP > Memorystore > Enabled"
}

GCP > Memorystore > Instance > CMDB

Configure whether to 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. All policies and controls in Turbot are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

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.

(Note: Setting CMDB to "Skip" will also pause these changes.)

[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Enabled if Memorystore API is enabled",
  "Enforce: Disabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Enabled if Memorystore API is enabled",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled if Memorystore API is enabled"
}

GCP > Memorystore > Instance > Labels

Determine the action to take when an GCP Memorystore instance labels are not updated based on the GCP > Memorystore > Instance > Labels > * policies.

The control ensure GCP Memorystore instance labels include labels defined in GCP > Memorystore > Instance > Labels > Template.

Labels not defined in Instance Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

[
  "Skip",
  "Check: Labels are correct",
  "Enforce: Set labels"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Labels are correct",
    "Enforce: Set labels"
  ],
  "example": [
    "Check: Labels are correct"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Labels > Template

The template is used to generate the keys and values for GCP Memorystore instance.

Labels not defined in Instance Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

[
  "{\n  project {\n    turbot {\n      id\n    }\n  }\n}\n",
  "{\n  defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-memorystore#/policy/types/memorystoreLabelsTemplate\" resourceId: \"{{ $.project.turbot.id }}\") {\n    value\n  }\n}\n"
]

"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"

GCP > Memorystore > Instance > Regions

A list of GCP regions in which GCP Memorystore instances are supported for use.

Any instances in a region not listed here will not be recorded in CMDB.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

"{\n  regions: policyValue(uri:\"tmod:@turbot/gcp-memorystore#/policy/types/memorystoreRegionsDefault\") {\n    value\n  }\n}\n"

"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Memorystore > Instance > Usage

Configure the number of GCP Memorystore instances that can be used for this region and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Memorystore > Instance > Usage policy.

[
  "Skip",
  "Check: Usage <= 85% of Limit",
  "Check: Usage <= 100% of Limit"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Usage <= 85% of Limit",
    "Check: Usage <= 100% of Limit"
  ],
  "example": [
    "Check: Usage <= 85% of Limit"
  ],
  "default": "Skip"
}

GCP > Memorystore > Instance > Usage > Limit

Maximum number of items that can be created for this region

{
  "type": "integer",
  "minimum": 0,
  "default": 100
}

GCP > Memorystore > Labels Template [Default]

A template used to generate the keys and values for GCP Memorystore resources.

By default, all Memorystore resource Labels > Template policies will use this value.

"{\n  defaultLabels: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/defaultLabelsTemplate\") {\n    value\n  }\n}\n"

"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"

GCP > Memorystore > Permissions

Configure whether permissions policies are in effect for GCP Memorystore. This setting does not affect Project level permissions (GCP/Admin, GCP/Owner, etc).

Note: The behavior of this policy depends on the value of GCP > Permissions.

[
  "Enabled",
  "Disabled",
  "Enabled if GCP > Memorystore > Enabled"
]

{
  "type": "string",
  "enum": [
    "Enabled",
    "Disabled",
    "Enabled if GCP > Memorystore > Enabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Enabled if GCP > Memorystore > Enabled"
}

GCP > Memorystore > Permissions > Levels

Define the permissions levels that can be used to grant access to Memorystore an GCP project. Permissions levels defined will appear in the UI to assign access to Turbot users.

Note: Some services do not use all permissions levels, and any permissions level that has no permissions associated will not be created even if it is selected here.

[
  "{\n  item: project {\n    turbot{\n      id\n    }\n  }\n}\n",
  "{\n  availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyType:'tmod:@turbot/gcp-iam#/policy/types/permissionsLevelsDefault'\") {\n    items {\n      value\n    }\n  }\n}\n"
]

"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"

{
  "type": "array",
  "items": {
    "type": "string",
    "enum": [
      "Metadata",
      "ReadOnly",
      "Operator",
      "Admin",
      "Owner"
    ]
  }
}

GCP > Memorystore > Permissions > Levels > Modifiers

A map of GCP API to Turbot Permission Level used to customize Turbot's standard permissions. You can add, remove or redefine the mapping of GCP API operations to Turbot permissions levels here.

Note: Modifiers are cumulative - if you add a permission to the metadata level, it is also added to readOnly, operator and admin. Modifier policies set here will “roll up” to the GCP level too - if you add a permission to Admin, it will be granted to GCP/Storage/Admin and also GCP/Admin

example:
  - "storage.bucket.create": admin
  - "sql.database.create": metadata

GCP > Memorystore > Regions

A list of GCP regions in which GCP Memorystore resources are supported for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy is the default value for all GCP Memorystore resources' Regions policies.

{
  "allOf": [
    {
      "$ref": "gcp#/definitions/regionNameMatcherList"
    },
    {
      "default": [
        "asia-east1",
        "asia-east2",
        "asia-northeast1",
        "asia-northeast2",
        "asia-south1",
        "asia-southeast1",
        "australia-southeast1",
        "europe-north1",
        "europe-west1",
        "europe-west2",
        "europe-west3",
        "europe-west4",
        "europe-west6",
        "northamerica-northeast1",
        "southamerica-east1",
        "us-central1",
        "us-east1",
        "us-east4",
        "us-west1",
        "us-west2"
      ]
    }
  ]
}

GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-memorystore

GCP logs advanced filter used to specify a subset of log entries that is forwarded to the Turbot Event Handlers by the logging sink on behalf of GCP Memorystore.

{
  "type": "string",
  "default": "(resource.type = audited_resource AND (protoPayload.authorizationInfo.permission = redis.instances.create OR protoPayload.authorizationInfo.permission = redis.instances.update OR protoPayload.authorizationInfo.permission = redis.instances.delete) AND severity>=INFO AND severity<ERROR)"
}

GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-memorystore

A calculated policy that Turbot uses to create a compiled list of ALL permission levels for GCP Memorystore that is used as input to the stack that manages the Turbot IAM permissions objects.

GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-memorystore

A calculated policy that Turbot uses to create a compiled list of ALL permissions for GCP Memorystore that is used as input to the control that manages the IAM stack.