Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Config can respond with.

Structs

• AccountAggregationSource

  A collection of accounts and regions.

• AggregateComplianceByConfigRule

  Indicates whether an Config rule is compliant based on account ID, region, compliance, and rule name.

  A rule is compliant if all of the resources that the rule evaluated comply with it. It is noncompliant if any of these resources do not comply.

• AggregateComplianceByConformancePack

  Provides aggregate compliance of the conformance pack. Indicates whether a conformance pack is compliant based on the name of the conformance pack, account ID, and region.

  A conformance pack is compliant if all of the rules in a conformance packs are compliant. It is noncompliant if any of the rules are not compliant. The compliance status of a conformance pack is INSUFFICIENT_DATA only if all rules within a conformance pack cannot be evaluated due to insufficient data. If some of the rules in a conformance pack are compliant but the compliance status of other rules in that same conformance pack is INSUFFICIENT_DATA, the conformance pack shows compliant.

• AggregateComplianceCount

  Returns the number of compliant and noncompliant rules for one or more accounts and regions in an aggregator.

• AggregateConformancePackCompliance

  Provides the number of compliant and noncompliant rules within a conformance pack. Also provides the compliance status of the conformance pack and the total rule count which includes compliant rules, noncompliant rules, and rules that cannot be evaluated due to insufficient data.

  A conformance pack is compliant if all of the rules in a conformance packs are compliant. It is noncompliant if any of the rules are not compliant. The compliance status of a conformance pack is INSUFFICIENT_DATA only if all rules within a conformance pack cannot be evaluated due to insufficient data. If some of the rules in a conformance pack are compliant but the compliance status of other rules in that same conformance pack is INSUFFICIENT_DATA, the conformance pack shows compliant.

• AggregateConformancePackComplianceCount

  The number of conformance packs that are compliant and noncompliant.

• AggregateConformancePackComplianceFilters

  Filters the conformance packs based on an account ID, region, compliance type, and the name of the conformance pack.

• AggregateConformancePackComplianceSummary

  Provides a summary of compliance based on either account ID or region.

• AggregateConformancePackComplianceSummaryFilters

  Filters the results based on account ID and region.

• AggregateEvaluationResult

  The details of an Config evaluation for an account ID and region in an aggregator. Provides the Amazon Web Services resource that was evaluated, the compliance of the resource, related time stamps, and supplementary information.

• AggregateResourceIdentifier

  The details that identify a resource that is collected by Config aggregator, including the resource type, ID, (if available) the custom resource name, the source account, and source region.

• AggregatedSourceStatus

  The current sync status between the source and the aggregator account.

• AggregationAuthorization

  An object that represents the authorizations granted to aggregator accounts and regions.

• AggregatorFilterResourceType

  An object to filter the configuration recorders based on the resource types in scope for recording.

• AggregatorFilterServicePrincipal

  An object to filter service-linked configuration recorders in an aggregator based on the linked Amazon Web Services service.

• AggregatorFilters

  An object to filter the data you specify for an aggregator.

• BaseConfigurationItem

  The detailed configurations of a specified resource.

• Compliance

  Indicates whether an Amazon Web Services resource or Config rule is compliant and provides the number of contributors that affect the compliance.

• ComplianceByConfigRule

  Indicates whether an Config rule is compliant. A rule is compliant if all of the resources that the rule evaluated comply with it. A rule is noncompliant if any of these resources do not comply.

• ComplianceByResource

  Indicates whether an Amazon Web Services resource that is evaluated according to one or more Config rules is compliant. A resource is compliant if it complies with all of the rules that evaluate it. A resource is noncompliant if it does not comply with one or more of these rules.

• ComplianceContributorCount

  The number of Amazon Web Services resources or Config rules responsible for the current compliance of the item, up to a maximum number.

• ComplianceSummary

  The number of Config rules or Amazon Web Services resources that are compliant and noncompliant.

• ComplianceSummaryByResourceType

  The number of Amazon Web Services resources of a specific type that are compliant or noncompliant, up to a maximum of 100 for each.

• ConfigExportDeliveryInfo

  Provides status of the delivery of the snapshot or the configuration history to the specified Amazon S3 bucket. Also provides the status of notifications about the Amazon S3 delivery to the specified Amazon SNS topic.

• ConfigRule

  Config rules evaluate the configuration settings of your Amazon Web Services resources. A rule can run when Config detects a configuration change to an Amazon Web Services resource or at a periodic frequency that you choose (for example, every 24 hours). There are two types of rules: Config Managed Rules and Config Custom Rules.

  Config Managed Rules are predefined, customizable rules created by Config. For a list of managed rules, see List of Config Managed Rules.

  Config Custom Rules are rules that you create from scratch. There are two ways to create Config custom rules: with Lambda functions ( Lambda Developer Guide) and with Guard (Guard GitHub Repository), a policy-as-code language. Config custom rules created with Lambda are called Config Custom Lambda Rules and Config custom rules created with Guard are called Config Custom Policy Rules.

  For more information about developing and using Config rules, see Evaluating Resource with Config Rules in the Config Developer Guide.

  You can use the Amazon Web Services CLI and Amazon Web Services SDKs if you want to create a rule that triggers evaluations for your resources when Config delivers the configuration snapshot. For more information, see ConfigSnapshotDeliveryProperties.

• ConfigRuleComplianceFilters

  Filters the compliance results based on account ID, region, compliance type, and rule name.

• ConfigRuleComplianceSummaryFilters

  Filters the results based on the account IDs and regions.

• ConfigRuleEvaluationStatus

  Status information for your Config Managed rules and Config Custom Policy rules. The status includes information such as the last time the rule ran, the last time it failed, and the related error for the last failure.

  This operation does not return status information about Config Custom Lambda rules.

• ConfigSnapshotDeliveryProperties

  Provides options for how often Config delivers configuration snapshots to the Amazon S3 bucket in your delivery channel.

  The frequency for a rule that triggers evaluations for your resources when Config delivers the configuration snapshot is set by one of two values, depending on which is less frequent:

  • The value for the deliveryFrequency parameter within the delivery channel configuration, which sets how often Config delivers configuration snapshots. This value also sets how often Config invokes evaluations for Config rules.

  • The value for the MaximumExecutionFrequency parameter, which sets the maximum frequency with which Config invokes evaluations for the rule. For more information, see ConfigRule.

  If the deliveryFrequency value is less frequent than the MaximumExecutionFrequency value for a rule, Config invokes the rule only as often as the deliveryFrequency value.

  1. For example, you want your rule to run evaluations when Config delivers the configuration snapshot.

  2. You specify the MaximumExecutionFrequency value for Six_Hours.

  3. You then specify the delivery channel deliveryFrequency value for TwentyFour_Hours.

  4. Because the value for deliveryFrequency is less frequent than MaximumExecutionFrequency, Config invokes evaluations for the rule every 24 hours.

  You should set the MaximumExecutionFrequency value to be at least as frequent as the deliveryFrequency value. You can view the deliveryFrequency value by using the DescribeDeliveryChannnels action.

  To update the deliveryFrequency with which Config delivers your configuration snapshots, use the PutDeliveryChannel action.

• ConfigStreamDeliveryInfo

  A list that contains the status of the delivery of the configuration stream notification to the Amazon SNS topic.

• ConfigurationAggregator

  The details about the configuration aggregator, including information about source accounts, regions, and metadata of the aggregator.

• ConfigurationItem

  A list that contains detailed configurations of a specified resource.

• ConfigurationRecorder

  Records configuration changes to the resource types in scope.

  For more information about the configuration recorder, see Working with the Configuration Recorder in the Config Developer Guide.

• ConfigurationRecorderFilter

  Filters configuration recorders by recording scope.

• ConfigurationRecorderStatus

  The current status of the configuration recorder.

  For a detailed status of recording events over time, add your Config events to CloudWatch metrics and use CloudWatch metrics.

• ConfigurationRecorderSummary

  A summary of a configuration recorder, including the arn, name, servicePrincipal, and recordingScope.

• ConformancePackComplianceFilters

  Filters the conformance pack by compliance types and Config rule names.

• ConformancePackComplianceScore

  A compliance score is the percentage of the number of compliant rule-resource combinations in a conformance pack compared to the number of total possible rule-resource combinations in the conformance pack. This metric provides you with a high-level view of the compliance state of your conformance packs. You can use it to identify, investigate, and understand the level of compliance in your conformance packs.

• ConformancePackComplianceScoresFilters

  A list of filters to apply to the conformance pack compliance score result set.

• ConformancePackComplianceSummary

  Summary includes the name and status of the conformance pack.

• ConformancePackDetail

  Returns details of a conformance pack. A conformance pack is a collection of Config rules and remediation actions that can be easily deployed in an account and a region.

• ConformancePackEvaluationFilters

  Filters a conformance pack by Config rule names, compliance types, Amazon Web Services resource types, and resource IDs.

• ConformancePackEvaluationResult

  The details of a conformance pack evaluation. Provides Config rule and Amazon Web Services resource type that was evaluated, the compliance of the conformance pack, related time stamps, and supplementary information.

• ConformancePackInputParameter

  Input parameters in the form of key-value pairs for the conformance pack, both of which you define. Keys can have a maximum character length of 255 characters, and values can have a maximum length of 4096 characters.

• ConformancePackRuleCompliance

  Compliance information of one or more Config rules within a conformance pack. You can filter using Config rule names and compliance types.

• ConformancePackStatusDetail

  Status details of a conformance pack.

• CustomPolicyDetails

  Provides the runtime system, policy definition, and whether debug logging enabled. You can specify the following CustomPolicyDetails parameter values only for Config Custom Policy rules.

• DeliveryChannel

  The channel through which Config delivers notifications and updated configuration states.

• DeliveryChannelStatus

  The status of a specified delivery channel.

  Valid values: Success | Failure

• DescribeConfigRulesFilters

  Returns a filtered list of Detective or Proactive Config rules. By default, if the filter is not defined, this API returns an unfiltered list. For more information on Detective or Proactive Config rules, see Evaluation Mode in the Config Developer Guide.

• Evaluation

  Identifies an Amazon Web Services resource and indicates whether it complies with the Config rule that it was evaluated against.

• EvaluationContext

  Use EvaluationContext to group independently initiated proactive resource evaluations. For example, CFN Stack. If you want to check just a resource definition, you do not need to provide evaluation context.

• EvaluationModeConfiguration

  The configuration object for Config rule evaluation mode. The supported valid values are Detective or Proactive.

• EvaluationResult

  The details of an Config evaluation. Provides the Amazon Web Services resource that was evaluated, the compliance of the resource, related time stamps, and supplementary information.

• EvaluationResultIdentifier

  Uniquely identifies an evaluation result.

• EvaluationResultQualifier

  Identifies an Config rule that evaluated an Amazon Web Services resource, and provides the type and ID of the resource that the rule evaluated.

• EvaluationStatus

  Returns status details of an evaluation.

• ExclusionByResourceTypes

  Specifies whether the configuration recorder excludes certain resource types from being recorded. Use the resourceTypes field to enter a comma-separated list of resource types you want to exclude from recording.

  By default, when Config adds support for a new resource type in the Region where you set up the configuration recorder, including global resource types, Config starts recording resources of that type automatically.

  How to use the exclusion recording strategy

  To use this option, you must set the useOnly field of RecordingStrategy to EXCLUSION_BY_RESOURCE_TYPES.

  Config will then record configuration changes for all supported resource types, except the resource types that you specify to exclude from being recorded.

  Global resource types and the exclusion recording strategy

  Unless specifically listed as exclusions, AWS::RDS::GlobalCluster will be recorded automatically in all supported Config Regions were the configuration recorder is enabled.

  IAM users, groups, roles, and customer managed policies will be recorded in the Region where you set up the configuration recorder if that is a Region where Config was available before February 2022. You cannot be record the global IAM resouce types in Regions supported by Config after February 2022. For a list of those Regions, see Recording Amazon Web Services Resources | Global Resources.

• ExecutionControls

  The controls that Config uses for executing remediations.

• ExternalEvaluation

  Identifies an Amazon Web Services resource and indicates whether it complies with the Config rule that it was evaluated against.

• FailedDeleteRemediationExceptionsBatch

  List of each of the failed delete remediation exceptions with specific reasons.

• FailedRemediationBatch

  List of each of the failed remediations with specific reasons.

• FailedRemediationExceptionBatch

  List of each of the failed remediation exceptions with specific reasons.

• FieldInfo

  Details about the fields such as name of the field.

• GroupedResourceCount

  The count of resources that are grouped by the group name.

• MemberAccountStatus

  Organization Config rule creation or deletion status in each member account. This includes the name of the rule, the status, error code and error message when the rule creation or deletion failed.

• OrganizationAggregationSource

  This object contains regions to set up the aggregator and an IAM role to retrieve organization details.

• OrganizationConfigRule

  An organization Config rule that has information about Config rules that Config creates in member accounts.

• OrganizationConfigRuleStatus

  Returns the status for an organization Config rule in an organization.

• OrganizationConformancePack

  An organization conformance pack that has information about conformance packs that Config creates in member accounts.

• OrganizationConformancePackDetailedStatus

  Organization conformance pack creation or deletion status in each member account. This includes the name of the conformance pack, the status, error code and error message when the conformance pack creation or deletion failed.

• OrganizationConformancePackStatus

  Returns the status for an organization conformance pack in an organization.

• OrganizationCustomPolicyRuleMetadata

  An object that specifies metadata for your organization's Config Custom Policy rule. The metadata includes the runtime system in use, which accounts have debug logging enabled, and other custom rule metadata, such as resource type, resource ID of Amazon Web Services resource, and organization trigger types that initiate Config to evaluate Amazon Web Services resources against a rule.

• OrganizationCustomPolicyRuleMetadataNoPolicy

  metadata for your organization Config Custom Policy rule including the runtime system in use, which accounts have debug logging enabled, and other custom rule metadata such as resource type, resource ID of Amazon Web Services resource, and organization trigger types that trigger Config to evaluate Amazon Web Services resources against a rule.

• OrganizationCustomRuleMetadata

  An object that specifies organization custom rule metadata such as resource type, resource ID of Amazon Web Services resource, Lambda function ARN, and organization trigger types that trigger Config to evaluate your Amazon Web Services resources against a rule. It also provides the frequency with which you want Config to run evaluations for the rule if the trigger type is periodic.

• OrganizationManagedRuleMetadata

  An object that specifies organization managed rule metadata such as resource type and ID of Amazon Web Services resource along with the rule identifier. It also provides the frequency with which you want Config to run evaluations for the rule if the trigger type is periodic.

• OrganizationResourceDetailedStatusFilters

  Status filter object to filter results based on specific member account ID or status type for an organization conformance pack.

• PendingAggregationRequest

  An object that represents the account ID and region of an aggregator account that is requesting authorization but is not yet authorized.

• QueryInfo

  Details about the query.

• RecordingGroup

  Specifies which resource types Config records for configuration changes. By default, Config records configuration changes for all current and future supported resource types in the Amazon Web Services Region where you have enabled Config, excluding the global IAM resource types: IAM users, groups, roles, and customer managed policies.

  In the recording group, you specify whether you want to record all supported current and future supported resource types or to include or exclude specific resources types. For a list of supported resource types, see Supported Resource Types in the Config developer guide.

  If you don't want Config to record all current and future supported resource types (excluding the global IAM resource types), use one of the following recording strategies:

  1. Record all current and future resource types with exclusions (EXCLUSION_BY_RESOURCE_TYPES), or

  2. Record specific resource types (INCLUSION_BY_RESOURCE_TYPES).

  If you use the recording strategy to Record all current and future resource types (ALL_SUPPORTED_RESOURCE_TYPES), you can use the flag includeGlobalResourceTypes to include the global IAM resource types in your recording.

  Aurora global clusters are recorded in all enabled Regions

  The AWS::RDS::GlobalCluster resource type will be recorded in all supported Config Regions where the configuration recorder is enabled.

  If you do not want to record AWS::RDS::GlobalCluster in all enabled Regions, use the EXCLUSION_BY_RESOURCE_TYPES or INCLUSION_BY_RESOURCE_TYPES recording strategy.

• RecordingMode

  Specifies the default recording frequency that Config uses to record configuration changes. Config supports Continuous recording and Daily recording.

  • Continuous recording allows you to record configuration changes continuously whenever a change occurs.

  • Daily recording allows you to receive a configuration item (CI) representing the most recent state of your resources over the last 24-hour period, only if it’s different from the previous CI recorded.

  Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.

  You can also override the recording frequency for specific resource types.

• RecordingModeOverride

  An object for you to specify your overrides for the recording mode.

• RecordingStrategy

  Specifies the recording strategy of the configuration recorder.

• Relationship

  The relationship of the related resource to the main resource.

• RemediationConfiguration

  An object that represents the details about the remediation configuration that includes the remediation action, parameters, and data to execute the action.

• RemediationException

  An object that represents the details about the remediation exception. The details include the rule name, an explanation of an exception, the time when the exception will be deleted, the resource ID, and resource type.

• RemediationExceptionResourceKey

  The details that identify a resource within Config, including the resource type and resource ID.

• RemediationExecutionStatus

  Provides details of the current status of the invoked remediation action for that resource.

• RemediationExecutionStep

  Name of the step from the SSM document.

• RemediationParameterValue

  The value is either a dynamic (resource) value or a static value. You must select either a dynamic value or a static value.

• ResourceCount

  An object that contains the resource type and the number of resources.

• ResourceCountFilters

  Filters the resource count based on account ID, region, and resource type.

• ResourceDetails

  Returns information about the resource being evaluated.

• ResourceEvaluation

  Returns details of a resource evaluation.

• ResourceEvaluationFilters

  Returns details of a resource evaluation based on the selected filter.

• ResourceFilters

  Filters the results by resource account ID, region, resource ID, and resource name.

• ResourceIdentifier

  The details that identify a resource that is discovered by Config, including the resource type, ID, and (if available) the custom resource name.

• ResourceKey

  The details that identify a resource within Config, including the resource type and resource ID.

• ResourceValue

  The dynamic value of the resource.

• RetentionConfiguration

  An object with the name of the retention configuration and the retention period in days. The object stores the configuration for data retention in Config.

• Scope

  Defines which resources trigger an evaluation for an Config rule. The 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. Specify a scope to constrain which resources trigger an evaluation for a rule. Otherwise, evaluations for the rule are triggered when any resource in your recording group changes in configuration.

• Source

  Provides the CustomPolicyDetails, the rule owner (Amazon Web Services for managed rules, CUSTOM_POLICY for Custom Policy rules, and CUSTOM_LAMBDA for Custom Lambda rules), the rule identifier, and the events that cause the evaluation of your Amazon Web Services resources.

• SourceDetail

  Provides the source and the message types that trigger Config to evaluate your Amazon Web Services resources against a rule. It also provides the frequency with which you want Config to run evaluations for the rule if the trigger type is periodic. You can specify the parameter values for SourceDetail only for custom rules.

• SsmControls

  Amazon Web Services Systems Manager (SSM) specific remediation controls.

• StaticValue

  The static value of the resource.

• StatusDetailFilters

  Status filter object to filter results based on specific member account ID or status type for an organization Config rule.

• StoredQuery

  Provides the details of a stored query.

• StoredQueryMetadata

  Returns details of a specific query.

• Tag

  The tags for the resource. The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.

• TemplateSsmDocumentDetails

  This API allows you to create a conformance pack template with an Amazon Web Services Systems Manager document (SSM document). To deploy a conformance pack using an SSM document, first create an SSM document with conformance pack content, and then provide the DocumentName in the PutConformancePack API. You can also provide the DocumentVersion.

  The TemplateSSMDocumentDetails object contains the name of the SSM document and the version of the SSM document.

• TimeWindow

  Filters evaluation results based on start and end times.

Enums

• AggregateConformancePackComplianceSummaryGroupKey
  When writing a match expression against AggregateConformancePackComplianceSummaryGroupKey, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AggregatedSourceStatusType
  When writing a match expression against AggregatedSourceStatusType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AggregatedSourceType
  When writing a match expression against AggregatedSourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AggregatorFilterType
  When writing a match expression against AggregatorFilterType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ChronologicalOrder
  When writing a match expression against ChronologicalOrder, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ComplianceType
  When writing a match expression against ComplianceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigRuleComplianceSummaryGroupKey
  When writing a match expression against ConfigRuleComplianceSummaryGroupKey, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigRuleState
  When writing a match expression against ConfigRuleState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigurationItemStatus
  When writing a match expression against ConfigurationItemStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigurationRecorderFilterName
  When writing a match expression against ConfigurationRecorderFilterName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConformancePackComplianceType
  When writing a match expression against ConformancePackComplianceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConformancePackState
  When writing a match expression against ConformancePackState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DeliveryStatus
  When writing a match expression against DeliveryStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EvaluationMode
  When writing a match expression against EvaluationMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventSource
  When writing a match expression against EventSource, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• MaximumExecutionFrequency
  When writing a match expression against MaximumExecutionFrequency, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• MemberAccountRuleStatus
  When writing a match expression against MemberAccountRuleStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• MessageType
  When writing a match expression against MessageType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrganizationConfigRuleTriggerType
  When writing a match expression against OrganizationConfigRuleTriggerType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrganizationConfigRuleTriggerTypeNoSn
  When writing a match expression against OrganizationConfigRuleTriggerTypeNoSn, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrganizationResourceDetailedStatus
  When writing a match expression against OrganizationResourceDetailedStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrganizationResourceStatus
  When writing a match expression against OrganizationResourceStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OrganizationRuleStatus
  When writing a match expression against OrganizationRuleStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Owner
  When writing a match expression against Owner, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RecorderStatus
  When writing a match expression against RecorderStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RecordingFrequency
  When writing a match expression against RecordingFrequency, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RecordingScope
  When writing a match expression against RecordingScope, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RecordingStrategyType
  When writing a match expression against RecordingStrategyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RemediationExecutionState
  When writing a match expression against RemediationExecutionState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RemediationExecutionStepState
  When writing a match expression against RemediationExecutionStepState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RemediationTargetType
  When writing a match expression against RemediationTargetType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceConfigurationSchemaType
  When writing a match expression against ResourceConfigurationSchemaType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceCountGroupKey
  When writing a match expression against ResourceCountGroupKey, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceEvaluationStatus
  When writing a match expression against ResourceEvaluationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceType
  When writing a match expression against ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceValueType
  When writing a match expression against ResourceValueType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortBy
  When writing a match expression against SortBy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SortOrder
  When writing a match expression against SortOrder, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.