@propulsionworks/cloudformation 0.0.1 → 0.1.0

package/out/exports/resources.generated/aws-location-tracker.d.ts

@@ -0,0 +1,84 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type LocationTracker = ResourceDefinitionWithAttributes<"AWS::Location::Tracker", LocationTrackerProps, LocationTrackerAttribs>;
+/**
+ * Specifies a tracker resource in your AWS account , which lets you receive current and historical location of devices.
+ */
+export type LocationTrackerProps = {
+    /**
+     * An optional description for the tracker resource.
+     * @minLength 0
+     * @maxLength 1000
+     */
+    Description?: string | undefined;
+    EventBridgeEnabled?: boolean | undefined;
+    KmsKeyEnableGeospatialQueries?: boolean | undefined;
+    /**
+     * A key identifier for an [AWS KMS customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html) . Enter a key ID, key ARN, alias name, or alias ARN.
+     * @minLength 1
+     * @maxLength 2048
+     */
+    KmsKeyId?: string | undefined;
+    /**
+     * Specifies the position filtering for the tracker resource.
+     *
+     * Valid values:
+     *
+     * - `TimeBased` - Location updates are evaluated against linked geofence collections, but not every location update is stored. If your update frequency is more often than 30 seconds, only one update per 30 seconds is stored for each unique device ID.
+     * - `DistanceBased` - If the device has moved less than 30 m (98.4 ft), location updates are ignored. Location updates within this area are neither evaluated against linked geofence collections, nor stored. This helps control costs by reducing the number of geofence evaluations and historical device positions to paginate through. Distance-based filtering can also reduce the effects of GPS noise when displaying device trajectories on a map.
+     * - `AccuracyBased` - If the device has moved less than the measured accuracy, location updates are ignored. For example, if two consecutive updates from a device have a horizontal accuracy of 5 m and 10 m, the second update is ignored if the device has moved less than 15 m. Ignored location updates are neither evaluated against linked geofence collections, nor stored. This can reduce the effects of GPS noise when displaying device trajectories on a map, and can help control your costs by reducing the number of geofence evaluations.
+     *
+     * This field is optional. If not specified, the default value is `TimeBased` .
+     */
+    PositionFiltering?: PositionFiltering | undefined;
+    PricingPlan?: PricingPlan | undefined;
+    /**
+     * This shape is deprecated since 2022-02-01: Deprecated. No longer allowed.
+     */
+    PricingPlanDataSource?: string | undefined;
+    /**
+     * An array of key-value pairs to apply to this resource.
+     */
+    Tags?: Tag[] | undefined;
+    /**
+     * The name for the tracker resource.
+     *
+     * Requirements:
+     *
+     * - Contain only alphanumeric characters (A-Z, a-z, 0-9) , hyphens (-), periods (.), and underscores (_).
+     * - Must be a unique tracker resource name.
+     * - No spaces allowed. For example, `ExampleTracker` .
+     * @minLength 1
+     * @maxLength 100
+     * @pattern ^[-._\w]+$
+     */
+    TrackerName: string;
+};
+export type LocationTrackerAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) for the tracker resource. Used when you need to specify a resource across all AWS .
+     *
+     * - Format example: `arn:aws:geo:region:account-id:tracker/ExampleTracker`
+     * @maxLength 1600
+     * @pattern ^arn(:[a-z0-9]+([.-][a-z0-9]+)*){2}(:([a-z0-9]+([.-][a-z0-9]+)*)?){2}:([^/].*)?$
+     */
+    Arn: string;
+    /**
+     * The timestamp for when the tracker resource was created in [ISO 8601](https://docs.aws.amazon.com/https://www.iso.org/iso-8601-date-and-time-format.html) format: `YYYY-MM-DDThh:mm:ss.sssZ` .
+     */
+    CreateTime: string;
+    /**
+     * Synonym for `Arn` . The Amazon Resource Name (ARN) for the tracker resource. Used when you need to specify a resource across all AWS .
+     *
+     * - Format example: `arn:aws:geo:region:account-id:tracker/ExampleTracker`
+     * @maxLength 1600
+     * @pattern ^arn(:[a-z0-9]+([.-][a-z0-9]+)*){2}(:([a-z0-9]+([.-][a-z0-9]+)*)?){2}:([^/].*)?$
+     */
+    TrackerArn: string;
+    /**
+     * The timestamp for when the tracker resource was last updated in [ISO 8601](https://docs.aws.amazon.com/https://www.iso.org/iso-8601-date-and-time-format.html) format: `YYYY-MM-DDThh:mm:ss.sssZ` .
+     */
+    UpdateTime: string;
+};
+export type PositionFiltering = "TimeBased" | "DistanceBased" | "AccuracyBased";
+export type PricingPlan = "RequestBasedUsage";
+//# sourceMappingURL=aws-location-tracker.d.ts.map

package/out/exports/resources.generated/aws-location-trackerconsumer.d.ts

@@ -0,0 +1,31 @@
+import type { ResourceDefinition } from "../main.ts";
+export type LocationTrackerConsumer = ResourceDefinition<"AWS::Location::TrackerConsumer", LocationTrackerConsumerProps>;
+/**
+ * The `AWS::Location::TrackerConsumer` resource specifies an association between a geofence collection and a tracker resource. The geofence collection is referred to as the *consumer* of the tracker. This allows the tracker resource to communicate location data to the linked geofence collection.
+ *
+ * > Currently not supported — Cross-account configurations, such as creating associations between a tracker resource in one account and a geofence collection in another account.
+ */
+export type LocationTrackerConsumerProps = {
+    /**
+     * The Amazon Resource Name (ARN) for the geofence collection to be associated to tracker resource. Used when you need to specify a resource across all AWS .
+     *
+     * - Format example: `arn:aws:geo:region:account-id:geofence-collection/ExampleGeofenceCollectionConsumer`
+     * @maxLength 1600
+     * @pattern ^arn(:[a-z0-9]+([.-][a-z0-9]+)*){2}(:([a-z0-9]+([.-][a-z0-9]+)*)?){2}:([^/].*)?$
+     */
+    ConsumerArn: string;
+    /**
+     * The name for the tracker resource.
+     *
+     * Requirements:
+     *
+     * - Contain only alphanumeric characters (A-Z, a-z, 0-9) , hyphens (-), periods (.), and underscores (_).
+     * - Must be a unique tracker resource name.
+     * - No spaces allowed. For example, `ExampleTracker` .
+     * @minLength 1
+     * @maxLength 100
+     * @pattern ^[-._\w]+$
+     */
+    TrackerName: string;
+};
+//# sourceMappingURL=aws-location-trackerconsumer.d.ts.map

package/out/exports/resources.generated/aws-logs-accountpolicy.d.ts

@@ -0,0 +1,150 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type LogsAccountPolicy = ResourceDefinitionWithAttributes<"AWS::Logs::AccountPolicy", LogsAccountPolicyProps, LogsAccountPolicyAttribs>;
+/**
+ * Creates or updates an account-level data protection policy or subscription filter policy that applies to all log groups or a subset of log groups in the account.
+ *
+ * *Data protection policy*
+ *
+ * A data protection policy can help safeguard sensitive data that's ingested by your log groups by auditing and masking the sensitive log data. Each account can have only one account-level data protection policy.
+ *
+ * > Sensitive data is detected and masked when it is ingested into a log group. When you set a data protection policy, log events ingested into the log groups before that time are not masked.
+ *
+ * If you create a data protection policy for your whole account, it applies to both existing log groups and all log groups that are created later in this account. The account policy is applied to existing log groups with eventual consistency. It might take up to 5 minutes before sensitive data in existing log groups begins to be masked.
+ *
+ * By default, when a user views a log event that includes masked data, the sensitive data is replaced by asterisks. A user who has the `logs:Unmask` permission can use a [GetLogEvents](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEvents.html) or [FilterLogEvents](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_FilterLogEvents.html) operation with the `unmask` parameter set to `true` to view the unmasked log events. Users with the `logs:Unmask` can also view unmasked data in the CloudWatch Logs console by running a CloudWatch Logs Insights query with the `unmask` query command.
+ *
+ * For more information, including a list of types of data that can be audited and masked, see [Protect sensitive log data with masking](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/mask-sensitive-log-data.html) .
+ *
+ * To create an account-level policy, you must be signed on with the `logs:PutDataProtectionPolicy` and `logs:PutAccountPolicy` permissions.
+ *
+ * An account-level policy applies to all log groups in the account. You can also create a data protection policy that applies to just one log group. If a log group has its own data protection policy and the account also has an account-level data protection policy, then the two policies are cumulative. Any sensitive term specified in either policy is masked.
+ *
+ * *Subscription filter policy*
+ *
+ * A subscription filter policy sets up a real-time feed of log events from CloudWatch Logs to other AWS services. Account-level subscription filter policies apply to both existing log groups and log groups that are created later in this account. Supported destinations are Kinesis Data Streams , Firehose , and Lambda . When log events are sent to the receiving service, they are Base64 encoded and compressed with the GZIP format.
+ *
+ * The following destinations are supported for subscription filters:
+ *
+ * - An Kinesis Data Streams data stream in the same account as the subscription policy, for same-account delivery.
+ * - An Firehose data stream in the same account as the subscription policy, for same-account delivery.
+ * - A Lambda function in the same account as the subscription policy, for same-account delivery.
+ * - A logical destination in a different account created with [PutDestination](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDestination.html) , for cross-account delivery. Kinesis Data Streams and Firehose are supported as logical destinations.
+ *
+ * Each account can have one account-level subscription filter policy. If you are updating an existing filter, you must specify the correct name in `PolicyName` . To perform a `PutAccountPolicy` subscription filter operation for any destination except a Lambda function, you must also have the `iam:PassRole` permission.
+ *
+ * *Field index policy*
+ *
+ * You can use field index policies to create indexes on fields found in log events in the log group. Creating field indexes lowers the scan volume for CloudWatch Logs Insights queries that reference those fields, because these queries attempt to skip the processing of log events that are known to not match the indexed field. Good fields to index are fields that you often need to query for. Common examples of indexes include request ID, session ID, user IDs, or instance IDs. For more information, see [Create field indexes to improve query performance and reduce costs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.html)
+ *
+ * For example, suppose you have created a field index for `requestId` . Then, any CloudWatch Logs Insights query on that log group that includes `requestId = *value*` or `requestId IN [ *value* , *value* , ...]` will attempt to process only the log events where the indexed field matches the specified value.
+ *
+ * Matches of log events to the names of indexed fields are case-sensitive. For example, an indexed field of `RequestId` won't match a log event containing `requestId` .
+ *
+ * You can have one account-level field index policy that applies to all log groups in the account. Or you can create as many as 20 account-level field index policies that are each scoped to a subset of log groups with the `SelectionCriteria` parameter. If you have multiple account-level index policies with selection criteria, no two of them can use the same or overlapping log group name prefixes. For example, if you have one policy filtered to log groups that start with `my-log` , you can't have another field index policy filtered to `my-logpprod` or `my-logging` .
+ *
+ * *Transformer policy*
+ *
+ * A *log transformer policy* transforms ingested log events into a different format, making them easier for you to process and analyze. You can also transform logs from different sources into standardized formats that contain relevant, source-specific information. After you have created a transformer, CloudWatch Logs performs this transformation at the time of log ingestion. You can then refer to the transformed versions of the logs during operations such as querying with CloudWatch Logs Insights or creating metric filters or subscription filters.
+ *
+ * You can also use a transformer to copy metadata from metadata keys into the log events themselves. This metadata can include log group name, log stream name, account ID and Region.
+ *
+ * A transformer for a log group is a series of processors, where each processor applies one type of transformation to the log events ingested into this log group. For more information about the available processors to use in a transformer, see [Processors that you can use](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html#CloudWatch-Logs-Transformation-Processors) .
+ *
+ * Having log events in standardized format enables visibility across your applications for your log analysis, reporting, and alarming needs. CloudWatch Logs provides transformation for common log types with out-of-the-box transformation templates for major AWS log sources such as VPC flow logs, Lambda , and Amazon RDS . You can use pre-built transformation templates or create custom transformation policies.
+ *
+ * You can create transformers only for the log groups in the Standard log class.
+ *
+ * You can have one account-level transformer policy that applies to all log groups in the account. Or you can create as many as 20 account-level transformer policies that are each scoped to a subset of log groups with the `selectionCriteria` parameter. If you have multiple account-level transformer policies with selection criteria, no two of them can use the same or overlapping log group name prefixes. For example, if you have one policy filtered to log groups that start with `my-log` , you can't have another field index policy filtered to `my-logpprod` or `my-logging` .
+ *
+ * You can also set up a transformer at the log-group level. For more information, see [AWS::Logs::Transformer](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-logs-transformer.html) . If there is both a log-group level transformer created with `PutTransformer` and an account-level transformer that could apply to the same log group, the log group uses only the log-group level transformer. It ignores the account-level transformer.
+ */
+export type LogsAccountPolicyProps = {
+    /**
+     * Specify the policy, in JSON.
+     *
+     * *Data protection policy*
+     *
+     * A data protection policy must include two JSON blocks:
+     *
+     * - The first block must include both a `DataIdentifer` array and an `Operation` property with an `Audit` action. The `DataIdentifer` array lists the types of sensitive data that you want to mask. For more information about the available options, see [Types of data that you can mask](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/mask-sensitive-log-data-types.html) .
+     *
+     * The `Operation` property with an `Audit` action is required to find the sensitive data terms. This `Audit` action must contain a `FindingsDestination` object. You can optionally use that `FindingsDestination` object to list one or more destinations to send audit findings to. If you specify destinations such as log groups, Firehose streams, and S3 buckets, they must already exist.
+     * - The second block must include both a `DataIdentifer` array and an `Operation` property with an `Deidentify` action. The `DataIdentifer` array must exactly match the `DataIdentifer` array in the first block of the policy.
+     *
+     * The `Operation` property with the `Deidentify` action is what actually masks the data, and it must contain the `"MaskConfig": {}` object. The `"MaskConfig": {}` object must be empty.
+     *
+     * > The contents of the two `DataIdentifer` arrays must match exactly.
+     *
+     * In addition to the two JSON blocks, the `policyDocument` can also include `Name` , `Description` , and `Version` fields. The `Name` is different than the operation's `policyName` parameter, and is used as a dimension when CloudWatch Logs reports audit findings metrics to CloudWatch .
+     *
+     * The JSON specified in `policyDocument` can be up to 30,720 characters long.
+     *
+     * *Subscription filter policy*
+     *
+     * A subscription filter policy can include the following attributes in a JSON block:
+     *
+     * - *DestinationArn* The ARN of the destination to deliver log events to. Supported destinations are:
+     *
+     * - An Kinesis Data Streams data stream in the same account as the subscription policy, for same-account delivery.
+     * - An Firehose data stream in the same account as the subscription policy, for same-account delivery.
+     * - A Lambda function in the same account as the subscription policy, for same-account delivery.
+     * - A logical destination in a different account created with [PutDestination](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDestination.html) , for cross-account delivery. Kinesis Data Streams and Firehose are supported as logical destinations.
+     * - *RoleArn* The ARN of an IAM role that grants CloudWatch Logs permissions to deliver ingested log events to the destination stream. You don't need to provide the ARN when you are working with a logical destination for cross-account delivery.
+     * - *FilterPattern* A filter pattern for subscribing to a filtered stream of log events.
+     * - *Distribution* The method used to distribute log data to the destination. By default, log data is grouped by log stream, but the grouping can be set to `Random` for a more even distribution. This property is only applicable when the destination is an Kinesis Data Streams data stream.
+     *
+     * *Field index policy*
+     *
+     * A field index filter policy can include the following attribute in a JSON block:
+     *
+     * - *Fields* The array of field indexes to create.
+     *
+     * The following is an example of an index policy document that creates two indexes, `RequestId` and `TransactionId` .
+     *
+     * `"policyDocument": "{ \"Fields\": [ \"RequestId\", \"TransactionId\" ] }"`
+     *
+     * *Transformer policy*
+     *
+     * A transformer policy must include one JSON block with the array of processors and their configurations. For more information about available processors, see [Processors that you can use](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html#CloudWatch-Logs-Transformation-Processors) .
+     * @minLength 1
+     * @maxLength 30720
+     */
+    PolicyDocument: string;
+    /**
+     * A name for the policy. This must be unique within the account.
+     * @minLength 1
+     * @maxLength 256
+     * @pattern ^[^:*]{1,256}$
+     */
+    PolicyName: string;
+    /**
+     * The type of policy that you're creating or updating.
+     */
+    PolicyType: "DATA_PROTECTION_POLICY" | "SUBSCRIPTION_FILTER_POLICY" | "FIELD_INDEX_POLICY" | "TRANSFORMER_POLICY";
+    /**
+     * Currently the only valid value for this parameter is `ALL` , which specifies that the policy applies to all log groups in the account. If you omit this parameter, the default of `ALL` is used. To scope down a subscription filter policy to a subset of log groups, use the `SelectionCriteria` parameter.
+     */
+    Scope?: "ALL" | undefined;
+    /**
+     * Use this parameter to apply the new policy to a subset of log groups in the account.
+     *
+     * You need to specify `SelectionCriteria` only when you specify `SUBSCRIPTION_FILTER_POLICY` , `FIELD_INDEX_POLICY` or `TRANSFORMER_POLICY` for `PolicyType` .
+     *
+     * If `PolicyType` is `SUBSCRIPTION_FILTER_POLICY` , the only supported `SelectionCriteria` filter is `LogGroupName NOT IN []`
+     *
+     * If `PolicyType` is `FIELD_INDEX_POLICY` or `TRANSFORMER_POLICY` , the only supported `SelectionCriteria` filter is `LogGroupNamePrefix`
+     *
+     * The `SelectionCriteria` string can be up to 25KB in length. The length is determined by using its UTF-8 bytes.
+     *
+     * Using the `SelectionCriteria` parameter with `SUBSCRIPTION_FILTER_POLICY` is useful to help prevent infinite loops. For more information, see [Log recursion prevention](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Subscriptions-recursion-prevention.html) .
+     */
+    SelectionCriteria?: string | undefined;
+};
+export type LogsAccountPolicyAttribs = {
+    /**
+     * The account ID of the account where this policy was created. For example, `123456789012` .
+     * @pattern ^\d{12}$
+     */
+    AccountId: string;
+};
+//# sourceMappingURL=aws-logs-accountpolicy.d.ts.map

package/out/exports/resources.generated/aws-logs-delivery.d.ts

@@ -0,0 +1,71 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type LogsDelivery = ResourceDefinitionWithAttributes<"AWS::Logs::Delivery", LogsDeliveryProps, LogsDeliveryAttribs>;
+/**
+ * This structure contains information about one *delivery* in your account.
+ *
+ * A delivery is a connection between a logical *delivery source* and a logical *delivery destination* .
+ *
+ * For more information, see [CreateDelivery](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html) .
+ *
+ * To update an existing delivery configuration, use [UpdateDeliveryConfiguration](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_UpdateDeliveryConfiguration.html) .
+ */
+export type LogsDeliveryProps = {
+    /**
+     * The ARN of the delivery destination that is associated with this delivery.
+     */
+    DeliveryDestinationArn: string;
+    /**
+     * The name of the delivery source that is associated with this delivery.
+     * @minLength 1
+     * @maxLength 60
+     * @pattern [\w-]*$
+     */
+    DeliverySourceName: string;
+    /**
+     * The field delimiter that is used between record fields when the final output format of a delivery is in `Plain` , `W3C` , or `Raw` format.
+     * @minLength 1
+     * @maxLength 5
+     */
+    FieldDelimiter?: string | undefined;
+    /**
+     * The list of record fields to be delivered to the destination, in order. If the delivery's log source has mandatory fields, they must be included in this list.
+     */
+    RecordFields?: string[] | undefined;
+    /**
+     * Use this parameter to cause the S3 objects that contain delivered logs to use a prefix structure that allows for integration with Apache Hive.
+     */
+    S3EnableHiveCompatiblePath?: boolean | undefined;
+    /**
+     * Use this to reconfigure the S3 object prefix to contain either static or variable sections. The valid variables to use in the suffix path will vary by each log source. To find the values supported for the suffix path for each log source, use the [DescribeConfigurationTemplates](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_DescribeConfigurationTemplates.html) operation and check the `allowedSuffixPathFields` field in the response.
+     * @minLength 0
+     * @maxLength 256
+     */
+    S3SuffixPath?: string | undefined;
+    /**
+     * An array of key-value pairs to apply to the delivery.
+     *
+     * For more information, see [Tag](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html) .
+     */
+    Tags?: Tag[] | undefined;
+};
+export type LogsDeliveryAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) that uniquely identifies this delivery.
+     */
+    Arn: string;
+    /**
+     * Displays whether the delivery destination associated with this delivery is CloudWatch Logs , Amazon S3 , or Firehose .
+     * @minLength 1
+     * @maxLength 12
+     * @pattern ^[0-9A-Za-z]+$
+     */
+    DeliveryDestinationType: string;
+    /**
+     * The unique ID that identifies this delivery in your account.
+     * @minLength 1
+     * @maxLength 64
+     * @pattern ^[0-9A-Za-z]+$
+     */
+    DeliveryId: string;
+};
+//# sourceMappingURL=aws-logs-delivery.d.ts.map

package/out/exports/resources.generated/aws-logs-deliverydestination.d.ts

@@ -0,0 +1,59 @@
+import type { ResourceDefinitionWithAttributes, TemplatePolicyDocument, Tag } from "../main.ts";
+export type LogsDeliveryDestination = ResourceDefinitionWithAttributes<"AWS::Logs::DeliveryDestination", LogsDeliveryDestinationProps, LogsDeliveryDestinationAttribs>;
+/**
+ * This structure contains information about one *delivery destination* in your account. A delivery destination is an AWS resource that represents an AWS service that logs can be sent to. CloudWatch Logs, Amazon S3, are supported as Firehose delivery destinations.
+ *
+ * To configure logs delivery between a supported AWS service and a destination, you must do the following:
+ *
+ * - Create a delivery source, which is a logical object that represents the resource that is actually sending the logs. For more information, see [PutDeliverySource](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliverySource.html) .
+ * - Create a *delivery destination* , which is a logical object that represents the actual delivery destination.
+ * - If you are delivering logs cross-account, you must use [PutDeliveryDestinationPolicy](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html) in the destination account to assign an IAM policy to the destination. This policy allows delivery to that destination.
+ * - Create a *delivery* by pairing exactly one delivery source and one delivery destination. For more information, see [CreateDelivery](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html) .
+ *
+ * You can configure a single delivery source to send logs to multiple destinations by creating multiple deliveries. You can also create multiple deliveries to configure multiple delivery sources to send logs to the same delivery destination.
+ */
+export type LogsDeliveryDestinationProps = {
+    /**
+     * An IAM policy that grants permissions to CloudWatch Logs to deliver logs cross-account to a specified destination in this account. For examples of this policy, see [Examples](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html#API_PutDeliveryDestinationPolicy_Examples) in the CloudWatch Logs API Reference.
+     * @policy
+     */
+    DeliveryDestinationPolicy?: TemplatePolicyDocument | undefined;
+    /**
+     * The ARN of the AWS destination that this delivery destination represents. That AWS destination can be a log group in CloudWatch Logs , an Amazon S3 bucket, or a Firehose stream.
+     */
+    DestinationResourceArn?: string | undefined;
+    /**
+     * The name of this delivery destination.
+     * @minLength 1
+     * @maxLength 60
+     * @pattern [\w-]*$
+     */
+    Name: string;
+    /**
+     * The format of the logs that are sent to this delivery destination.
+     * @minLength 1
+     * @maxLength 12
+     * @pattern ^[0-9A-Za-z]+$
+     */
+    OutputFormat?: string | undefined;
+    /**
+     * An array of key-value pairs to apply to the delivery destination.
+     *
+     * For more information, see [Tag](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html) .
+     */
+    Tags?: Tag[] | undefined;
+};
+export type LogsDeliveryDestinationAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) that uniquely identifies this delivery destination.
+     */
+    Arn: string;
+    /**
+     * Displays whether this delivery destination is CloudWatch Logs, Amazon S3, or Firehose.
+     * @minLength 1
+     * @maxLength 12
+     * @pattern ^[0-9A-Za-z]+$
+     */
+    DeliveryDestinationType: string;
+};
+//# sourceMappingURL=aws-logs-deliverydestination.d.ts.map

package/out/exports/resources.generated/aws-logs-deliverysource.d.ts

@@ -0,0 +1,59 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type LogsDeliverySource = ResourceDefinitionWithAttributes<"AWS::Logs::DeliverySource", LogsDeliverySourceProps, LogsDeliverySourceAttribs>;
+/**
+ * Creates or updates one *delivery source* in your account. A delivery source is an AWS resource that sends logs to an AWS destination. The destination can be CloudWatch Logs , Amazon S3 , or Firehose .
+ *
+ * Only some AWS services support being configured as a delivery source. These services are listed as *Supported [V2 Permissions]* in the table at [Enabling logging from AWS services.](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html)
+ *
+ * To configure logs delivery between a supported AWS service and a destination, you must do the following:
+ *
+ * - Create a delivery source, which is a logical object that represents the resource that is actually sending the logs.
+ * - Create a *delivery destination* , which is a logical object that represents the actual delivery destination. For more information, see [AWS::Logs::DeliveryDestination](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-logs-deliverydestination.html) or [PutDeliveryDestination](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestination.html) .
+ * - Create a *delivery* by pairing exactly one delivery source and one delivery destination. For more information, see [AWS::Logs::Delivery](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-logs-delivery.html) or [CreateDelivery](https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html) .
+ *
+ * You can configure a single delivery source to send logs to multiple destinations by creating multiple deliveries. You can also create multiple deliveries to configure multiple delivery sources to send logs to the same delivery destination.
+ */
+export type LogsDeliverySourceProps = {
+    /**
+     * The type of log that the source is sending. For valid values for this parameter, see the documentation for the source service.
+     * @minLength 1
+     * @maxLength 255
+     * @pattern [\w-]*$
+     */
+    LogType?: string | undefined;
+    /**
+     * The unique name of the delivery source.
+     * @minLength 1
+     * @maxLength 60
+     * @pattern [\w-]*$
+     */
+    Name: string;
+    /**
+     * The ARN of the AWS resource that is generating and sending logs. For example, `arn:aws:workmail:us-east-1:123456789012:organization/m-1234EXAMPLEabcd1234abcd1234abcd1234`
+     */
+    ResourceArn?: string | undefined;
+    /**
+     * An array of key-value pairs to apply to the delivery source.
+     *
+     * For more information, see [Tag](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html) .
+     */
+    Tags?: Tag[] | undefined;
+};
+export type LogsDeliverySourceAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) that uniquely identifies this delivery source.
+     */
+    Arn: string;
+    /**
+     * This array contains the ARN of the AWS resource that sends logs and is represented by this delivery source. Currently, only one ARN can be in the array.
+     */
+    ResourceArns: string[];
+    /**
+     * The AWS service that is sending logs.
+     * @minLength 1
+     * @maxLength 255
+     * @pattern [\w-]*$
+     */
+    Service: string;
+};
+//# sourceMappingURL=aws-logs-deliverysource.d.ts.map

package/out/exports/resources.generated/aws-logs-destination.d.ts

@@ -0,0 +1,36 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type LogsDestination = ResourceDefinitionWithAttributes<"AWS::Logs::Destination", LogsDestinationProps, LogsDestinationAttribs>;
+/**
+ * The AWS::Logs::Destination resource specifies a CloudWatch Logs destination. A destination encapsulates a physical resource (such as an Amazon Kinesis data stream) and enables you to subscribe that resource to a stream of log events.
+ */
+export type LogsDestinationProps = {
+    /**
+     * The name of the destination.
+     * @minLength 1
+     * @maxLength 512
+     * @pattern ^[^:*]{1,512}$
+     */
+    DestinationName: string;
+    /**
+     * An IAM policy document that governs which AWS accounts can create subscription filters against this destination.
+     * @minLength 1
+     */
+    DestinationPolicy?: string | undefined;
+    /**
+     * The ARN of an IAM role that permits CloudWatch Logs to send data to the specified AWS resource.
+     * @minLength 1
+     */
+    RoleArn: string;
+    /**
+     * The Amazon Resource Name (ARN) of the physical target where the log events are delivered (for example, a Kinesis stream).
+     * @minLength 1
+     */
+    TargetArn: string;
+};
+export type LogsDestinationAttribs = {
+    /**
+     * The ARN of the CloudWatch Logs destination, such as `arn:aws:logs:us-west-1:123456789012:destination:MyDestination` .
+     */
+    Arn: string;
+};
+//# sourceMappingURL=aws-logs-destination.d.ts.map

package/out/exports/resources.generated/aws-logs-integration.d.ts

@@ -0,0 +1,64 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type LogsIntegration = ResourceDefinitionWithAttributes<"AWS::Logs::Integration", LogsIntegrationProps, LogsIntegrationAttribs>;
+/**
+ * Creates an integration between CloudWatch Logs and another service in this account. Currently, only integrations with OpenSearch Service are supported, and currently you can have only one integration in your account.
+ *
+ * Integrating with OpenSearch Service makes it possible for you to create curated vended logs dashboards, powered by OpenSearch Service analytics. For more information, see [Vended log dashboards powered by Amazon OpenSearch Service](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-OpenSearch-Dashboards.html) .
+ *
+ * You can use this operation only to create a new integration. You can't modify an existing integration.
+ */
+export type LogsIntegrationProps = {
+    /**
+     * The name of this integration.
+     * @minLength 1
+     * @maxLength 50
+     * @pattern [\.\-_/#A-Za-z0-9]+
+     */
+    IntegrationName: string;
+    /**
+     * The type of integration. Integrations with OpenSearch Service have the type `OPENSEARCH` .
+     */
+    IntegrationType: "OPENSEARCH";
+    /**
+     * This structure contains configuration details about an integration between CloudWatch Logs and another entity.
+     */
+    ResourceConfig: {
+        OpenSearchResourceConfig?: OpenSearchResourceConfig | undefined;
+    };
+};
+export type LogsIntegrationAttribs = {
+    /**
+     * The current status of this integration.
+     */
+    IntegrationStatus: "PROVISIONING" | "ACTIVE" | "FAILED";
+};
+/**
+ * This structure contains configuration details about an integration between CloudWatch Logs and OpenSearch Service.
+ */
+export type OpenSearchResourceConfig = {
+    /**
+     * If you want to use an existing OpenSearch Service application for your integration with OpenSearch Service, specify it here. If you omit this, a new application will be created.
+     */
+    ApplicationARN?: string | undefined;
+    /**
+     * Specify the ARNs of IAM roles and IAM users who you want to grant permission to for viewing the dashboards.
+     *
+     * > In addition to specifying these users here, you must also grant them the *CloudWatchOpenSearchDashboardAccess* IAM policy. For more information, see [IAM policies for users](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/OpenSearch-Dashboards-UserRoles.html) .
+     */
+    DashboardViewerPrincipals: string[];
+    /**
+     * Specify the ARN of an IAM role that CloudWatch Logs will use to create the integration. This role must have the permissions necessary to access the OpenSearch Service collection to be able to create the dashboards. For more information about the permissions needed, see [Permissions that the integration needs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/OpenSearch-Dashboards-CreateRole.html) in the CloudWatch Logs User Guide.
+     */
+    DataSourceRoleArn: string;
+    /**
+     * To have the vended dashboard data encrypted with AWS KMS instead of the CloudWatch Logs default encryption method, specify the ARN of the AWS KMS key that you want to use.
+     */
+    KmsKeyArn?: string | undefined;
+    /**
+     * Specify how many days that you want the data derived by OpenSearch Service to be retained in the index that the dashboard refers to. This also sets the maximum time period that you can choose when viewing data in the dashboard. Choosing a longer time frame will incur additional costs.
+     * @min 1
+     * @max 3650
+     */
+    RetentionDays?: number | undefined;
+};
+//# sourceMappingURL=aws-logs-integration.d.ts.map

package/out/exports/resources.generated/aws-logs-loganomalydetector.d.ts

@@ -0,0 +1,66 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type LogsLogAnomalyDetector = ResourceDefinitionWithAttributes<"AWS::Logs::LogAnomalyDetector", LogsLogAnomalyDetectorProps, LogsLogAnomalyDetectorAttribs>;
+/**
+ * Creates or updates an *anomaly detector* that regularly scans one or more log groups and look for patterns and anomalies in the logs.
+ *
+ * An anomaly detector can help surface issues by automatically discovering anomalies in your log event traffic. An anomaly detector uses machine learning algorithms to scan log events and find *patterns* . A pattern is a shared text structure that recurs among your log fields. Patterns provide a useful tool for analyzing large sets of logs because a large number of log events can often be compressed into a few patterns.
+ *
+ * The anomaly detector uses pattern recognition to find `anomalies` , which are unusual log events. It compares current log events and patterns with trained baselines.
+ *
+ * Fields within a pattern are called *tokens* . Fields that vary within a pattern, such as a request ID or timestamp, are referred to as *dynamic tokens* and represented by `<*>` .
+ *
+ * For more information see [Log anomaly detection](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/LogsAnomalyDetection.html) .
+ */
+export type LogsLogAnomalyDetectorProps = {
+    /**
+     * The ID of the account to create the anomaly detector in.
+     */
+    AccountId?: string | undefined;
+    /**
+     * The number of days to have visibility on an anomaly. After this time period has elapsed for an anomaly, it will be automatically baselined and the anomaly detector will treat new occurrences of a similar anomaly as normal. Therefore, if you do not correct the cause of an anomaly during the time period specified in `AnomalyVisibilityTime` , it will be considered normal going forward and will not be detected as an anomaly.
+     */
+    AnomalyVisibilityTime?: number | undefined;
+    /**
+     * A name for this anomaly detector.
+     */
+    DetectorName?: string | undefined;
+    /**
+     * Specifies how often the anomaly detector is to run and look for anomalies. Set this value according to the frequency that the log group receives new logs. For example, if the log group receives new log events every 10 minutes, then 15 minutes might be a good setting for `EvaluationFrequency` .
+     */
+    EvaluationFrequency?: "FIVE_MIN" | "TEN_MIN" | "FIFTEEN_MIN" | "THIRTY_MIN" | "ONE_HOUR" | undefined;
+    /**
+     * You can use this parameter to limit the anomaly detection model to examine only log events that match the pattern you specify here. For more information, see [Filter and Pattern Syntax](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html) .
+     * @pattern
+     */
+    FilterPattern?: string | undefined;
+    /**
+     * Optionally assigns a AWS KMS key to secure this anomaly detector and its findings. If a key is assigned, the anomalies found and the model used by this detector are encrypted at rest with the key. If a key is assigned to an anomaly detector, a user must have permissions for both this key and for the anomaly detector to retrieve information about the anomalies that it finds.
+     *
+     * For more information about using a AWS KMS key and to see the required IAM policy, see [Use a AWS KMS key with an anomaly detector](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/LogsAnomalyDetection-KMS.html) .
+     * @maxLength 256
+     */
+    KmsKeyId?: string | undefined;
+    /**
+     * The ARN of the log group that is associated with this anomaly detector. You can specify only one log group ARN.
+     */
+    LogGroupArnList?: string[] | undefined;
+};
+export type LogsLogAnomalyDetectorAttribs = {
+    /**
+     * The ARN of the anomaly detector.
+     */
+    AnomalyDetectorArn: string;
+    /**
+     * Specifies whether the anomaly detector is currently active.
+     */
+    AnomalyDetectorStatus: string;
+    /**
+     * The time that the anomaly detector was created.
+     */
+    CreationTimeStamp: number;
+    /**
+     * The time that the anomaly detector was most recently modified.
+     */
+    LastModifiedTimeStamp: number;
+};
+//# sourceMappingURL=aws-logs-loganomalydetector.d.ts.map