@propulsionworks/cloudformation 0.0.2 → 0.1.0

package/out/exports/resources.generated/aws-ecr-repository.d.ts

@@ -0,0 +1,109 @@
+import type { ResourceDefinitionWithAttributes, TemplatePolicyDocument, Tag } from "../main.ts";
+export type ECRRepository = ResourceDefinitionWithAttributes<"AWS::ECR::Repository", ECRRepositoryProps, ECRRepositoryAttribs>;
+/**
+ * The `AWS::ECR::Repository` resource specifies an Amazon Elastic Container Registry (Amazon ECR) repository, where users can push and pull Docker images, Open Container Initiative (OCI) images, and OCI compatible artifacts. For more information, see [Amazon ECR private repositories](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Repositories.html) in the *Amazon ECR User Guide* .
+ */
+export type ECRRepositoryProps = {
+    /**
+     * If true, deleting the repository force deletes the contents of the repository. If false, the repository must be empty before attempting to delete it.
+     */
+    EmptyOnDelete?: boolean | undefined;
+    /**
+     * The encryption configuration for the repository. This determines how the contents of your repository are encrypted at rest.
+     */
+    EncryptionConfiguration?: EncryptionConfiguration | undefined;
+    /**
+     * The image scanning configuration for the repository. This determines whether images are scanned for known vulnerabilities after being pushed to the repository.
+     */
+    ImageScanningConfiguration?: ImageScanningConfiguration | undefined;
+    /**
+     * The tag mutability setting for the repository. If this parameter is omitted, the default setting of `MUTABLE` will be used which will allow image tags to be overwritten. If `IMMUTABLE` is specified, all image tags within the repository will be immutable which will prevent them from being overwritten.
+     */
+    ImageTagMutability?: "MUTABLE" | "IMMUTABLE" | undefined;
+    /**
+     * Creates or updates a lifecycle policy. For information about lifecycle policy syntax, see [Lifecycle policy template](https://docs.aws.amazon.com/AmazonECR/latest/userguide/LifecyclePolicies.html) .
+     */
+    LifecyclePolicy?: LifecyclePolicy | undefined;
+    /**
+     * The name to use for the repository. The repository name may be specified on its own (such as `nginx-web-app` ) or it can be prepended with a namespace to group the repository into a category (such as `project-a/nginx-web-app` ). If you don't specify a name, AWS CloudFormation generates a unique physical ID and uses that ID for the repository name. For more information, see [Name type](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-name.html) .
+     *
+     * The repository name must start with a letter and can only contain lowercase letters, numbers, hyphens, underscores, and forward slashes.
+     *
+     * > If you specify a name, you cannot perform updates that require replacement of this resource. You can perform updates that require no or some interruption. If you must replace the resource, specify a new name.
+     * @minLength 2
+     * @maxLength 256
+     * @pattern ^(?=.{2,256}$)((?:[a-z0-9]+(?:[._-][a-z0-9]+)*‍/)*[a-z0-9]+(?:[._-][a-z0-9]+)*)$
+     */
+    RepositoryName?: string | undefined;
+    /**
+     * The JSON repository policy text to apply to the repository. For more information, see [Amazon ECR repository policies](https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-policy-examples.html) in the *Amazon Elastic Container Registry User Guide* .
+     * @policy
+     */
+    RepositoryPolicyText?: TemplatePolicyDocument | undefined;
+    /**
+     * An array of key-value pairs to apply to this resource.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type ECRRepositoryAttribs = {
+    /**
+     * Returns the Amazon Resource Name (ARN) for the specified `AWS::ECR::Repository` resource. For example, `arn:aws:ecr: *eu-west-1* : *123456789012* :repository/ *test-repository*` .
+     */
+    Arn: string;
+    /**
+     * Returns the URI for the specified `AWS::ECR::Repository` resource. For example, `*123456789012* .dkr.ecr. *us-west-2* .amazonaws.com/repository` .
+     */
+    RepositoryUri: string;
+};
+/**
+ * The encryption configuration for the repository. This determines how the contents of your repository are encrypted at rest.
+ *
+ * By default, when no encryption configuration is set or the `AES256` encryption type is used, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts your data at rest using an AES256 encryption algorithm. This does not require any action on your part.
+ *
+ * For more control over the encryption of the contents of your repository, you can use server-side encryption with AWS Key Management Service key stored in AWS Key Management Service ( AWS KMS ) to encrypt your images. For more information, see [Amazon ECR encryption at rest](https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html) in the *Amazon Elastic Container Registry User Guide* .
+ */
+export type EncryptionConfiguration = {
+    /**
+     * The encryption type to use.
+     *
+     * If you use the `KMS` encryption type, the contents of the repository will be encrypted using server-side encryption with AWS Key Management Service key stored in AWS KMS . When you use AWS KMS to encrypt your data, you can either use the default AWS managed AWS KMS key for Amazon ECR, or specify your own AWS KMS key, which you already created.
+     *
+     * If you use the `KMS_DSSE` encryption type, the contents of the repository will be encrypted with two layers of encryption using server-side encryption with the AWS KMS Management Service key stored in AWS KMS . Similar to the `KMS` encryption type, you can either use the default AWS managed AWS KMS key for Amazon ECR, or specify your own AWS KMS key, which you've already created.
+     *
+     * If you use the `AES256` encryption type, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts the images in the repository using an AES256 encryption algorithm.
+     *
+     * For more information, see [Amazon ECR encryption at rest](https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html) in the *Amazon Elastic Container Registry User Guide* .
+     */
+    EncryptionType: EncryptionType;
+    /**
+     * If you use the `KMS` encryption type, specify the AWS KMS key to use for encryption. The alias, key ID, or full ARN of the AWS KMS key can be specified. The key must exist in the same Region as the repository. If no key is specified, the default AWS managed AWS KMS key for Amazon ECR will be used.
+     */
+    KmsKey?: string | undefined;
+};
+/**
+ * The encryption type to use.
+ */
+export type EncryptionType = "AES256" | "KMS" | "KMS_DSSE";
+/**
+ * The image scanning configuration for a repository.
+ */
+export type ImageScanningConfiguration = {
+    /**
+     * The setting that determines whether images are scanned after being pushed to a repository. If set to `true` , images will be scanned after being pushed. If this parameter is not specified, it will default to `false` and images will not be scanned unless a scan is manually started.
+     */
+    ScanOnPush?: boolean | undefined;
+};
+/**
+ * The `LifecyclePolicy` property type specifies a lifecycle policy. For information about lifecycle policy syntax, see [Lifecycle policy template](https://docs.aws.amazon.com/AmazonECR/latest/userguide/LifecyclePolicies.html) in the *Amazon ECR User Guide* .
+ */
+export type LifecyclePolicy = {
+    /**
+     * The JSON repository policy text to apply to the repository.
+     */
+    LifecyclePolicyText?: string | undefined;
+    /**
+     * The AWS account ID associated with the registry that contains the repository. If you do not specify a registry, the default registry is assumed.
+     */
+    RegistryId?: string | undefined;
+};
+//# sourceMappingURL=aws-ecr-repository.d.ts.map

package/out/exports/resources.generated/aws-ecr-repositorycreationtemplate.d.ts

@@ -0,0 +1,96 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ECRRepositoryCreationTemplate = ResourceDefinitionWithAttributes<"AWS::ECR::RepositoryCreationTemplate", ECRRepositoryCreationTemplateProps, ECRRepositoryCreationTemplateAttribs>;
+/**
+ * The details of the repository creation template associated with the request.
+ */
+export type ECRRepositoryCreationTemplateProps = {
+    /**
+     * A list of enumerable Strings representing the repository creation scenarios that this template will apply towards. The two supported scenarios are PULL_THROUGH_CACHE and REPLICATION
+     */
+    AppliedFor: AppliedForItem[];
+    /**
+     * The ARN of the role to be assumed by Amazon ECR. Amazon ECR will assume your supplied role when the customRoleArn is specified. When this field isn't specified, Amazon ECR will use the service-linked role for the repository creation template.
+     * @maxLength 2048
+     * @pattern ^arn:aws[-a-z0-9]*:iam::[0-9]{12}:role/[A-Za-z0-9+=,-.@_]*$
+     */
+    CustomRoleArn?: string | undefined;
+    /**
+     * The description associated with the repository creation template.
+     * @minLength 0
+     * @maxLength 256
+     */
+    Description?: string | undefined;
+    /**
+     * The encryption configuration associated with the repository creation template.
+     */
+    EncryptionConfiguration?: EncryptionConfiguration | undefined;
+    /**
+     * The tag mutability setting for the repository. If this parameter is omitted, the default setting of MUTABLE will be used which will allow image tags to be overwritten. If IMMUTABLE is specified, all image tags within the repository will be immutable which will prevent them from being overwritten.
+     */
+    ImageTagMutability?: "MUTABLE" | "IMMUTABLE" | undefined;
+    /**
+     * The lifecycle policy to use for repositories created using the template.
+     * @minLength 100
+     * @maxLength 30720
+     */
+    LifecyclePolicy?: string | undefined;
+    /**
+     * The repository namespace prefix associated with the repository creation template.
+     * @minLength 1
+     * @maxLength 256
+     * @pattern ^((?:[a-z0-9]+(?:[._-][a-z0-9]+)*‍/)*[a-z0-9]+(?:[._-][a-z0-9]+)*‍/?|ROOT)$
+     */
+    Prefix: string;
+    /**
+     * The repository policy to apply to repositories created using the template. A repository policy is a permissions policy associated with a repository to control access permissions.
+     */
+    RepositoryPolicy?: string | undefined;
+    /**
+     * The metadata to apply to the repository to help you categorize and organize. 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.
+     */
+    ResourceTags?: Tag[] | undefined;
+};
+export type ECRRepositoryCreationTemplateAttribs = {
+    /**
+     * The date and time, in JavaScript date format, when the repository creation template was created.
+     */
+    CreatedAt: string;
+    /**
+     * The date and time, in JavaScript date format, when the repository creation template was last updated.
+     */
+    UpdatedAt: string;
+};
+/**
+ * Enumerable Strings representing the repository creation scenarios that the template will apply towards.
+ */
+export type AppliedForItem = "REPLICATION" | "PULL_THROUGH_CACHE";
+/**
+ * The encryption configuration for the repository. This determines how the contents of your repository are encrypted at rest.
+ *
+ * By default, when no encryption configuration is set or the `AES256` encryption type is used, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts your data at rest using an AES256 encryption algorithm. This does not require any action on your part.
+ *
+ * For more control over the encryption of the contents of your repository, you can use server-side encryption with AWS Key Management Service key stored in AWS Key Management Service ( AWS KMS ) to encrypt your images. For more information, see [Amazon ECR encryption at rest](https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html) in the *Amazon Elastic Container Registry User Guide* .
+ */
+export type EncryptionConfiguration = {
+    /**
+     * The encryption type to use.
+     *
+     * If you use the `KMS` encryption type, the contents of the repository will be encrypted using server-side encryption with AWS Key Management Service key stored in AWS KMS . When you use AWS KMS to encrypt your data, you can either use the default AWS managed AWS KMS key for Amazon ECR, or specify your own AWS KMS key, which you already created.
+     *
+     * If you use the `KMS_DSSE` encryption type, the contents of the repository will be encrypted with two layers of encryption using server-side encryption with the AWS KMS Management Service key stored in AWS KMS . Similar to the `KMS` encryption type, you can either use the default AWS managed AWS KMS key for Amazon ECR, or specify your own AWS KMS key, which you've already created.
+     *
+     * If you use the `AES256` encryption type, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts the images in the repository using an AES256 encryption algorithm.
+     *
+     * For more information, see [Amazon ECR encryption at rest](https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html) in the *Amazon Elastic Container Registry User Guide* .
+     */
+    EncryptionType: EncryptionType;
+    /**
+     * If you use the `KMS` encryption type, specify the AWS KMS key to use for encryption. The alias, key ID, or full ARN of the AWS KMS key can be specified. The key must exist in the same Region as the repository. If no key is specified, the default AWS managed AWS KMS key for Amazon ECR will be used.
+     */
+    KmsKey?: string | undefined;
+};
+/**
+ * The encryption type to use.
+ */
+export type EncryptionType = "AES256" | "KMS" | "KMS_DSSE";
+//# sourceMappingURL=aws-ecr-repositorycreationtemplate.d.ts.map

package/out/exports/resources.generated/aws-ecs-capacityprovider.d.ts

@@ -0,0 +1,92 @@
+import type { ResourceDefinition, Tag } from "../main.ts";
+export type ECSCapacityProvider = ResourceDefinition<"AWS::ECS::CapacityProvider", ECSCapacityProviderProps>;
+/**
+ * Creates a new capacity provider. Capacity providers are associated with an Amazon ECS cluster and are used in capacity provider strategies to facilitate cluster auto scaling.
+ *
+ * Only capacity providers that use an Auto Scaling group can be created. Amazon ECS tasks on AWS Fargate use the `FARGATE` and `FARGATE_SPOT` capacity providers. These providers are available to all accounts in the AWS Regions that AWS Fargate supports.
+ */
+export type ECSCapacityProviderProps = {
+    /**
+     * The Auto Scaling group settings for the capacity provider.
+     */
+    AutoScalingGroupProvider?: AutoScalingGroupProvider | undefined;
+    /**
+     * The name of the capacity provider. If a name is specified, it cannot start with `aws` , `ecs` , or `fargate` . If no name is specified, a default name in the `CFNStackName-CFNResourceName-RandomString` format is used.
+     */
+    Name?: string | undefined;
+    /**
+     * The metadata that you apply to the capacity provider to help you categorize and organize it. Each tag consists of a key and an optional value. You define both.
+     *
+     * The following basic restrictions apply to tags:
+     *
+     * - Maximum number of tags per resource - 50
+     * - For each resource, each tag key must be unique, and each tag key can have only one value.
+     * - Maximum key length - 128 Unicode characters in UTF-8
+     * - Maximum value length - 256 Unicode characters in UTF-8
+     * - If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
+     * - Tag keys and values are case-sensitive.
+     * - Do not use `aws:` , `AWS:` , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for AWS use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
+     */
+    Tags?: Tag[] | undefined;
+};
+/**
+ * The details of the Auto Scaling group for the capacity provider.
+ */
+export type AutoScalingGroupProvider = {
+    /**
+     * The Amazon Resource Name (ARN) that identifies the Auto Scaling group, or the Auto Scaling group name.
+     */
+    AutoScalingGroupArn: string;
+    /**
+     * The managed draining option for the Auto Scaling group capacity provider. When you enable this, Amazon ECS manages and gracefully drains the EC2 container instances that are in the Auto Scaling group capacity provider.
+     */
+    ManagedDraining?: "DISABLED" | "ENABLED" | undefined;
+    /**
+     * The managed scaling settings for the Auto Scaling group capacity provider.
+     */
+    ManagedScaling?: ManagedScaling | undefined;
+    /**
+     * The managed termination protection setting to use for the Auto Scaling group capacity provider. This determines whether the Auto Scaling group has managed termination protection. The default is off.
+     *
+     * > When using managed termination protection, managed scaling must also be used otherwise managed termination protection doesn't work.
+     *
+     * When managed termination protection is on, Amazon ECS prevents the Amazon EC2 instances in an Auto Scaling group that contain tasks from being terminated during a scale-in action. The Auto Scaling group and each instance in the Auto Scaling group must have instance protection from scale-in actions on as well. For more information, see [Instance Protection](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection) in the *AWS Auto Scaling User Guide* .
+     *
+     * When managed termination protection is off, your Amazon EC2 instances aren't protected from termination when the Auto Scaling group scales in.
+     */
+    ManagedTerminationProtection?: "DISABLED" | "ENABLED" | undefined;
+};
+/**
+ * The managed scaling settings for the Auto Scaling group capacity provider.
+ *
+ * When managed scaling is turned on, Amazon ECS manages the scale-in and scale-out actions of the Auto Scaling group. Amazon ECS manages a target tracking scaling policy using an Amazon ECS managed CloudWatch metric with the specified `targetCapacity` value as the target value for the metric. For more information, see [Using managed scaling](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/asg-capacity-providers.html#asg-capacity-providers-managed-scaling) in the *Amazon Elastic Container Service Developer Guide* .
+ *
+ * If managed scaling is off, the user must manage the scaling of the Auto Scaling group.
+ */
+export type ManagedScaling = {
+    /**
+     * The period of time, in seconds, after a newly launched Amazon EC2 instance can contribute to CloudWatch metrics for Auto Scaling group. If this parameter is omitted, the default value of `300` seconds is used.
+     */
+    InstanceWarmupPeriod?: number | undefined;
+    /**
+     * The maximum number of Amazon EC2 instances that Amazon ECS will scale out at one time. If this parameter is omitted, the default value of `10000` is used.
+     */
+    MaximumScalingStepSize?: number | undefined;
+    /**
+     * The minimum number of Amazon EC2 instances that Amazon ECS will scale out at one time. The scale in process is not affected by this parameter If this parameter is omitted, the default value of `1` is used.
+     *
+     * When additional capacity is required, Amazon ECS will scale up the minimum scaling step size even if the actual demand is less than the minimum scaling step size.
+     *
+     * If you use a capacity provider with an Auto Scaling group configured with more than one Amazon EC2 instance type or Availability Zone, Amazon ECS will scale up by the exact minimum scaling step size value and will ignore both the maximum scaling step size as well as the capacity demand.
+     */
+    MinimumScalingStepSize?: number | undefined;
+    /**
+     * Determines whether to use managed scaling for the capacity provider.
+     */
+    Status?: "DISABLED" | "ENABLED" | undefined;
+    /**
+     * The target capacity utilization as a percentage for the capacity provider. The specified value must be greater than `0` and less than or equal to `100` . For example, if you want the capacity provider to maintain 10% spare capacity, then that means the utilization is 90%, so use a `targetCapacity` of `90` . The default value of `100` percent results in the Amazon EC2 instances in your Auto Scaling group being completely used.
+     */
+    TargetCapacity?: number | undefined;
+};
+//# sourceMappingURL=aws-ecs-capacityprovider.d.ts.map

package/out/exports/resources.generated/aws-ecs-cluster.d.ts

@@ -0,0 +1,211 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ECSCluster = ResourceDefinitionWithAttributes<"AWS::ECS::Cluster", ECSClusterProps, ECSClusterAttribs>;
+/**
+ * The `AWS::ECS::Cluster` resource creates an Amazon Elastic Container Service (Amazon ECS) cluster.
+ */
+export type ECSClusterProps = {
+    /**
+     * The short name of one or more capacity providers to associate with the cluster. A capacity provider must be associated with a cluster before it can be included as part of the default capacity provider strategy of the cluster or used in a capacity provider strategy when calling the [CreateService](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html) or [RunTask](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) actions.
+     *
+     * If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must be created but not associated with another cluster. New Auto Scaling group capacity providers can be created with the [CreateCapacityProvider](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCapacityProvider.html) API operation.
+     *
+     * To use a AWS Fargate capacity provider, specify either the `FARGATE` or `FARGATE_SPOT` capacity providers. The AWS Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used.
+     *
+     * The [PutCapacityProvider](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutCapacityProvider.html) API operation is used to update the list of available capacity providers for a cluster after the cluster is created.
+     */
+    CapacityProviders?: string[] | undefined;
+    /**
+     * A user-generated string that you use to identify your cluster. If you don't specify a name, AWS CloudFormation generates a unique physical ID for the name.
+     */
+    ClusterName?: string | undefined;
+    /**
+     * The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights with enhanced observability or CloudWatch Container Insights for a cluster.
+     *
+     * Container Insights with enhanced observability provides all the Container Insights metrics, plus additional task and container metrics. This version supports enhanced observability for Amazon ECS clusters using the Amazon EC2 and Fargate launch types. After you configure Container Insights with enhanced observability on Amazon ECS, Container Insights auto-collects detailed infrastructure telemetry from the cluster level down to the container level in your environment and displays these critical performance data in curated dashboards removing the heavy lifting in observability set-up.
+     *
+     * For more information, see [Monitor Amazon ECS containers using Container Insights with enhanced observability](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cloudwatch-container-insights.html) in the *Amazon Elastic Container Service Developer Guide* .
+     */
+    ClusterSettings?: ClusterSettings[] | undefined;
+    /**
+     * The execute command and managed storage configuration for the cluster.
+     */
+    Configuration?: ClusterConfiguration | undefined;
+    /**
+     * The default capacity provider strategy for the cluster. When services or tasks are run in the cluster with no launch type or capacity provider strategy specified, the default capacity provider strategy is used.
+     */
+    DefaultCapacityProviderStrategy?: CapacityProviderStrategyItem[] | undefined;
+    /**
+     * Use this parameter to set a default Service Connect namespace. After you set a default Service Connect namespace, any new services with Service Connect turned on that are created in the cluster are added as client services in the namespace. This setting only applies to new services that set the `enabled` parameter to `true` in the `ServiceConnectConfiguration` . You can set the namespace of each service individually in the `ServiceConnectConfiguration` to override this default parameter.
+     *
+     * Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see [Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) in the *Amazon Elastic Container Service Developer Guide* .
+     */
+    ServiceConnectDefaults?: ServiceConnectDefaults | undefined;
+    /**
+     * The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.
+     *
+     * The following basic restrictions apply to tags:
+     *
+     * - Maximum number of tags per resource - 50
+     * - For each resource, each tag key must be unique, and each tag key can have only one value.
+     * - Maximum key length - 128 Unicode characters in UTF-8
+     * - Maximum value length - 256 Unicode characters in UTF-8
+     * - If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
+     * - Tag keys and values are case-sensitive.
+     * - Do not use `aws:` , `AWS:` , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for AWS use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type ECSClusterAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the Amazon ECS cluster, such as `arn:aws:ecs:us-east-2:123456789012:cluster/MyECSCluster` .
+     */
+    Arn: string;
+};
+/**
+ * The `CapacityProviderStrategyItem` property specifies the details of the default capacity provider strategy for the cluster. When services or tasks are run in the cluster with no launch type or capacity provider strategy specified, the default capacity provider strategy is used.
+ */
+export type CapacityProviderStrategyItem = {
+    /**
+     * The *base* value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a *base* defined. If no value is specified, the default value of `0` is used.
+     */
+    Base?: number | undefined;
+    /**
+     * The short name of the capacity provider.
+     */
+    CapacityProvider?: string | undefined;
+    /**
+     * The *weight* value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The `weight` value is taken into consideration after the `base` value, if defined, is satisfied.
+     *
+     * If no `weight` value is specified, the default value of `0` is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of `0` can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of `0` , any `RunTask` or `CreateService` actions using the capacity provider strategy will fail.
+     *
+     * An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of `1` , then when the `base` is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of `1` for *capacityProviderA* and a weight of `4` for *capacityProviderB* , then for every one task that's run using *capacityProviderA* , four tasks would use *capacityProviderB* .
+     */
+    Weight?: number | undefined;
+};
+/**
+ * The execute command and managed storage configuration for the cluster.
+ */
+export type ClusterConfiguration = {
+    /**
+     * The details of the execute command configuration.
+     */
+    ExecuteCommandConfiguration?: ExecuteCommandConfiguration | undefined;
+    /**
+     * The details of the managed storage configuration.
+     */
+    ManagedStorageConfiguration?: ManagedStorageConfiguration | undefined;
+};
+/**
+ * The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights with enhanced observability or CloudWatch Container Insights for a cluster.
+ *
+ * Container Insights with enhanced observability provides all the Container Insights metrics, plus additional task and container metrics. This version supports enhanced observability for Amazon ECS clusters using the Amazon EC2 and Fargate launch types. After you configure Container Insights with enhanced observability on Amazon ECS, Container Insights auto-collects detailed infrastructure telemetry from the cluster level down to the container level in your environment and displays these critical performance data in curated dashboards removing the heavy lifting in observability set-up.
+ *
+ * For more information, see [Monitor Amazon ECS containers using Container Insights with enhanced observability](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cloudwatch-container-insights.html) in the *Amazon Elastic Container Service Developer Guide* .
+ */
+export type ClusterSettings = {
+    /**
+     * The name of the cluster setting. The value is `containerInsights` .
+     */
+    Name?: string | undefined;
+    /**
+     * The value to set for the cluster setting. The supported values are `enhanced` , `enabled` , and `disabled` .
+     *
+     * To use Container Insights with enhanced observability, set the `containerInsights` account setting to `enhanced` .
+     *
+     * To use Container Insights, set the `containerInsights` account setting to `enabled` .
+     *
+     * If a cluster value is specified, it will override the `containerInsights` value set with [PutAccountSetting](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSetting.html) or [PutAccountSettingDefault](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutAccountSettingDefault.html) .
+     */
+    Value?: string | undefined;
+};
+/**
+ * The details of the execute command configuration.
+ */
+export type ExecuteCommandConfiguration = {
+    /**
+     * Specify an AWS Key Management Service key ID to encrypt the data between the local client and the container.
+     */
+    KmsKeyId?: string | undefined;
+    /**
+     * The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When `logging=OVERRIDE` is specified, a `logConfiguration` must be provided.
+     */
+    LogConfiguration?: ExecuteCommandLogConfiguration | undefined;
+    /**
+     * The log setting to use for redirecting logs for your execute command results. The following log settings are available.
+     *
+     * - `NONE` : The execute command session is not logged.
+     * - `DEFAULT` : The `awslogs` configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no `awslogs` log driver is configured in the task definition, the output won't be logged.
+     * - `OVERRIDE` : Specify the logging details as a part of `logConfiguration` . If the `OVERRIDE` logging option is specified, the `logConfiguration` is required.
+     */
+    Logging?: string | undefined;
+};
+/**
+ * The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket.
+ */
+export type ExecuteCommandLogConfiguration = {
+    /**
+     * Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be off.
+     */
+    CloudWatchEncryptionEnabled?: boolean | undefined;
+    /**
+     * The name of the CloudWatch log group to send logs to.
+     *
+     * > The CloudWatch log group must already be created.
+     */
+    CloudWatchLogGroupName?: string | undefined;
+    /**
+     * The name of the S3 bucket to send logs to.
+     *
+     * > The S3 bucket must already be created.
+     */
+    S3BucketName?: string | undefined;
+    /**
+     * Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.
+     */
+    S3EncryptionEnabled?: boolean | undefined;
+    /**
+     * An optional folder in the S3 bucket to place logs in.
+     */
+    S3KeyPrefix?: string | undefined;
+};
+/**
+ * The managed storage configuration for the cluster.
+ */
+export type ManagedStorageConfiguration = {
+    /**
+     * Specify the AWS Key Management Service key ID for Fargate ephemeral storage.
+     *
+     * When you specify a `fargateEphemeralStorageKmsKeyId` , AWS Fargate uses the key to encrypt data at rest in ephemeral storage. For more information about Fargate ephemeral storage encryption, see [Customer managed keys for AWS Fargate ephemeral storage for Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-storage-encryption.html) in the *Amazon Elastic Container Service Developer Guide* .
+     *
+     * The key must be a single Region key.
+     */
+    FargateEphemeralStorageKmsKeyId?: string | undefined;
+    /**
+     * Specify a AWS Key Management Service key ID to encrypt Amazon ECS managed storage.
+     *
+     * When you specify a `kmsKeyId` , Amazon ECS uses the key to encrypt data volumes managed by Amazon ECS that are attached to tasks in the cluster. The following data volumes are managed by Amazon ECS: Amazon EBS. For more information about encryption of Amazon EBS volumes attached to Amazon ECS tasks, see [Encrypt data stored in Amazon EBS volumes for Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-kms-encryption.html) in the *Amazon Elastic Container Service Developer Guide* .
+     *
+     * The key must be a single Region key.
+     */
+    KmsKeyId?: string | undefined;
+};
+/**
+ * Use this parameter to set a default Service Connect namespace. After you set a default Service Connect namespace, any new services with Service Connect turned on that are created in the cluster are added as client services in the namespace. This setting only applies to new services that set the `enabled` parameter to `true` in the `ServiceConnectConfiguration` . You can set the namespace of each service individually in the `ServiceConnectConfiguration` to override this default parameter.
+ *
+ * Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see [Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) in the *Amazon Elastic Container Service Developer Guide* .
+ */
+export type ServiceConnectDefaults = {
+    /**
+     * The namespace name or full Amazon Resource Name (ARN) of the AWS Cloud Map namespace that's used when you create a service and don't specify a Service Connect configuration. The namespace name can include up to 1024 characters. The name is case-sensitive. The name can't include greater than (>), less than (<), double quotation marks ("), or slash (/).
+     *
+     * If you enter an existing namespace name or ARN, then that namespace will be used. Any namespace type is supported. The namespace must be in this account and this AWS Region.
+     *
+     * If you enter a new name, a AWS Cloud Map namespace will be created. Amazon ECS creates a AWS Cloud Map namespace with the "API calls" method of instance discovery only. This instance discovery method is the "HTTP" namespace type in the AWS Command Line Interface . Other types of instance discovery aren't used by Service Connect.
+     *
+     * If you update the cluster with an empty string `""` for the namespace name, the cluster configuration for Service Connect is removed. Note that the namespace will remain in AWS Cloud Map and must be deleted separately.
+     *
+     * For more information about AWS Cloud Map , see [Working with Services](https://docs.aws.amazon.com/cloud-map/latest/dg/working-with-services.html) in the *AWS Cloud Map Developer Guide* .
+     */
+    Namespace?: string | undefined;
+};
+//# sourceMappingURL=aws-ecs-cluster.d.ts.map

package/out/exports/resources.generated/aws-ecs-clustercapacityproviderassociations.d.ts

@@ -0,0 +1,49 @@
+import type { ResourceDefinition } from "../main.ts";
+export type ECSClusterCapacityProviderAssociations = ResourceDefinition<"AWS::ECS::ClusterCapacityProviderAssociations", ECSClusterCapacityProviderAssociationsProps>;
+/**
+ * The `AWS::ECS::ClusterCapacityProviderAssociations` resource associates one or more capacity providers and a default capacity provider strategy with a cluster.
+ */
+export type ECSClusterCapacityProviderAssociationsProps = {
+    /**
+     * The capacity providers to associate with the cluster.
+     */
+    CapacityProviders: CapacityProvider[];
+    /**
+     * The cluster the capacity provider association is the target of.
+     */
+    Cluster: string;
+    /**
+     * The default capacity provider strategy to associate with the cluster.
+     */
+    DefaultCapacityProviderStrategy: CapacityProviderStrategy[];
+};
+/**
+ * If using ec2 auto-scaling, the name of the associated capacity provider. Otherwise FARGATE, FARGATE_SPOT.
+ */
+export type CapacityProvider = ("FARGATE" | "FARGATE_SPOT") | string;
+/**
+ * The `CapacityProviderStrategy` property specifies the details of the default capacity provider strategy for the cluster. When services or tasks are run in the cluster with no launch type or capacity provider strategy specified, the default capacity provider strategy is used.
+ */
+export type CapacityProviderStrategy = {
+    /**
+     * The *base* value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a *base* defined. If no value is specified, the default value of `0` is used.
+     * @min 0
+     * @max 100000
+     */
+    Base?: number | undefined;
+    /**
+     * The short name of the capacity provider.
+     */
+    CapacityProvider: CapacityProvider;
+    /**
+     * The *weight* value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The `weight` value is taken into consideration after the `base` value, if defined, is satisfied.
+     *
+     * If no `weight` value is specified, the default value of `0` is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of `0` can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of `0` , any `RunTask` or `CreateService` actions using the capacity provider strategy will fail.
+     *
+     * An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of `1` , then when the `base` is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of `1` for *capacityProviderA* and a weight of `4` for *capacityProviderB* , then for every one task that's run using *capacityProviderA* , four tasks would use *capacityProviderB* .
+     * @min 0
+     * @max 1000
+     */
+    Weight?: number | undefined;
+};
+//# sourceMappingURL=aws-ecs-clustercapacityproviderassociations.d.ts.map

package/out/exports/resources.generated/aws-ecs-primarytaskset.d.ts

@@ -0,0 +1,20 @@
+import type { ResourceDefinition } from "../main.ts";
+export type ECSPrimaryTaskSet = ResourceDefinition<"AWS::ECS::PrimaryTaskSet", ECSPrimaryTaskSetProps>;
+/**
+ * Modifies which task set in a service is the primary task set. Any parameters that are updated on the primary task set in a service will transition to the service. This is used when a service uses the `EXTERNAL` deployment controller type. For more information, see [Amazon ECS Deployment Types](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html) in the *Amazon Elastic Container Service Developer Guide* .
+ */
+export type ECSPrimaryTaskSetProps = {
+    /**
+     * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set exists in.
+     */
+    Cluster: string;
+    /**
+     * The short name or full Amazon Resource Name (ARN) of the service that the task set exists in.
+     */
+    Service: string;
+    /**
+     * The short name or full Amazon Resource Name (ARN) of the task set to set as the primary task set in the deployment.
+     */
+    TaskSetId: string;
+};
+//# sourceMappingURL=aws-ecs-primarytaskset.d.ts.map