@propulsionworks/cloudformation 0.0.2 → 0.1.0

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

@@ -0,0 +1,219 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type ECSTaskSet = ResourceDefinitionWithAttributes<"AWS::ECS::TaskSet", ECSTaskSetProps, ECSTaskSetAttribs>;
+/**
+ * Create a task set in the specified cluster and 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* .
+ *
+ * > On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
+ *
+ * For information about the maximum number of task sets and other quotas, see [Amazon ECS service quotas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html) in the *Amazon Elastic Container Service Developer Guide* .
+ */
+export type ECSTaskSetProps = {
+    /**
+     * The capacity provider strategy that are associated with the task set.
+     */
+    CapacityProviderStrategy?: CapacityProviderStrategyItem[] | undefined;
+    /**
+     * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service to create the task set in.
+     */
+    Cluster: string;
+    /**
+     * An optional non-unique tag that identifies this task set in external systems. If the task set is associated with a service discovery registry, the tasks in this task set will have the `ECS_TASK_SET_EXTERNAL_ID` AWS Cloud Map attribute set to the provided value.
+     */
+    ExternalId?: string | undefined;
+    /**
+     * The launch type that new tasks in the task set uses. For more information, see [Amazon ECS launch types](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_types.html) in the *Amazon Elastic Container Service Developer Guide* .
+     *
+     * If a `launchType` is specified, the `capacityProviderStrategy` parameter must be omitted.
+     */
+    LaunchType?: "EC2" | "FARGATE" | undefined;
+    /**
+     * A load balancer object representing the load balancer to use with the task set. The supported load balancer types are either an Application Load Balancer or a Network Load Balancer.
+     */
+    LoadBalancers?: LoadBalancer[] | undefined;
+    /**
+     * The network configuration for the task set.
+     */
+    NetworkConfiguration?: NetworkConfiguration | undefined;
+    /**
+     * The platform version that the tasks in the task set uses. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the `LATEST` platform version is used.
+     */
+    PlatformVersion?: string | undefined;
+    /**
+     * A floating-point percentage of your desired number of tasks to place and keep running in the task set.
+     */
+    Scale?: Scale | undefined;
+    /**
+     * The short name or full Amazon Resource Name (ARN) of the service to create the task set in.
+     */
+    Service: string;
+    /**
+     * The details of the service discovery registries to assign to this task set. For more information, see [Service discovery](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html) .
+     */
+    ServiceRegistries?: ServiceRegistry[] | undefined;
+    /**
+     * The metadata that you apply to the task set 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;
+    /**
+     * The task definition for the tasks in the task set to use. If a revision isn't specified, the latest `ACTIVE` revision is used.
+     */
+    TaskDefinition: string;
+};
+export type ECSTaskSetAttribs = {
+    /**
+     * The ID of the task set.
+     */
+    Id: string;
+};
+/**
+ * An object representing the networking details for a task or service. For example `awsVpcConfiguration={subnets=["subnet-12344321"],securityGroups=["sg-12344321"]}` .
+ */
+export type AwsVpcConfiguration = {
+    /**
+     * Whether the task's elastic network interface receives a public IP address.
+     *
+     * Consider the following when you set this value:
+     *
+     * - When you use `create-service` or `update-service` , the default is `DISABLED` .
+     * - When the service `deploymentController` is `ECS` , the value must be `DISABLED` .
+     */
+    AssignPublicIp?: "DISABLED" | "ENABLED" | undefined;
+    /**
+     * The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified.
+     *
+     * > All specified security groups must be from the same VPC.
+     */
+    SecurityGroups?: string[] | undefined;
+    /**
+     * The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified.
+     *
+     * > All specified subnets must be from the same VPC.
+     */
+    Subnets: string[];
+};
+/**
+ * The details of a capacity provider strategy. A capacity provider strategy can be set when using the [RunTask](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) or [CreateCluster](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html) APIs or as the default capacity provider strategy for a cluster with the `CreateCluster` API.
+ *
+ * Only capacity providers that are already associated with a cluster and have an `ACTIVE` or `UPDATING` status can be used in a capacity provider strategy. The [PutClusterCapacityProviders](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html) API is used to associate a capacity provider with a cluster.
+ *
+ * If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the [CreateClusterCapacityProvider](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.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 in a capacity provider strategy.
+ *
+ * With `FARGATE_SPOT` , you can run interruption tolerant tasks at a rate that's discounted compared to the `FARGATE` price. `FARGATE_SPOT` runs tasks on spare compute capacity. When AWS needs the capacity back, your tasks are interrupted with a two-minute warning. `FARGATE_SPOT` supports Linux tasks with the X86_64 architecture on platform version 1.3.0 or later. `FARGATE_SPOT` supports Linux tasks with the ARM64 architecture on platform version 1.4.0 or later.
+ *
+ * A capacity provider strategy can contain a maximum of 20 capacity providers.
+ */
+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 load balancer configuration to use with a service or task set.
+ *
+ * When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.
+ *
+ * We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.
+ *
+ * A service-linked role is required for services that use multiple target groups. For more information, see [Using service-linked roles](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html) in the *Amazon Elastic Container Service Developer Guide* .
+ */
+export type LoadBalancer = {
+    /**
+     * The name of the container (as it appears in a container definition) to associate with the load balancer.
+     *
+     * You need to specify the container name when configuring the target group for an Amazon ECS load balancer.
+     */
+    ContainerName?: string | undefined;
+    /**
+     * The port on the container to associate with the load balancer. This port must correspond to a `containerPort` in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the `hostPort` of the port mapping.
+     */
+    ContainerPort?: number | undefined;
+    /**
+     * The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.
+     *
+     * A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer.
+     *
+     * For services using the `ECS` deployment controller, you can specify one or multiple target groups. For more information, see [Registering multiple target groups with a service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html) in the *Amazon Elastic Container Service Developer Guide* .
+     *
+     * For services using the `CODE_DEPLOY` deployment controller, you're required to define two target groups for the load balancer. For more information, see [Blue/green deployment with CodeDeploy](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-bluegreen.html) in the *Amazon Elastic Container Service Developer Guide* .
+     *
+     * > If your service's task definition uses the `awsvpc` network mode, you must choose `ip` as the target type, not `instance` . Do this when creating your target groups because tasks that use the `awsvpc` network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.
+     */
+    TargetGroupArn?: string | undefined;
+};
+/**
+ * The network configuration for a task or service.
+ */
+export type NetworkConfiguration = {
+    /**
+     * The VPC subnets and security groups that are associated with a task.
+     *
+     * > All specified subnets and security groups must be from the same VPC.
+     */
+    AwsVpcConfiguration?: AwsVpcConfiguration | undefined;
+};
+/**
+ * A floating-point percentage of the desired number of tasks to place and keep running in the task set.
+ */
+export type Scale = {
+    /**
+     * The unit of measure for the scale value.
+     */
+    Unit?: "PERCENT" | undefined;
+    /**
+     * The value, specified as a percent total of a service's `desiredCount` , to scale the task set. Accepted values are numbers between 0 and 100.
+     * @min 0
+     * @max 100
+     */
+    Value?: number | undefined;
+};
+/**
+ * The details for the service registry.
+ *
+ * Each service may be associated with one service registry. Multiple service registries for each service are not supported.
+ *
+ * When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.
+ */
+export type ServiceRegistry = {
+    /**
+     * The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the `bridge` or `host` network mode, you must specify a `containerName` and `containerPort` combination from the task definition. If the task definition that your service task specifies uses the `awsvpc` network mode and a type SRV DNS record is used, you must specify either a `containerName` and `containerPort` combination or a `port` value. However, you can't specify both.
+     */
+    ContainerName?: string | undefined;
+    /**
+     * The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the `bridge` or `host` network mode, you must specify a `containerName` and `containerPort` combination from the task definition. If the task definition your service task specifies uses the `awsvpc` network mode and a type SRV DNS record is used, you must specify either a `containerName` and `containerPort` combination or a `port` value. However, you can't specify both.
+     */
+    ContainerPort?: number | undefined;
+    /**
+     * The port value used if your service discovery service specified an SRV record. This field might be used if both the `awsvpc` network mode and SRV records are used.
+     */
+    Port?: number | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is AWS Cloud Map . For more information, see [CreateService](https://docs.aws.amazon.com/cloud-map/latest/api/API_CreateService.html) .
+     */
+    RegistryArn?: string | undefined;
+};
+//# sourceMappingURL=aws-ecs-taskset.d.ts.map

package/out/exports/resources.generated/aws-efs-accesspoint.d.ts

@@ -0,0 +1,98 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EFSAccessPoint = ResourceDefinitionWithAttributes<"AWS::EFS::AccessPoint", EFSAccessPointProps, EFSAccessPointAttribs>;
+/**
+ * The `AWS::EFS::AccessPoint` resource creates an EFS access point. An access point is an application-specific view into an EFS file system that applies an operating system user and group, and a file system path, to any file system request made through the access point. The operating system user and group override any identity information provided by the NFS client. The file system path is exposed as the access point's root directory. Applications using the access point can only access data in its own directory and below. To learn more, see [Mounting a file system using EFS access points](https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html) .
+ *
+ * This operation requires permissions for the `elasticfilesystem:CreateAccessPoint` action.
+ */
+export type EFSAccessPointProps = {
+    /**
+     * An array of key-value pairs to apply to this resource.
+     *
+     * For more information, see [Tag](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html) .
+     */
+    AccessPointTags?: Tag[] | undefined;
+    /**
+     * The opaque string specified in the request to ensure idempotent creation.
+     */
+    ClientToken?: string | undefined;
+    /**
+     * The ID of the EFS file system that the access point applies to. Accepts only the ID format for input when specifying a file system, for example `fs-0123456789abcedf2` .
+     */
+    FileSystemId: string;
+    /**
+     * The full POSIX identity, including the user ID, group ID, and secondary group IDs on the access point that is used for all file operations by NFS clients using the access point.
+     */
+    PosixUser?: PosixUser | undefined;
+    /**
+     * The directory on the EFS file system that the access point exposes as the root directory to NFS clients using the access point.
+     */
+    RootDirectory?: RootDirectory | undefined;
+};
+export type EFSAccessPointAttribs = {
+    /**
+     * The ID of the EFS access point.
+     */
+    AccessPointId: string;
+    /**
+     * The Amazon Resource Name (ARN) of the access point.
+     */
+    Arn: string;
+};
+/**
+ * Required if the `RootDirectory` > `Path` specified does not exist. Specifies the POSIX IDs and permissions to apply to the access point's `RootDirectory` > `Path` . If the access point root directory does not exist, EFS creates it with these settings when a client connects to the access point. When specifying `CreationInfo` , you must include values for all properties.
+ *
+ * Amazon EFS creates a root directory only if you have provided the CreationInfo: OwnUid, OwnGID, and permissions for the directory. If you do not provide this information, Amazon EFS does not create the root directory. If the root directory does not exist, attempts to mount using the access point will fail.
+ *
+ * > If you do not provide `CreationInfo` and the specified `RootDirectory` does not exist, attempts to mount the file system using the access point will fail.
+ */
+export type CreationInfo = {
+    /**
+     * Specifies the POSIX group ID to apply to the `RootDirectory` . Accepts values from 0 to 2^32 (4294967295).
+     */
+    OwnerGid: string;
+    /**
+     * Specifies the POSIX user ID to apply to the `RootDirectory` . Accepts values from 0 to 2^32 (4294967295).
+     */
+    OwnerUid: string;
+    /**
+     * Specifies the POSIX permissions to apply to the `RootDirectory` , in the format of an octal number representing the file's mode bits.
+     * @pattern ^[0-7]{3,4}$
+     */
+    Permissions: string;
+};
+/**
+ * The full POSIX identity, including the user ID, group ID, and any secondary group IDs, on the access point that is used for all file system operations performed by NFS clients using the access point.
+ */
+export type PosixUser = {
+    /**
+     * The POSIX group ID used for all file system operations using this access point.
+     */
+    Gid: string;
+    /**
+     * Secondary POSIX group IDs used for all file system operations using this access point.
+     */
+    SecondaryGids?: string[] | undefined;
+    /**
+     * The POSIX user ID used for all file system operations using this access point.
+     */
+    Uid: string;
+};
+/**
+ * Specifies the directory on the Amazon EFS file system that the access point provides access to. The access point exposes the specified file system path as the root directory of your file system to applications using the access point. NFS clients using the access point can only access data in the access point's `RootDirectory` and its subdirectories.
+ */
+export type RootDirectory = {
+    /**
+     * (Optional) Specifies the POSIX IDs and permissions to apply to the access point's `RootDirectory` . If the `RootDirectory` > `Path` specified does not exist, EFS creates the root directory using the `CreationInfo` settings when a client connects to an access point. When specifying the `CreationInfo` , you must provide values for all properties.
+     *
+     * > If you do not provide `CreationInfo` and the specified `RootDirectory` > `Path` does not exist, attempts to mount the file system using the access point will fail.
+     */
+    CreationInfo?: CreationInfo | undefined;
+    /**
+     * Specifies the path on the EFS file system to expose as the root directory to NFS clients using the access point to access the EFS file system. A path can have up to four subdirectories. If the specified path does not exist, you are required to provide the `CreationInfo` .
+     * @minLength 1
+     * @maxLength 100
+     */
+    Path?: string | undefined;
+};
+//# sourceMappingURL=aws-efs-accesspoint.d.ts.map

package/out/exports/resources.generated/aws-efs-filesystem.d.ts

@@ -0,0 +1,182 @@
+import type { ResourceDefinitionWithAttributes, TemplatePolicyDocument, Tag } from "../main.ts";
+export type EFSFileSystem = ResourceDefinitionWithAttributes<"AWS::EFS::FileSystem", EFSFileSystemProps, EFSFileSystemAttribs>;
+/**
+ * The `AWS::EFS::FileSystem` resource creates a new, empty file system in Amazon Elastic File System ( Amazon EFS ). You must create a mount target ( [AWS::EFS::MountTarget](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-efs-mounttarget.html) ) to mount your EFS file system on an Amazon EC2 or other AWS cloud compute resource.
+ */
+export type EFSFileSystemProps = {
+    /**
+     * For One Zone file systems, specify the AWS Availability Zone in which to create the file system. Use the format `us-east-1a` to specify the Availability Zone. For more information about One Zone file systems, see [EFS file system types](https://docs.aws.amazon.com/efs/latest/ug/availability-durability.html#file-system-type) in the *Amazon EFS User Guide* .
+     *
+     * > One Zone file systems are not available in all Availability Zones in AWS Regions where Amazon EFS is available.
+     */
+    AvailabilityZoneName?: string | undefined;
+    /**
+     * Use the `BackupPolicy` to turn automatic backups on or off for the file system.
+     */
+    BackupPolicy?: BackupPolicy | undefined;
+    /**
+     * (Optional) A boolean that specifies whether or not to bypass the `FileSystemPolicy` lockout safety check. The lockout safety check determines whether the policy in the request will lock out, or prevent, the IAM principal that is making the request from making future `PutFileSystemPolicy` requests on this file system. Set `BypassPolicyLockoutSafetyCheck` to `True` only when you intend to prevent the IAM principal that is making the request from making subsequent `PutFileSystemPolicy` requests on this file system. The default value is `False` .
+     */
+    BypassPolicyLockoutSafetyCheck?: boolean | undefined;
+    /**
+     * A Boolean value that, if true, creates an encrypted file system. When creating an encrypted file system, you have the option of specifying a KmsKeyId for an existing AWS KMS key . If you don't specify a KMS key , then the default KMS key for Amazon EFS , `/aws/elasticfilesystem` , is used to protect the encrypted file system.
+     */
+    Encrypted?: boolean | undefined;
+    /**
+     * The `FileSystemPolicy` for the EFS file system. A file system policy is an IAM resource policy used to control NFS access to an EFS file system. For more information, see [Using IAM to control NFS access to Amazon EFS](https://docs.aws.amazon.com/efs/latest/ug/iam-access-control-nfs-efs.html) in the *Amazon EFS User Guide* .
+     * @policy
+     */
+    FileSystemPolicy?: TemplatePolicyDocument | undefined;
+    /**
+     * Describes the protection on the file system.
+     */
+    FileSystemProtection?: FileSystemProtection | undefined;
+    /**
+     * Use to create one or more tags associated with the file system. Each tag is a user-defined key-value pair. Name your file system on creation by including a `"Key":"Name","Value":"{value}"` key-value pair. Each key must be unique. For more information, see [Tagging AWS resources](https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html) in the *AWS General Reference Guide* .
+     */
+    FileSystemTags?: Tag[] | undefined;
+    /**
+     * The ID of the AWS KMS key to be used to protect the encrypted file system. This parameter is only required if you want to use a nondefault KMS key . If this parameter is not specified, the default KMS key for Amazon EFS is used. This ID can be in one of the following formats:
+     *
+     * - Key ID - A unique identifier of the key, for example `1234abcd-12ab-34cd-56ef-1234567890ab` .
+     * - ARN - An Amazon Resource Name (ARN) for the key, for example `arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab` .
+     * - Key alias - A previously created display name for a key, for example `alias/projectKey1` .
+     * - Key alias ARN - An ARN for a key alias, for example `arn:aws:kms:us-west-2:444455556666:alias/projectKey1` .
+     *
+     * If `KmsKeyId` is specified, the `Encrypted` parameter must be set to true.
+     */
+    KmsKeyId?: string | undefined;
+    /**
+     * An array of `LifecyclePolicy` objects that define the file system's `LifecycleConfiguration` object. A `LifecycleConfiguration` object informs Lifecycle management of the following:
+     *
+     * - When to move files in the file system from primary storage to IA storage.
+     * - When to move files in the file system from primary storage or IA storage to Archive storage.
+     * - When to move files that are in IA or Archive storage to primary storage.
+     *
+     * > Amazon EFS requires that each `LifecyclePolicy` object have only a single transition. This means that in a request body, `LifecyclePolicies` needs to be structured as an array of `LifecyclePolicy` objects, one object for each transition, `TransitionToIA` , `TransitionToArchive` `TransitionToPrimaryStorageClass` . See the example requests in the following section for more information.
+     */
+    LifecyclePolicies?: LifecyclePolicy[] | undefined;
+    /**
+     * The performance mode of the file system. We recommend `generalPurpose` performance mode for all file systems. File systems using the `maxIO` performance mode can scale to higher levels of aggregate throughput and operations per second with a tradeoff of slightly higher latencies for most file operations. The performance mode can't be changed after the file system has been created. The `maxIO` mode is not supported on One Zone file systems.
+     *
+     * > Due to the higher per-operation latencies with Max I/O, we recommend using General Purpose performance mode for all file systems.
+     *
+     * Default is `generalPurpose` .
+     */
+    PerformanceMode?: string | undefined;
+    /**
+     * The throughput, measured in mebibytes per second (MiBps), that you want to provision for a file system that you're creating. Required if `ThroughputMode` is set to `provisioned` . Valid values are 1-3414 MiBps, with the upper limit depending on Region. To increase this limit, contact Support . For more information, see [Amazon EFS quotas that you can increase](https://docs.aws.amazon.com/efs/latest/ug/limits.html#soft-limits) in the *Amazon EFS User Guide* .
+     */
+    ProvisionedThroughputInMibps?: number | undefined;
+    /**
+     * Describes the replication configuration for a specific file system.
+     */
+    ReplicationConfiguration?: ReplicationConfiguration | undefined;
+    /**
+     * Specifies the throughput mode for the file system. The mode can be `bursting` , `provisioned` , or `elastic` . If you set `ThroughputMode` to `provisioned` , you must also set a value for `ProvisionedThroughputInMibps` . After you create the file system, you can decrease your file system's Provisioned throughput or change between the throughput modes, with certain time restrictions. For more information, see [Specifying throughput with provisioned mode](https://docs.aws.amazon.com/efs/latest/ug/performance.html#provisioned-throughput) in the *Amazon EFS User Guide* .
+     *
+     * Default is `bursting` .
+     */
+    ThroughputMode?: string | undefined;
+};
+export type EFSFileSystemAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the EFS file system.
+     *
+     * Example: `arn:aws:elasticfilesystem:us-west-2:1111333322228888:file-system/fs-0123456789abcdef8`
+     */
+    Arn: string;
+    /**
+     * The ID of the EFS file system. For example: `fs-abcdef0123456789a`
+     */
+    FileSystemId: string;
+};
+/**
+ * The backup policy turns automatic backups for the file system on or off.
+ */
+export type BackupPolicy = {
+    /**
+     * Set the backup policy status for the file system.
+     *
+     * - *`ENABLED`* - Turns automatic backups on for the file system.
+     * - *`DISABLED`* - Turns automatic backups off for the file system.
+     */
+    Status: "DISABLED" | "ENABLED";
+};
+/**
+ * Describes the protection on the file system.
+ */
+export type FileSystemProtection = {
+    /**
+     * The status of the file system's replication overwrite protection.
+     *
+     * - `ENABLED` – The file system cannot be used as the destination file system in a replication configuration. The file system is writeable. Replication overwrite protection is `ENABLED` by default.
+     * - `DISABLED` – The file system can be used as the destination file system in a replication configuration. The file system is read-only and can only be modified by EFS replication.
+     * - `REPLICATING` – The file system is being used as the destination file system in a replication configuration. The file system is read-only and is modified only by EFS replication.
+     *
+     * If the replication configuration is deleted, the file system's replication overwrite protection is re-enabled, the file system becomes writeable.
+     */
+    ReplicationOverwriteProtection?: "DISABLED" | "ENABLED" | undefined;
+};
+/**
+ * Describes a policy used by Lifecycle management that specifies when to transition files into and out of the EFS storage classes. For more information, see [Managing file system storage](https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html) .
+ *
+ * > - Each `LifecyclePolicy` object can have only a single transition. This means that in a request body, `LifecyclePolicies` must be structured as an array of `LifecyclePolicy` objects, one object for each transition, `TransitionToIA` , `TransitionToArchive` , `TransitionToPrimaryStorageClass` .
+ * > - See the AWS::EFS::FileSystem examples for the correct `LifecyclePolicy` structure. Do not use the syntax shown on this page.
+ */
+export type LifecyclePolicy = {
+    /**
+     * The number of days after files were last accessed in primary storage (the Standard storage class) at which to move them to Archive storage. Metadata operations such as listing the contents of a directory don't count as file access events.
+     */
+    TransitionToArchive?: string | undefined;
+    /**
+     * The number of days after files were last accessed in primary storage (the Standard storage class) at which to move them to Infrequent Access (IA) storage. Metadata operations such as listing the contents of a directory don't count as file access events.
+     */
+    TransitionToIA?: string | undefined;
+    /**
+     * Whether to move files back to primary (Standard) storage after they are accessed in IA or Archive storage. Metadata operations such as listing the contents of a directory don't count as file access events.
+     */
+    TransitionToPrimaryStorageClass?: string | undefined;
+};
+/**
+ * Describes the replication configuration for a specific file system.
+ */
+export type ReplicationConfiguration = {
+    /**
+     * An array of destination objects. Only one destination object is supported.
+     */
+    Destinations?: ReplicationDestination[] | undefined;
+};
+/**
+ * Describes the destination file system in the replication configuration.
+ */
+export type ReplicationDestination = {
+    /**
+     * For One Zone file systems, the replication configuration must specify the Availability Zone in which the destination file system is located.
+     *
+     * Use the format `us-east-1a` to specify the Availability Zone. For more information about One Zone file systems, see [EFS file system types](https://docs.aws.amazon.com/efs/latest/ug/storage-classes.html) in the *Amazon EFS User Guide* .
+     *
+     * > One Zone file system type is not available in all Availability Zones in AWS Regions where Amazon EFS is available.
+     */
+    AvailabilityZoneName?: string | undefined;
+    /**
+     * The ID of the destination Amazon EFS file system.
+     * @pattern ^(arn:aws[-a-z]*:elasticfilesystem:[0-9a-z-:]+:file-system/fs-[0-9a-f]{8,40}|fs-[0-9a-f]{8,40})$
+     */
+    FileSystemId?: string | undefined;
+    /**
+     * The ID of an AWS KMS key used to protect the encrypted file system.
+     */
+    KmsKeyId?: string | undefined;
+    /**
+     * The AWS Region in which the destination file system is located.
+     *
+     * > For One Zone file systems, the replication configuration must specify the AWS Region in which the destination file system is located.
+     */
+    Region?: string | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the current source file system in the replication configuration.
+     */
+    RoleArn?: string | undefined;
+};
+//# sourceMappingURL=aws-efs-filesystem.d.ts.map

package/out/exports/resources.generated/aws-efs-mounttarget.d.ts

@@ -0,0 +1,38 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type EFSMountTarget = ResourceDefinitionWithAttributes<"AWS::EFS::MountTarget", EFSMountTargetProps, EFSMountTargetAttribs>;
+/**
+ * The `AWS::EFS::MountTarget` resource is an Amazon EFS resource that creates a mount target for an EFS file system. You can then mount the file system on Amazon EC2 instances or other resources by using the mount target.
+ */
+export type EFSMountTargetProps = {
+    /**
+     * The ID of the file system for which to create the mount target.
+     */
+    FileSystemId: string;
+    /**
+     * Valid IPv4 address within the address range of the specified subnet.
+     */
+    IpAddress?: string | undefined;
+    /**
+     * VPC security group IDs, of the form `sg-xxxxxxxx` . These must be for the same VPC as the subnet specified. The maximum number of security groups depends on account quota. For more information, see [Amazon VPC Quotas](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html) in the *Amazon VPC User Guide* (see the *Security Groups* table).
+     */
+    SecurityGroups: string[];
+    /**
+     * The ID of the subnet to add the mount target in. For One Zone file systems, use the subnet that is associated with the file system's Availability Zone.
+     */
+    SubnetId: string;
+};
+export type EFSMountTargetAttribs = {
+    /**
+     * The ID of the Amazon EFS file system that the mount target provides access to.
+     *
+     * Example: `fs-0123456789111222a`
+     */
+    Id: string;
+    /**
+     * The IPv4 address of the mount target.
+     *
+     * Example: 192.0.2.0
+     */
+    IpAddress: string;
+};
+//# sourceMappingURL=aws-efs-mounttarget.d.ts.map

package/out/exports/resources.generated/aws-eks-accessentry.d.ts

@@ -0,0 +1,86 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSAccessEntry = ResourceDefinitionWithAttributes<"AWS::EKS::AccessEntry", EKSAccessEntryProps, EKSAccessEntryAttribs>;
+/**
+ * Creates an access entry.
+ *
+ * An access entry allows an IAM principal to access your cluster. Access entries can replace the need to maintain entries in the `aws-auth` `ConfigMap` for authentication. You have the following options for authorizing an IAM principal to access Kubernetes objects on your cluster: Kubernetes role-based access control (RBAC), Amazon EKS, or both. Kubernetes RBAC authorization requires you to create and manage Kubernetes `Role` , `ClusterRole` , `RoleBinding` , and `ClusterRoleBinding` objects, in addition to managing access entries. If you use Amazon EKS authorization exclusively, you don't need to create and manage Kubernetes `Role` , `ClusterRole` , `RoleBinding` , and `ClusterRoleBinding` objects.
+ *
+ * For more information about access entries, see [Access entries](https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html) in the *Amazon EKS User Guide* .
+ */
+export type EKSAccessEntryProps = {
+    /**
+     * The access policies to associate to the access entry.
+     */
+    AccessPolicies?: AccessPolicy[] | undefined;
+    /**
+     * The name of your cluster.
+     * @minLength 1
+     */
+    ClusterName: string;
+    /**
+     * The value for `name` that you've specified for `kind: Group` as a `subject` in a Kubernetes `RoleBinding` or `ClusterRoleBinding` object. Amazon EKS doesn't confirm that the value for `name` exists in any bindings on your cluster. You can specify one or more names.
+     *
+     * Kubernetes authorizes the `principalArn` of the access entry to access any cluster objects that you've specified in a Kubernetes `Role` or `ClusterRole` object that is also specified in a binding's `roleRef` . For more information about creating Kubernetes `RoleBinding` , `ClusterRoleBinding` , `Role` , or `ClusterRole` objects, see [Using RBAC Authorization in the Kubernetes documentation](https://docs.aws.amazon.com/https://kubernetes.io/docs/reference/access-authn-authz/rbac/) .
+     *
+     * If you want Amazon EKS to authorize the `principalArn` (instead of, or in addition to Kubernetes authorizing the `principalArn` ), you can associate one or more access policies to the access entry using `AssociateAccessPolicy` . If you associate any access policies, the `principalARN` has all permissions assigned in the associated access policies and all permissions in any Kubernetes `Role` or `ClusterRole` objects that the group names are bound to.
+     */
+    KubernetesGroups?: string[] | undefined;
+    /**
+     * The ARN of the IAM principal for the `AccessEntry` . You can specify one ARN for each access entry. You can't specify the same ARN in more than one access entry. This value can't be changed after access entry creation.
+     *
+     * The valid principals differ depending on the type of the access entry in the `type` field. For `STANDARD` access entries, you can use every IAM principal type. For nodes ( `EC2` (for EKS Auto Mode), `EC2_LINUX` , `EC2_WINDOWS` , `FARGATE_LINUX` , and `HYBRID_LINUX` ), the only valid ARN is IAM roles. You can't use the STS session principal type with access entries because this is a temporary principal for each session and not a permanent identity that can be assigned permissions.
+     *
+     * [IAM best practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) recommend using IAM roles with temporary credentials, rather than IAM users with long-term credentials.
+     * @minLength 1
+     */
+    PrincipalArn: string;
+    /**
+     * Metadata that assists with categorization and organization. Each tag consists of a key and an optional value. You define both. Tags don't propagate to any other cluster or AWS resources.
+     */
+    Tags?: Tag[] | undefined;
+    /**
+     * The type of the new access entry. Valid values are `STANDARD` , `FARGATE_LINUX` , `EC2_LINUX` , `EC2_WINDOWS` , `EC2` (for EKS Auto Mode), `HYBRID_LINUX` , and `HYPERPOD_LINUX` .
+     *
+     * If the `principalArn` is for an IAM role that's used for self-managed Amazon EC2 nodes, specify `EC2_LINUX` or `EC2_WINDOWS` . Amazon EKS grants the necessary permissions to the node for you. If the `principalArn` is for any other purpose, specify `STANDARD` . If you don't specify a value, Amazon EKS sets the value to `STANDARD` . If you have the access mode of the cluster set to `API_AND_CONFIG_MAP` , it's unnecessary to create access entries for IAM roles used with Fargate profiles or managed Amazon EC2 nodes, because Amazon EKS creates entries in the `aws-auth` `ConfigMap` for the roles. You can't change this value once you've created the access entry.
+     *
+     * If you set the value to `EC2_LINUX` or `EC2_WINDOWS` , you can't specify values for `kubernetesGroups` , or associate an `AccessPolicy` to the access entry.
+     */
+    Type?: string | undefined;
+    /**
+     * The username to authenticate to Kubernetes with. We recommend not specifying a username and letting Amazon EKS specify it for you. For more information about the value Amazon EKS specifies for you, or constraints before specifying your own username, see [Creating access entries](https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html#creating-access-entries) in the *Amazon EKS User Guide* .
+     */
+    Username?: string | undefined;
+};
+export type EKSAccessEntryAttribs = {
+    /**
+     * The ARN of the access entry.
+     */
+    AccessEntryArn: string;
+};
+/**
+ * An access policy includes permissions that allow Amazon EKS to authorize an IAM principal to work with Kubernetes objects on your cluster. The policies are managed by Amazon EKS, but they're not IAM policies. You can't view the permissions in the policies using the API. The permissions for many of the policies are similar to the Kubernetes `cluster-admin` , `admin` , `edit` , and `view` cluster roles. For more information about these cluster roles, see [User-facing roles](https://docs.aws.amazon.com/https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) in the Kubernetes documentation. To view the contents of the policies, see [Access policy permissions](https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html#access-policy-permissions) in the *Amazon EKS User Guide* .
+ */
+export type AccessPolicy = {
+    /**
+     * The scope of an `AccessPolicy` that's associated to an `AccessEntry` .
+     */
+    AccessScope: AccessScope;
+    /**
+     * The ARN of the access policy.
+     */
+    PolicyArn: string;
+};
+/**
+ * The scope of an `AccessPolicy` that's associated to an `AccessEntry` .
+ */
+export type AccessScope = {
+    /**
+     * A Kubernetes `namespace` that an access policy is scoped to. A value is required if you specified `namespace` for `Type` .
+     */
+    Namespaces?: string[] | undefined;
+    /**
+     * The scope type of an access policy.
+     */
+    Type: "namespace" | "cluster";
+};
+//# sourceMappingURL=aws-eks-accessentry.d.ts.map