@propulsionworks/cloudformation 0.0.1 → 0.1.0

package/out/exports/resources.generated/aws-config-configrule.d.ts

@@ -0,0 +1,177 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type ConfigConfigRule = ResourceDefinitionWithAttributes<"AWS::Config::ConfigRule", ConfigConfigRuleProps, ConfigConfigRuleAttribs>;
+/**
+ * > You must first create and start the AWS Config configuration recorder in order to create AWS Config managed rules with AWS CloudFormation . For more information, see [Managing the Configuration Recorder](https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html) .
+ *
+ * Adds or updates an AWS Config rule to evaluate if your AWS resources comply with your desired configurations. For information on how many AWS Config rules you can have per account, see [*Service Limits*](https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html) in the *AWS Config Developer Guide* .
+ *
+ * There are two types of rules: *AWS Config Managed Rules* and *AWS Config Custom Rules* . You can use the `ConfigRule` resource to create both AWS Config Managed Rules and AWS Config Custom Rules.
+ *
+ * AWS Config Managed Rules are predefined, customizable rules created by AWS Config . For a list of managed rules, see [List of AWS Config Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html) . If you are adding an AWS Config managed rule, you must specify the rule's identifier for the `SourceIdentifier` key.
+ *
+ * AWS Config Custom Rules are rules that you create from scratch. There are two ways to create AWS Config custom rules: with Lambda functions ( [AWS Lambda Developer Guide](https://docs.aws.amazon.com/config/latest/developerguide/gettingstarted-concepts.html#gettingstarted-concepts-function) ) and with Guard ( [Guard GitHub Repository](https://docs.aws.amazon.com/https://github.com/aws-cloudformation/cloudformation-guard) ), a policy-as-code language. AWS Config custom rules created with AWS Lambda are called *AWS Config Custom Lambda Rules* and AWS Config custom rules created with Guard are called *AWS Config Custom Policy Rules* .
+ *
+ * If you are adding a new AWS Config Custom Lambda rule, you first need to create an AWS Lambda function that the rule invokes to evaluate your resources. When you use the `ConfigRule` resource to add a Custom Lambda rule to AWS Config , you must specify the Amazon Resource Name (ARN) that AWS Lambda assigns to the function. You specify the ARN in the `SourceIdentifier` key. This key is part of the `Source` object, which is part of the `ConfigRule` object.
+ *
+ * For any new AWS Config rule that you add, specify the `ConfigRuleName` in the `ConfigRule` object. Do not specify the `ConfigRuleArn` or the `ConfigRuleId` . These values are generated by AWS Config for new rules.
+ *
+ * If you are updating a rule that you added previously, you can specify the rule by `ConfigRuleName` , `ConfigRuleId` , or `ConfigRuleArn` in the `ConfigRule` data type that you use in this request.
+ *
+ * For more information about developing and using AWS Config rules, see [Evaluating Resources with AWS Config Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *AWS Config Developer Guide* .
+ */
+export type ConfigConfigRuleProps = {
+    /**
+     * A name for the AWS Config rule. If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the rule name. For more information, see [Name Type](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-name.html) .
+     */
+    ConfigRuleName?: string | undefined;
+    /**
+     * The description that you provide for the AWS Config rule.
+     */
+    Description?: string | undefined;
+    /**
+     * The modes the AWS Config rule can be evaluated in. The valid values are distinct objects. By default, the value is Detective evaluation mode only.
+     */
+    EvaluationModes?: EvaluationModeConfiguration[] | undefined;
+    /**
+     * A string, in JSON format, that is passed to the AWS Config rule Lambda function.
+     */
+    InputParameters?: string | Record<string, unknown> | undefined;
+    /**
+     * The maximum frequency with which AWS Config runs evaluations for a rule. You can specify a value for `MaximumExecutionFrequency` when:
+     *
+     * - You are using an AWS managed rule that is triggered at a periodic frequency.
+     * - Your custom rule is triggered when AWS Config delivers the configuration snapshot. For more information, see [ConfigSnapshotDeliveryProperties](https://docs.aws.amazon.com/config/latest/APIReference/API_ConfigSnapshotDeliveryProperties.html) .
+     *
+     * > By default, rules with a periodic trigger are evaluated every 24 hours. To change the frequency, specify a valid value for the `MaximumExecutionFrequency` parameter.
+     */
+    MaximumExecutionFrequency?: string | undefined;
+    /**
+     * Defines which resources can trigger an evaluation for the rule. The scope can include one or more resource types, a combination of one resource type and one resource ID, or a combination of a tag key and value. Specify a scope to constrain the resources that can trigger an evaluation for the rule. If you do not specify a scope, evaluations are triggered when any resource in the recording group changes.
+     */
+    Scope?: Scope | undefined;
+    /**
+     * Provides the rule owner ( `AWS` for managed rules, `CUSTOM_POLICY` for Custom Policy rules, and `CUSTOM_LAMBDA` for Custom Lambda rules), the rule identifier, and the notifications that cause the function to evaluate your AWS resources.
+     */
+    Source: Source;
+};
+export type ConfigConfigRuleAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the AWS Config rule, such as `arn:aws:config:us-east-1:123456789012:config-rule/config-rule-a1bzhi` .
+     */
+    Arn: string;
+    /**
+     * Compliance type determined by the Config rule
+     */
+    "Compliance.Type": string;
+    /**
+     * The ID of the AWS Config rule, such as `config-rule-a1bzhi` .
+     */
+    ConfigRuleId: string;
+};
+/**
+ * Provides the CustomPolicyDetails, the rule owner ( `AWS` 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 AWS resources.
+ */
+export type CustomPolicyDetails = {
+    /**
+     * The boolean expression for enabling debug logging for your AWS Config Custom Policy rule. The default value is `false` .
+     */
+    EnableDebugLogDelivery?: boolean | undefined;
+    /**
+     * The runtime system for your AWS Config Custom Policy rule. Guard is a policy-as-code language that allows you to write policies that are enforced by AWS Config Custom Policy rules. For more information about Guard, see the [Guard GitHub Repository](https://docs.aws.amazon.com/https://github.com/aws-cloudformation/cloudformation-guard) .
+     */
+    PolicyRuntime?: string | undefined;
+    /**
+     * The policy definition containing the logic for your AWS Config Custom Policy rule.
+     */
+    PolicyText?: string | undefined;
+};
+/**
+ * The configuration object for AWS Config rule evaluation mode. The supported valid values are Detective or Proactive.
+ */
+export type EvaluationModeConfiguration = {
+    /**
+     * The mode of an evaluation. The valid values are Detective or Proactive.
+     */
+    Mode?: string | undefined;
+};
+/**
+ * Defines which resources trigger an evaluation for an AWS 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.
+ */
+export type Scope = {
+    /**
+     * The ID of the only AWS resource that you want to trigger an evaluation for the rule. If you specify a resource ID, you must specify one resource type for `ComplianceResourceTypes` .
+     */
+    ComplianceResourceId?: string | undefined;
+    /**
+     * The resource types of only those AWS resources that you want to trigger an evaluation for the rule. You can only specify one type if you also specify a resource ID for `ComplianceResourceId` .
+     */
+    ComplianceResourceTypes?: string[] | undefined;
+    /**
+     * The tag key that is applied to only those AWS resources that you want to trigger an evaluation for the rule.
+     */
+    TagKey?: string | undefined;
+    /**
+     * The tag value applied to only those AWS resources that you want to trigger an evaluation for the rule. If you specify a value for `TagValue` , you must also specify a value for `TagKey` .
+     */
+    TagValue?: string | undefined;
+};
+/**
+ * Provides the CustomPolicyDetails, the rule owner ( `AWS` 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 AWS resources.
+ */
+export type Source = {
+    /**
+     * Provides the runtime system, policy definition, and whether debug logging is enabled. Required when owner is set to `CUSTOM_POLICY` .
+     */
+    CustomPolicyDetails?: CustomPolicyDetails | undefined;
+    /**
+     * Indicates whether AWS or the customer owns and manages the AWS Config rule.
+     *
+     * AWS Config Managed Rules are predefined rules owned by AWS . For more information, see [AWS Config Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html) in the *AWS Config developer guide* .
+     *
+     * AWS Config Custom Rules are rules that you can develop either with Guard ( `CUSTOM_POLICY` ) or AWS Lambda ( `CUSTOM_LAMBDA` ). For more information, see [AWS Config Custom Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_develop-rules.html) in the *AWS Config developer guide* .
+     */
+    Owner: string;
+    /**
+     * Provides the source and the message types that cause AWS Config to evaluate your AWS resources against a rule. It also provides the frequency with which you want AWS Config to run evaluations for the rule if the trigger type is periodic.
+     *
+     * If the owner is set to `CUSTOM_POLICY` , the only acceptable values for the AWS Config rule trigger message type are `ConfigurationItemChangeNotification` and `OversizedConfigurationItemChangeNotification` .
+     */
+    SourceDetails?: SourceDetail[] | undefined;
+    /**
+     * For AWS Config Managed rules, a predefined identifier from a list. For example, `IAM_PASSWORD_POLICY` is a managed rule. To reference a managed rule, see [List of AWS Config Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html) .
+     *
+     * For AWS Config Custom Lambda rules, the identifier is the Amazon Resource Name (ARN) of the rule's AWS Lambda function, such as `arn:aws:lambda:us-east-2:123456789012:function:custom_rule_name` .
+     *
+     * For AWS Config Custom Policy rules, this field will be ignored.
+     */
+    SourceIdentifier?: string | undefined;
+};
+/**
+ * Provides the source and the message types that trigger AWS Config to evaluate your AWS resources against a rule. It also provides the frequency with which you want AWS 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.
+ */
+export type SourceDetail = {
+    /**
+     * The source of the event, such as an AWS service, that triggers AWS Config to evaluate your AWS resources.
+     */
+    EventSource: string;
+    /**
+     * The frequency at which you want AWS Config to run evaluations for a custom rule with a periodic trigger. If you specify a value for `MaximumExecutionFrequency` , then `MessageType` must use the `ScheduledNotification` value.
+     *
+     * > By default, rules with a periodic trigger are evaluated every 24 hours. To change the frequency, specify a valid value for the `MaximumExecutionFrequency` parameter.
+     * >
+     * > Based on the valid value you choose, AWS Config runs evaluations once for each valid value. For example, if you choose `Three_Hours` , AWS Config runs evaluations once every three hours. In this case, `Three_Hours` is the frequency of this rule.
+     */
+    MaximumExecutionFrequency?: string | undefined;
+    /**
+     * The type of notification that triggers AWS Config to run an evaluation for a rule. You can specify the following notification types:
+     *
+     * - `ConfigurationItemChangeNotification` - Triggers an evaluation when AWS Config delivers a configuration item as a result of a resource change.
+     * - `OversizedConfigurationItemChangeNotification` - Triggers an evaluation when AWS Config delivers an oversized configuration item. AWS Config may generate this notification type when a resource changes and the notification exceeds the maximum size allowed by Amazon SNS.
+     * - `ScheduledNotification` - Triggers a periodic evaluation at the frequency specified for `MaximumExecutionFrequency` .
+     * - `ConfigurationSnapshotDeliveryCompleted` - Triggers a periodic evaluation when AWS Config delivers a configuration snapshot.
+     *
+     * If you want your custom rule to be triggered by configuration changes, specify two SourceDetail objects, one for `ConfigurationItemChangeNotification` and one for `OversizedConfigurationItemChangeNotification` .
+     */
+    MessageType: string;
+};
+//# sourceMappingURL=aws-config-configrule.d.ts.map

package/out/exports/resources.generated/aws-config-configurationaggregator.d.ts

@@ -0,0 +1,67 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ConfigConfigurationAggregator = ResourceDefinitionWithAttributes<"AWS::Config::ConfigurationAggregator", ConfigConfigurationAggregatorProps, ConfigConfigurationAggregatorAttribs>;
+/**
+ * The details about the configuration aggregator, including information about source accounts, regions, and metadata of the aggregator.
+ */
+export type ConfigConfigurationAggregatorProps = {
+    /**
+     * Provides a list of source accounts and regions to be aggregated.
+     */
+    AccountAggregationSources?: AccountAggregationSource[] | undefined;
+    /**
+     * The name of the aggregator.
+     * @minLength 1
+     * @maxLength 256
+     * @pattern [\w\-]+
+     */
+    ConfigurationAggregatorName?: string | undefined;
+    /**
+     * Provides an organization and list of regions to be aggregated.
+     */
+    OrganizationAggregationSource?: OrganizationAggregationSource | undefined;
+    /**
+     * An array of tag object.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type ConfigConfigurationAggregatorAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the aggregator.
+     */
+    ConfigurationAggregatorArn: string;
+};
+/**
+ * A collection of accounts and regions.
+ */
+export type AccountAggregationSource = {
+    /**
+     * The 12-digit account ID of the account being aggregated.
+     */
+    AccountIds: string[];
+    /**
+     * If true, aggregate existing AWS Config regions and future regions.
+     */
+    AllAwsRegions?: boolean | undefined;
+    /**
+     * The source regions being aggregated.
+     */
+    AwsRegions?: string[] | undefined;
+};
+/**
+ * This object contains regions to set up the aggregator and an IAM role to retrieve organization details.
+ */
+export type OrganizationAggregationSource = {
+    /**
+     * If true, aggregate existing AWS Config regions and future regions.
+     */
+    AllAwsRegions?: boolean | undefined;
+    /**
+     * The source regions being aggregated.
+     */
+    AwsRegions?: string[] | undefined;
+    /**
+     * ARN of the IAM role used to retrieve AWS Organizations details associated with the aggregator account.
+     */
+    RoleArn: string;
+};
+//# sourceMappingURL=aws-config-configurationaggregator.d.ts.map

package/out/exports/resources.generated/aws-config-configurationrecorder.d.ts

@@ -0,0 +1,311 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type ConfigConfigurationRecorder = ResourceDefinitionWithAttributes<"AWS::Config::ConfigurationRecorder", ConfigConfigurationRecorderProps, ConfigConfigurationRecorderAttribs>;
+/**
+ * The `AWS::Config::ConfigurationRecorder` resource type describes the AWS resource types that AWS Config records for configuration changes.
+ *
+ * The configuration recorder stores the configuration changes of the specified resources in your account as configuration items.
+ *
+ * > To enable AWS Config , you must create a configuration recorder and a delivery channel.
+ * >
+ * > AWS Config uses the delivery channel to deliver the configuration changes to your Amazon S3 bucket or Amazon SNS topic. For more information, see [AWS::Config::DeliveryChannel](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-deliverychannel.html) .
+ *
+ * AWS CloudFormation starts the recorder as soon as the delivery channel is available.
+ *
+ * To stop the recorder and delete it, delete the configuration recorder from your stack. To stop the recorder without deleting it, call the [StopConfigurationRecorder](https://docs.aws.amazon.com/config/latest/APIReference/API_StopConfigurationRecorder.html) action of the AWS Config API directly.
+ *
+ * For more information, see [Configuration Recorder](https://docs.aws.amazon.com/config/latest/developerguide/config-concepts.html#config-recorder) in the AWS Config Developer Guide.
+ */
+export type ConfigConfigurationRecorderProps = {
+    /**
+     * The name of the configuration recorder. AWS Config automatically assigns the name of "default" when creating the configuration recorder.
+     *
+     * You cannot change the name of the configuration recorder after it has been created. To change the configuration recorder name, you must delete it and create a new configuration recorder with a new name.
+     */
+    Name?: string | undefined;
+    /**
+     * Specifies which resource types AWS Config records for configuration changes.
+     *
+     * > *High Number of AWS Config Evaluations*
+     * >
+     * > You may notice increased activity in your account during your initial month recording with AWS Config when compared to subsequent months. During the initial bootstrapping process, AWS Config runs evaluations on all the resources in your account that you have selected for AWS Config to record.
+     * >
+     * > If you are running ephemeral workloads, you may see increased activity from AWS Config as it records configuration changes associated with creating and deleting these temporary resources. An *ephemeral workload* is a temporary use of computing resources that are loaded and run when needed. Examples include Amazon Elastic Compute Cloud ( Amazon EC2 ) Spot Instances, Amazon EMR jobs, and AWS Auto Scaling . If you want to avoid the increased activity from running ephemeral workloads, you can run these types of workloads in a separate account with AWS Config turned off to avoid increased configuration recording and rule evaluations.
+     */
+    RecordingGroup?: RecordingGroup | undefined;
+    /**
+     * Specifies the default recording frequency for the configuration recorder. AWS 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.
+     *
+     * > *Some resource types require continuous recording*
+     * >
+     * > AWS 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.
+     */
+    RecordingMode?: RecordingMode | undefined;
+    /**
+     * Amazon Resource Name (ARN) of the IAM role assumed by AWS Config and used by the configuration recorder. For more information, see [Permissions for the IAM Role Assigned](https://docs.aws.amazon.com/config/latest/developerguide/iamrole-permissions.html) to AWS Config in the AWS Config Developer Guide.
+     *
+     * > *Pre-existing AWS Config role*
+     * >
+     * > If you have used an AWS service that uses AWS Config , such as AWS Security Hub or AWS Control Tower , and an AWS Config role has already been created, make sure that the IAM role that you use when setting up AWS Config keeps the same minimum permissions as the already created AWS Config role. You must do this so that the other AWS service continues to run as expected.
+     * >
+     * > For example, if AWS Control Tower has an IAM role that allows AWS Config to read Amazon Simple Storage Service ( Amazon S3 ) objects, make sure that the same permissions are granted within the IAM role you use when setting up AWS Config . Otherwise, it may interfere with how AWS Control Tower operates. For more information about IAM roles for AWS Config , see [*Identity and Access Management for AWS Config*](https://docs.aws.amazon.com/config/latest/developerguide/security-iam.html) in the *AWS Config Developer Guide* .
+     */
+    RoleARN: string;
+};
+export type ConfigConfigurationRecorderAttribs = {
+    Id: string;
+};
+/**
+ * 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 AWS Config adds support for a new resource type in the Region where you set up the configuration recorder, including global resource types, AWS 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](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `EXCLUSION_BY_RESOURCE_TYPES` .
+ * >
+ * > AWS 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 AWS 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 AWS Config was available before February 2022. You cannot be record the global IAM resouce types in Regions supported by AWS Config after February 2022. This list where you cannot record the global IAM resource types includes the following Regions:
+ * >
+ * > - Asia Pacific (Hyderabad)
+ * > - Asia Pacific (Melbourne)
+ * > - Canada West (Calgary)
+ * > - Europe (Spain)
+ * > - Europe (Zurich)
+ * > - Israel (Tel Aviv)
+ * > - Middle East (UAE)
+ */
+export type ExclusionByResourceTypes = {
+    /**
+     * A comma-separated list of resource types to exclude from recording by the configuration recorder.
+     */
+    ResourceTypes: string[];
+};
+/**
+ * Specifies which resource types AWS Config records for configuration changes. By default, AWS Config records configuration changes for all current and future supported resource types in the AWS Region where you have enabled AWS 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](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html#supported-resources) in the *AWS Config developer guide* .
+ *
+ * If you don't want AWS Config to record all current and future supported resource types (excluding the global IAM resource types), use one of the following recording strategies:
+ *
+ * - *Record all current and future resource types with exclusions* ( `EXCLUSION_BY_RESOURCE_TYPES` ), or
+ * - *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 AWS 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.
+ */
+export type RecordingGroup = {
+    /**
+     * Specifies whether AWS Config records configuration changes for all supported resource types, excluding the global IAM resource types.
+     *
+     * If you set this field to `true` , when AWS Config adds support for a new resource type, AWS Config starts recording resources of that type automatically.
+     *
+     * If you set this field to `true` , you cannot enumerate specific resource types to record in the `resourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) , or to exclude in the `resourceTypes` field of [ExclusionByResourceTypes](https://docs.aws.amazon.com/config/latest/APIReference/API_ExclusionByResourceTypes.html) .
+     *
+     * > *Region availability*
+     * >
+     * > Check [Resource Coverage by Region Availability](https://docs.aws.amazon.com/config/latest/developerguide/what-is-resource-config-coverage.html) to see if a resource type is supported in the AWS Region where you set up AWS Config .
+     */
+    AllSupported?: boolean | undefined;
+    /**
+     * An object that specifies how AWS Config excludes resource types from being recorded by the configuration recorder.
+     *
+     * To use this option, you must set the `useOnly` field of [AWS::Config::ConfigurationRecorder RecordingStrategy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-config-configurationrecorder-recordingstrategy.html) to `EXCLUSION_BY_RESOURCE_TYPES` .
+     */
+    ExclusionByResourceTypes?: ExclusionByResourceTypes | undefined;
+    /**
+     * This option is a bundle which only applies to the global IAM resource types: IAM users, groups, roles, and customer managed policies. These global IAM resource types can only be recorded by AWS Config in Regions where AWS Config was available before February 2022. You cannot be record the global IAM resouce types in Regions supported by AWS Config after February 2022. This list where you cannot record the global IAM resource types includes the following Regions:
+     *
+     * - Asia Pacific (Hyderabad)
+     * - Asia Pacific (Melbourne)
+     * - Canada West (Calgary)
+     * - Europe (Spain)
+     * - Europe (Zurich)
+     * - Israel (Tel Aviv)
+     * - Middle East (UAE)
+     *
+     * > *Aurora global clusters are recorded in all enabled Regions*
+     * >
+     * > The `AWS::RDS::GlobalCluster` resource type will be recorded in all supported AWS Config Regions where the configuration recorder is enabled, even if `IncludeGlobalResourceTypes` is set to `false` . The `IncludeGlobalResourceTypes` option is a bundle which only applies to IAM users, groups, roles, and customer managed policies.
+     * >
+     * > If you do not want to record `AWS::RDS::GlobalCluster` in all enabled Regions, use one of the following recording strategies:
+     * >
+     * > - *Record all current and future resource types with exclusions* ( `EXCLUSION_BY_RESOURCE_TYPES` ), or
+     * > - *Record specific resource types* ( `INCLUSION_BY_RESOURCE_TYPES` ).
+     * >
+     * > For more information, see [Selecting Which Resources are Recorded](https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html#select-resources-all) in the *AWS Config developer guide* . > *IncludeGlobalResourceTypes and the exclusion recording strategy*
+     * >
+     * > The `IncludeGlobalResourceTypes` field has no impact on the `EXCLUSION_BY_RESOURCE_TYPES` recording strategy. This means that the global IAM resource types ( IAM users, groups, roles, and customer managed policies) will not be automatically added as exclusions for `ExclusionByResourceTypes` when `IncludeGlobalResourceTypes` is set to `false` .
+     * >
+     * > The `IncludeGlobalResourceTypes` field should only be used to modify the `AllSupported` field, as the default for the `AllSupported` field is to record configuration changes for all supported resource types excluding the global IAM resource types. To include the global IAM resource types when `AllSupported` is set to `true` , make sure to set `IncludeGlobalResourceTypes` to `true` .
+     * >
+     * > To exclude the global IAM resource types for the `EXCLUSION_BY_RESOURCE_TYPES` recording strategy, you need to manually add them to the `ResourceTypes` field of `ExclusionByResourceTypes` . > *Required and optional fields*
+     * >
+     * > Before you set this field to `true` , set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` . Optionally, you can set the `useOnly` field of [RecordingStrategy](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `ALL_SUPPORTED_RESOURCE_TYPES` . > *Overriding fields*
+     * >
+     * > If you set this field to `false` but list global IAM resource types in the `ResourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) , AWS Config will still record configuration changes for those specified resource types *regardless* of if you set the `IncludeGlobalResourceTypes` field to false.
+     * >
+     * > If you do not want to record configuration changes to the global IAM resource types (IAM users, groups, roles, and customer managed policies), make sure to not list them in the `ResourceTypes` field in addition to setting the `IncludeGlobalResourceTypes` field to false.
+     */
+    IncludeGlobalResourceTypes?: boolean | undefined;
+    /**
+     * An object that specifies the recording strategy for the configuration recorder.
+     *
+     * - If you set the `useOnly` field of [RecordingStrategy](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `ALL_SUPPORTED_RESOURCE_TYPES` , AWS Config records configuration changes for all supported resource types, excluding the global IAM resource types. You also must set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` . When AWS Config adds support for a new resource type, AWS Config automatically starts recording resources of that type.
+     * - If you set the `useOnly` field of [RecordingStrategy](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `INCLUSION_BY_RESOURCE_TYPES` , AWS Config records configuration changes for only the resource types you specify in the `ResourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) .
+     * - If you set the `useOnly` field of [RecordingStrategy](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `EXCLUSION_BY_RESOURCE_TYPES` , AWS Config records configuration changes for all supported resource types except the resource types that you specify to exclude from being recorded in the `ResourceTypes` field of [ExclusionByResourceTypes](https://docs.aws.amazon.com/config/latest/APIReference/API_ExclusionByResourceTypes.html) .
+     *
+     * > *Required and optional fields*
+     * >
+     * > The `recordingStrategy` field is optional when you set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` .
+     * >
+     * > The `recordingStrategy` field is optional when you list resource types in the `ResourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) .
+     * >
+     * > The `recordingStrategy` field is required if you list resource types to exclude from recording in the `ResourceTypes` field of [ExclusionByResourceTypes](https://docs.aws.amazon.com/config/latest/APIReference/API_ExclusionByResourceTypes.html) . > *Overriding fields*
+     * >
+     * > If you choose `EXCLUSION_BY_RESOURCE_TYPES` for the recording strategy, the `ExclusionByResourceTypes` field will override other properties in the request.
+     * >
+     * > For example, even if you set `IncludeGlobalResourceTypes` to false, global IAM resource types will still be automatically recorded in this option unless those resource types are specifically listed as exclusions in the `ResourceTypes` field of `ExclusionByResourceTypes` . > *Global resources types and the resource exclusion recording strategy*
+     * >
+     * > By default, if you choose the `EXCLUSION_BY_RESOURCE_TYPES` recording strategy, when AWS Config adds support for a new resource type in the Region where you set up the configuration recorder, including global resource types, AWS Config starts recording resources of that type automatically.
+     * >
+     * > Unless specifically listed as exclusions, `AWS::RDS::GlobalCluster` will be recorded automatically in all supported AWS 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 AWS Config was available before February 2022. You cannot be record the global IAM resouce types in Regions supported by AWS Config after February 2022. This list where you cannot record the global IAM resource types includes the following Regions:
+     * >
+     * > - Asia Pacific (Hyderabad)
+     * > - Asia Pacific (Melbourne)
+     * > - Canada West (Calgary)
+     * > - Europe (Spain)
+     * > - Europe (Zurich)
+     * > - Israel (Tel Aviv)
+     * > - Middle East (UAE)
+     */
+    RecordingStrategy?: RecordingStrategy | undefined;
+    /**
+     * A comma-separated list that specifies which resource types AWS Config records.
+     *
+     * For a list of valid `ResourceTypes` values, see the *Resource Type Value* column in [Supported AWS resource Types](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html#supported-resources) in the *AWS Config developer guide* .
+     *
+     * > *Required and optional fields*
+     * >
+     * > Optionally, you can set the `useOnly` field of [RecordingStrategy](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingStrategy.html) to `INCLUSION_BY_RESOURCE_TYPES` .
+     * >
+     * > To record all configuration changes, set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` , and either omit this field or don't specify any resource types in this field. If you set the `AllSupported` field to `false` and specify values for `ResourceTypes` , when AWS Config adds support for a new type of resource, it will not record resources of that type unless you manually add that type to your recording group. > *Region availability*
+     * >
+     * > Before specifying a resource type for AWS Config to track, check [Resource Coverage by Region Availability](https://docs.aws.amazon.com/config/latest/developerguide/what-is-resource-config-coverage.html) to see if the resource type is supported in the AWS Region where you set up AWS Config . If a resource type is supported by AWS Config in at least one Region, you can enable the recording of that resource type in all Regions supported by AWS Config , even if the specified resource type is not supported in the AWS Region where you set up AWS Config .
+     */
+    ResourceTypes?: string[] | undefined;
+};
+/**
+ * Specifies the default recording frequency that AWS Config uses to record configuration changes. AWS 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.
+ *
+ * > AWS 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.
+ */
+export type RecordingMode = {
+    /**
+     * The default recording frequency that AWS Config uses to record configuration changes.
+     *
+     * > Daily recording cannot be specified for the following resource types:
+     * >
+     * > - `AWS::Config::ResourceCompliance`
+     * > - `AWS::Config::ConformancePackCompliance`
+     * > - `AWS::Config::ConfigurationRecorder`
+     * >
+     * > For the *allSupported* ( `ALL_SUPPORTED_RESOURCE_TYPES` ) recording strategy, these resource types will be set to Continuous recording.
+     */
+    RecordingFrequency: string;
+    /**
+     * An array of `recordingModeOverride` objects for you to specify your overrides for the recording mode. The `recordingModeOverride` object in the `recordingModeOverrides` array consists of three fields: a `description` , the new `recordingFrequency` , and an array of `resourceTypes` to override.
+     */
+    RecordingModeOverrides?: RecordingModeOverride[] | undefined;
+};
+/**
+ * An object for you to specify your overrides for the recording mode.
+ */
+export type RecordingModeOverride = {
+    /**
+     * A description that you provide for the override.
+     */
+    Description?: string | undefined;
+    /**
+     * The recording frequency that will be applied to all the resource types specified in the override.
+     *
+     * - 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.
+     *
+     * > AWS 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.
+     */
+    RecordingFrequency: string;
+    /**
+     * A comma-separated list that specifies which resource types AWS Config includes in the override.
+     *
+     * > Daily recording cannot be specified for the following resource types:
+     * >
+     * > - `AWS::Config::ResourceCompliance`
+     * > - `AWS::Config::ConformancePackCompliance`
+     * > - `AWS::Config::ConfigurationRecorder`
+     */
+    ResourceTypes: string[];
+};
+/**
+ * Specifies the recording strategy of the configuration recorder.
+ *
+ * Valid values include: `ALL_SUPPORTED_RESOURCE_TYPES` , `INCLUSION_BY_RESOURCE_TYPES` , and `EXCLUSION_BY_RESOURCE_TYPES` .
+ */
+export type RecordingStrategy = {
+    /**
+     * The recording strategy for the configuration recorder.
+     *
+     * - If you set this option to `ALL_SUPPORTED_RESOURCE_TYPES` , AWS Config records configuration changes for all supported resource types, excluding the global IAM resource types. You also must set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` . When AWS Config adds support for a new resource type, AWS Config automatically starts recording resources of that type. For a list of supported resource types, see [Supported Resource Types](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html#supported-resources) in the *AWS Config developer guide* .
+     * - If you set this option to `INCLUSION_BY_RESOURCE_TYPES` , AWS Config records configuration changes for only the resource types that you specify in the `ResourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) .
+     * - If you set this option to `EXCLUSION_BY_RESOURCE_TYPES` , AWS Config records configuration changes for all supported resource types, except the resource types that you specify to exclude from being recorded in the `ResourceTypes` field of [ExclusionByResourceTypes](https://docs.aws.amazon.com/config/latest/APIReference/API_ExclusionByResourceTypes.html) .
+     *
+     * > *Required and optional fields*
+     * >
+     * > The `recordingStrategy` field is optional when you set the `AllSupported` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) to `true` .
+     * >
+     * > The `recordingStrategy` field is optional when you list resource types in the `ResourceTypes` field of [RecordingGroup](https://docs.aws.amazon.com/config/latest/APIReference/API_RecordingGroup.html) .
+     * >
+     * > The `recordingStrategy` field is required if you list resource types to exclude from recording in the `ResourceTypes` field of [ExclusionByResourceTypes](https://docs.aws.amazon.com/config/latest/APIReference/API_ExclusionByResourceTypes.html) . > *Overriding fields*
+     * >
+     * > If you choose `EXCLUSION_BY_RESOURCE_TYPES` for the recording strategy, the `ExclusionByResourceTypes` field will override other properties in the request.
+     * >
+     * > For example, even if you set `IncludeGlobalResourceTypes` to false, global IAM resource types will still be automatically recorded in this option unless those resource types are specifically listed as exclusions in the `ResourceTypes` field of `ExclusionByResourceTypes` . > *Global resource types and the exclusion recording strategy*
+     * >
+     * > By default, if you choose the `EXCLUSION_BY_RESOURCE_TYPES` recording strategy, when AWS Config adds support for a new resource type in the Region where you set up the configuration recorder, including global resource types, AWS Config starts recording resources of that type automatically.
+     * >
+     * > Unless specifically listed as exclusions, `AWS::RDS::GlobalCluster` will be recorded automatically in all supported AWS 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 AWS Config was available before February 2022. You cannot be record the global IAM resouce types in Regions supported by AWS Config after February 2022. This list where you cannot record the global IAM resource types includes the following Regions:
+     * >
+     * > - Asia Pacific (Hyderabad)
+     * > - Asia Pacific (Melbourne)
+     * > - Canada West (Calgary)
+     * > - Europe (Spain)
+     * > - Europe (Zurich)
+     * > - Israel (Tel Aviv)
+     * > - Middle East (UAE)
+     */
+    UseOnly: string;
+};
+//# sourceMappingURL=aws-config-configurationrecorder.d.ts.map

package/out/exports/resources.generated/aws-config-conformancepack.d.ts

@@ -0,0 +1,76 @@
+import type { ResourceDefinition } from "../main.ts";
+export type ConfigConformancePack = ResourceDefinition<"AWS::Config::ConformancePack", ConfigConformancePackProps>;
+/**
+ * A conformance pack is a collection of AWS Config rules and remediation actions that can be easily deployed in an account and a region. ConformancePack creates a service linked role in your account. The service linked role is created only when the role does not exist in your account.
+ */
+export type ConfigConformancePackProps = {
+    /**
+     * A list of ConformancePackInputParameter objects.
+     */
+    ConformancePackInputParameters?: ConformancePackInputParameter[] | undefined;
+    /**
+     * Name of the conformance pack you want to create.
+     * @minLength 1
+     * @maxLength 256
+     * @pattern [a-zA-Z][-a-zA-Z0-9]*
+     */
+    ConformancePackName: string;
+    /**
+     * The name of the Amazon S3 bucket where AWS Config stores conformance pack templates.
+     * @minLength 0
+     * @maxLength 63
+     */
+    DeliveryS3Bucket?: string | undefined;
+    /**
+     * The prefix for the Amazon S3 bucket.
+     * @minLength 0
+     * @maxLength 1024
+     */
+    DeliveryS3KeyPrefix?: string | undefined;
+    /**
+     * A string containing full conformance pack template body. Structure containing the template body with a minimum length of 1 byte and a maximum length of 51,200 bytes.
+     *
+     * > You can only use a YAML template with two resource types: config rule ( `AWS::Config::ConfigRule` ) and a remediation action ( `AWS::Config::RemediationConfiguration` ).
+     * @minLength 1
+     * @maxLength 51200
+     */
+    TemplateBody?: string | undefined;
+    /**
+     * Location of file containing the template body (s3://bucketname/prefix). The uri must point to the conformance pack template (max size: 300 KB) that is located in an Amazon S3 bucket.
+     *
+     * > You must have access to read Amazon S3 bucket.
+     * @minLength 1
+     * @maxLength 1024
+     * @pattern s3://.*
+     */
+    TemplateS3Uri?: string | undefined;
+    /**
+     * An object that contains the name or Amazon Resource Name (ARN) of the AWS Systems Manager document (SSM document) and the version of the SSM document that is used to create a conformance pack.
+     */
+    TemplateSSMDocumentDetails?: {
+        /**
+         * @minLength 3
+         * @maxLength 128
+         */
+        DocumentName?: string | undefined;
+        /**
+         * @minLength 1
+         * @maxLength 128
+         */
+        DocumentVersion?: string | undefined;
+    } | undefined;
+};
+/**
+ * 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.
+ */
+export type ConformancePackInputParameter = {
+    /**
+     * One part of a key-value pair.
+     */
+    ParameterName: string;
+    /**
+     * Another part of the key-value pair.
+     */
+    ParameterValue: string;
+};
+//# sourceMappingURL=aws-config-conformancepack.d.ts.map