# ControlScopeProperty

A framework consists of one or more controls.

Each control has its own control scope. The control scope can include one or more resource types, a combination of a tag key and value, or a combination of one resource type and one resource ID. If no scope is specified, evaluations for the rule are triggered when any resource in your recording group changes in configuration.

> To set a control scope that includes all of a particular resource, leave the `ControlScope` empty or do not pass it when calling `CreateFramework` .

- Source: Generated code
- Type last changed: v2.93.0 · 23 Aug 2023

## Example

```ts
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_backup as backup } from 'aws-cdk-lib';
const controlScopeProperty: backup.CfnFramework.ControlScopeProperty = {
  complianceResourceIds: ['complianceResourceIds'],
  complianceResourceTypes: ['complianceResourceTypes'],
  tags: [{
    key: 'key',
    value: 'value',
  }],
};
```

## Properties

- `complianceResourceIds`: string[] — The ID of the only AWS resource that you want your control scope to contain.

- `complianceResourceTypes`: string[] — Describes whether the control scope includes one or more types of resources, such as `EFS` or `RDS` .

- `tags`: [CfnTag](/cdk/api/v2/docs/aws-cdk-lib.CfnTag.html)[] — The tag key-value pair applied to those AWS resources that you want to trigger an evaluation for a rule.

  A maximum of one key-value pair can be provided. The tag value is optional, but it cannot be an empty string if you are creating or editing a framework from the console (though the value can be an empty string when included in a CloudFormation template).

  The structure to assign a tag is: `[{"Key":"string","Value":"string"}]` .
